Repository navigation
Inconsistency in docs for where to install skills #6171
Description
Question
In the docs for skills, it seems like it is recommending to install skills in ~/.opencode/skill, while most of the other docs are recommending that skills are installed in ~/.config/opencode/skill.
Furthermore, it seems that ~/.config/opencode/skill works fine as well, and it remains undocumented.
Is there a reason for this difference? This is also important for those of us who version control our opencode configurations - having the split is sub-optimal for those cases.
Expected: There should be only one way that the docs recommend to install configurations and skills across the board
Activity
docs: document ~/.opencode as valid global config directory
malhashemi commentedon Dec 25, 2025
Hi @conradkoh this was a miss on my end when I opened the original skill PR, actually both paths are supported by opendcode as valid global directories. I have mad a PR to clarify this.
Thanks
connorads commentedon Dec 26, 2025
I updated it to be
~/.config/opencode/skillin #6132 because I also got confused!Not sure why it isn't live on the website yet 🤷
conradkoh commentedon Dec 26, 2025
Great, thanks @connorads. Hmm, is the docs release pipeline not auto run on merge 🤔
connorads commentedon Dec 27, 2025
Yeah not sure why it's not updating @conradkoh, raised an issue #6241
connorads commentedon Dec 28, 2025
Looks like this is sorted now
https://opencode.ai/docs/skills/
LeoMartinDev commentedon Jan 7, 2026
It would be great to support standards agent skills like https://agentskills.io/home
connorads commentedon Jan 7, 2026
What do you mean exactly @LeoMartinDev? Can you give some example(s)
OpenCode already supports agent skills: https://opencode.ai/docs/skills/
PS. I think we can close this issue now @conradkoh
LeoMartinDev commentedon Jan 7, 2026
Actually opencode only detects SKILLS from .claude or .opencode directories. What would be great is for opencode to support SKILLS from everywhere in the project
rekram1-node commentedon Jan 7, 2026
@LeoMartinDev what part of the spec isn't being implemented?