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
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Current OpenCode skill discovery is limited to fixed paths like .opencode/skill/<name>/SKILL.md and .claude/skills/, requiring skills to live in specific subdirectories . This lacks flexibility for broader standards. The agentskills.io protocol offers a standardized way to package reusable procedural knowledge and capabilities that agents can load on demand.
Example Implementation
# In any repo directory: ./skills/marketing/SKILL.md or ./src/tools/SKILL.md
# Agent prompts: "Use the marketing skill to generate a campaign"
# OpenCode lists: Available skills: marketing (./skills/marketing), git-release (./.opencode/skill/git-release)
Reacted by dev-abhirup-sc, Raphael Rösch and kenzo
It is confusing and would be ideal to conform to the spec.. below is some context on de-confusing myself which not even Opus was able to formulate the questions to clear itself up for 5 hours today dealing with these nuances and non-conforming details with OpenCode's implementation.
If the lack of conformity to the spec as its written was an intentional design decision, I happen to agree that skills should be instruction-only and therefore makes sense NOT to allow executable scripts to be bundled with them. But then maybe its an opportunity to collaborate with agentskills.io to change that in spec OR have them update and make clear in OpenCode docs that it does NOT support that aspect of the spec
Another thing slightly off-topic is that all extensibility features support intermediary directories except tools which requires tool files to be exactly at ~/.opencode/tools/ ... this took some time to understand but I definitely made the assumption.
Activity
github-actions commentedon Jan 7, 2026
This issue might be a duplicate of existing issues. Please check:
.claude/skills? #6266: Does opencode actually support finding skills at.claude/skills? (discusses configurability of skill discovery paths)Feel free to ignore if none of these address your specific case.
developerfred commentedon Jan 7, 2026
@LeoMartinDev have you already taken a look at https://github.com/code-yeongyu/oh-my-opencode It's a plugin that offers this native support; it's an OpenCode plugin.
rekram1-node commentedon Jan 7, 2026
@LeoMartinDev .skills/ doesnt appear to be part of the spec. Can you show me where it has that?
LeoMartinDev commentedon Jan 7, 2026
.skills is an example path, it could be anywhere I guess as long as it's folder containing a SKILL.md file.
Cursor recently started to support this https://cursor.com/docs/context/skills
diegohb commentedon Jan 25, 2026
I wanted to continue this discussion...
It is confusing and would be ideal to conform to the spec.. below is some context on de-confusing myself which not even Opus was able to formulate the questions to clear itself up for 5 hours today dealing with these nuances and non-conforming details with OpenCode's implementation.
DeepWiki:
If the lack of conformity to the spec as its written was an intentional design decision, I happen to agree that skills should be instruction-only and therefore makes sense NOT to allow executable scripts to be bundled with them. But then maybe its an opportunity to collaborate with agentskills.io to change that in spec OR have them update and make clear in OpenCode docs that it does NOT support that aspect of the spec
Another thing slightly off-topic is that all extensibility features support intermediary directories except tools which requires tool files to be exactly at ~/.opencode/tools/ ... this took some time to understand but I definitely made the assumption.
github-actions commentedon Mar 27, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.