You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show skills published by MCP servers (SEP-2640 skills extension) in the $ and / menus
#36098
MCP now has a standard for servers to publish Agent Skills. This asks whether T3 Code could list those skills in the $ and / menus next to locally installed ones.
What the extension is
SEP-2640 reached Final status. It defines how an MCP server serves Agent Skills using the existing Resources primitive, under the extension id io.modelcontextprotocol/skills:
skills/list enumerates the skills a server publishes. skills/get returns one skill's entry by URI.
Each file of a skill is a resource, normally at skill://<skill-path>/<file-path>, so SKILL.md and its supporting files load one at a time, when needed.
Every listed file carries a SHA-256 digest and a size, and a host verifies content against the digest.
Skill names resolve per origin, so a served skill cannot silently take the place of a local one.
One menu for every skill a thread can use. Today the menus list the skills each provider reports. Skills published by a connected MCP server are invisible there, even though the agent may be able to use them. Listing them, labelled with the server they came from, would make the menu complete.
No install step for server-published skills. A team or vendor that publishes skills through its MCP server would not need every person to install and update a copy locally.
Consistent across providers. Provider harnesses are adopting the extension at different speeds. If T3 Code read skills/list from the MCP servers configured for a thread, the menus could show the same served skills whichever provider runs the thread. I do not know whether T3 Code's architecture allows that, or whether it has to wait for each harness, so this is a question as much as a request.
Origin labelling. The extension asks hosts to keep served skills distinct from local ones and to resolve names per server. A server label on each row would cover that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
MCP now has a standard for servers to publish Agent Skills. This asks whether T3 Code could list those skills in the
$and/menus next to locally installed ones.What the extension is
SEP-2640 reached Final status. It defines how an MCP server serves Agent Skills using the existing Resources primitive, under the extension id
io.modelcontextprotocol/skills:skills/listenumerates the skills a server publishes.skills/getreturns one skill's entry by URI.skill://<skill-path>/<file-path>, soSKILL.mdand its supporting files load one at a time, when needed.Working group repo: https://github.com/modelcontextprotocol/ext-skills
Why it fits T3 Code
skills/listfrom the MCP servers configured for a thread, the menus could show the same served skills whichever provider runs the thread. I do not know whether T3 Code's architecture allows that, or whether it has to wait for each harness, so this is a question as much as a request.Related
All reactions