Skills page agent scope omits Single Agent (single_agent)

[suger-m]

Summary

Backend already supports scoping Skills to single_agent (SkillToolkit is assembled with Agents.single_agent), but the Skills page "Select agent access" list is built mainly from Workforce workers (WORKFLOW_AGENT_LIST + custom workers). It does not stably surface Single Agent (single_agent / CAMEL Agent).

Impact

• Global skills work as expected (isGlobal: true).
• Restricting or assigning a skill only to Single Agent cannot be done reliably from the UI, even though the backend filter (_is_agent_allowed / selectedAgents) already accepts "single_agent"`.

Expected

Skills → Select agent access should always include Single Agent (single_agent, display name aligned with workspace: "CAMEL Agent") alongside workforce agents, so users can bind skills to Single Agent mode.

Actual

Agent chips are workforce-oriented; Single Agent is missing unless it happens to appear via an unrelated worker name.

Suggested fix

Include a stable single_agent option in SkillListItem agent options (and display metadata), matching backend Agents.single_agent.

References

• src/pages/Agents/components/SkillListItem.tsx (allAgents from WORKFLOW_AGENT_LIST + workerList)
• backend/app/agent/factory/toolkit_assembler.py (SkillToolkit(..., Agents.single_agent))
• backend/app/service/task.py (Agents.single_agent = \"single_agent\")