Backward compatibility broken - enforcement of the /skill directory naming #6432

Activity

1. Melodeiro

   added

   bugSomething isn't workingSomething isn't working

   on Dec 30, 2025
2. github-actions

   assigned

   rekram1-node

   on Dec 30, 2025
3. github-actions commented on Dec 30, 2025

   

   github-actionsBot

   on Dec 30, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Inconsistency in docs for where to install skills #6171: Inconsistency in docs for where to install skills - discusses the difference between ~/.opencode/skill and ~/.config/opencode/skill
   • Global skills are not loaded #6292: Global skills are not loaded - related issue where skills in global config folder are not being discovered
   • Skill discovery doesn't match Claude Code's skills/ directory structure #6177: Skill discovery doesn't match Claude Code's skills/ directory structure - related to skill directory naming compatibility

   Feel free to ignore if none of these address your specific case.
4. Melodeiro commented on Dec 30, 2025

   

   Melodeiro

   on Dec 30, 2025

   Author

   More actions

   Here is an implementation which im using for reference. Maybe you can get some insights as well https://github.com/joshuadavidthomas/opencode-agent-skills
5. rekram1-node commented on Dec 30, 2025

   

   rekram1-node

   on Dec 30, 2025

   Collaborator

   More actions

   are you disabling the native skills support then? I think opencode supoorts those same features
6. Melodeiro commented on Dec 30, 2025

   

   Melodeiro

   on Dec 30, 2025

   Author

   More actions

   @rekram1-node, the most desired option for me is dynamic discovery of skills, using semantic search, to make the context less bloated.

   How can i disable the error message that /skills directory is wrong one? As i understood from the source code it is included in INVALID_DIRS and assertValid, and prevents opencode from starting up entirely
7. rekram1-node commented on Dec 30, 2025

   

   rekram1-node

   on Dec 30, 2025

   Collaborator

   More actions

   not possible to disable on ur end without source code changes
8. Melodeiro commented on Dec 30, 2025

   

   Melodeiro

   on Dec 30, 2025

   Author

   More actions

   Yeah thats what im asking about, at least make it a non-strict rule, only as a warning
9. rekram1-node commented on Dec 30, 2025

   

   rekram1-node

   on Dec 30, 2025

   Collaborator

   More actions

   we will change this on our end

   ❤️React with ❤️1Reacted by Melodeiro
10. rekram1-node commented on Dec 31, 2025

    

    rekram1-node

    on Dec 31, 2025

    Collaborator

    More actions

    fixed in next release: b9ef09a

    ❤️React with ❤️1Reacted by Melodeiro
11. rekram1-node

    closed this as completedon Dec 31, 2025
12. yacinehmito

    added a commit that references this issue on Jan 18, 2026

    docs: clarify skill naming is convention, not enforced

    ...

    39e6346