Related to #348 (closed as stale/not-planned), which asked more broadly for A2A config UI support. Re-raising a narrower, concrete piece of that gap.
Problem
Connecting an A2A client to a Declarative agent that performs actions fails validation with:
Field 'skills' array is empty. Agent must have at least one skill if it performs actions.
The dashboard's agent create/edit form only exposes a skills UI for spec.skills (git repo / OCI image refs) — the feature that materializes skill files into a /skills folder at runtime. But the validation error is actually about spec.declarative.a2aConfig.skills, a completely separate, purely descriptive field (id/name/tags/description/examples) that populates the AgentCard's advertised skills for A2A clients. There's no UI path to set this at all — the only way to satisfy the validation is to kubectl patch the Agent CR directly.
These are two unrelated fields that happen to share the word "skills," which makes the gap confusing in practice: the UI you're pointed to (git/OCI loader) isn't the one the error is actually asking about.
Suggested fix
Add a simple, repeatable form section to the agent create/edit UI (id / name / tags / description / examples) that maps directly to a2aConfig.skills, presented distinctly from the existing git/OCI skills-loader UI so the two concepts aren't conflated.
Related to #348 (closed as stale/not-planned), which asked more broadly for A2A config UI support. Re-raising a narrower, concrete piece of that gap.
Problem
Connecting an A2A client to a Declarative agent that performs actions fails validation with:
The dashboard's agent create/edit form only exposes a skills UI for
spec.skills(git repo / OCI image refs) — the feature that materializes skill files into a/skillsfolder at runtime. But the validation error is actually aboutspec.declarative.a2aConfig.skills, a completely separate, purely descriptive field (id/name/tags/description/examples) that populates the AgentCard's advertised skills for A2A clients. There's no UI path to set this at all — the only way to satisfy the validation is tokubectl patchthe Agent CR directly.These are two unrelated fields that happen to share the word "skills," which makes the gap confusing in practice: the UI you're pointed to (git/OCI loader) isn't the one the error is actually asking about.
Suggested fix
Add a simple, repeatable form section to the agent create/edit UI (id / name / tags / description / examples) that maps directly to
a2aConfig.skills, presented distinctly from the existing git/OCI skills-loader UI so the two concepts aren't conflated.