Repository navigation
feat(mcp): tell chat agents to follow a Skill without a shell - #520
Merged
Merged
Conversation
get_skill already returns the SKILL.md text, but every instruction led with runCommand, which a chat app cannot run. The tool description, the MCP section of /agent.md, and the skilld-registry Skill now say how to use a Skill without a shell: follow the markdown field for the session.
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. The pull request closed. |
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
None. Follows #516, whose homepage trust line says skilld works without a terminal.
❓ Type of change
📚 Description
ChatGPT, Claude, and other MCP apps can find a Skill through the MCP server, and
get_skillalready returns its SKILL.md text inmarkdown. Every instruction still led withrunCommand, which a chat app cannot run, so an agent there had no stated way to use the Skill.The
get_skilldescription, the MCP section of/agent.md, and theskilld-registrySkill now say the same thing. Without a shell, the agent followsmarkdownfor the session, after it names the Skill and its source repository. The files beside SKILL.md are listed infiles, not included.The CLI stays the lead path. A chat-app run gets SKILL.md only, with no supporting files and no approval stop for Skill behaviors.