RFD: Add Agent Skills List proposal

[ignatov]

Proposes a mechanism for agents to advertise available skills to clients, aligned with the Agent Skills Specification (https://agentskills.io/specification).

Introduces:

• AvailableSkill type with name, description, license, compatibility, and allowedTools fields
• AvailableSkillsUpdate session notification

[benbrandt]

Seems reasonable. If I understand correctly, this is solely for informational purposes to the client to show the user?
At this stage, there would be no management of the skills available from the client?

[jwflicker]

What about enabling the client to forward additional locations of some skills folders to the agent, say at session creation, similar to how the client can forward a collection of MCP servers for the agent to use. Maybe the IDE has its own skills folders. Maybe the user wrote their own skills folder they would like to use across different agents.

[yordis]

How would it work when Skills are acting as Slash Commands? Does the Agent decide to put them in the Slash Command or not?

Recently, that is what has been happening, deprecating "Slash Commands" per se, and just have metadata in the skills to allow such direct activation.

Second, I am guessing the intention here is to do something like @skillname along with /skillname?

[timvisher-dd]

I'll add the basic premise of my duplicate RFD: I mainly want $ to work like it does in the codex and claude CLIs as well as the / completion to include skills as it does in the same. I think all we really need for this is an extremely small skills/list message and data structure containing a name and description.

[yurishkuro]

From a client perspective why does a client need to know the difference between command and skill? If client can invoke the skill directly then it's no different from invoking a command. If it cannot invoke the skill directly (i.e. the agent autonomously decides when to use a skill) then the client doesn't need to know such structured info about the skill, it would be sufficient to include capabilities in the description of the agent itself.

[timvisher-dd]

From a client perspective why does a client need to know the difference between command and skill? If client can invoke the skill directly then it's no different from invoking a command. If it cannot invoke the skill directly (i.e. the agent autonomously decides when to use a skill) then the client doesn't need to know such structured info about the skill, it would be sufficient to include capabilities in the description of the agent itself.

IMO it's because agents see skills as special. I went to the effort of translating most of my old docs into skills and saw a meaningful improvement to the agents' use of them. So as a human I'm interested in being able to surface what skills an agent knows about conveniently.

That said I agree that / should just fold them all together (perhaps with a simple type indicator like /foo Bar bat bin (skill) at most) and $ should only surface skills.