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
[FEATURE]: Add skills.exclude config to disable specific skill directories #26424
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Problem
OpenCode scans 6 standard skill directories (global + project-level):
~/.config/opencode/skills//SKILL.md
~/.claude/skills//SKILL.md
~/.agents/skills//SKILL.md
.opencode/skills//SKILL.md
.claude/skills//SKILL.md
.agents/skills//SKILL.md
Users may want to exclude specific directories (e.g., ~/.agents/skills/) while keeping others (e.g., ~/.claude/skills/). Currently there is no selective exclusion mechanism — either all global directories are scanned, or none via OPENCODE_DISABLE_GLOBAL_CONFIG.
Proposed Solution
Add a skills.exclude config option in opencode.json:
{
skills: {exclude: [~/.agents/skills]
}
}
Behavior:
Accepts an array of directory paths (supports ~ expansion)
Paths are checked against skill directory roots
Matching directories are skipped during discovery
Other directories remain unaffected
Why This Matters
Users with large skill collections in ~/.agents/skills/ may want to limit noise in the available skills list
GSD framework users have internal skills that should not appear in agent selection
permission.skill: deny blocks programmatic spawning (via task tool), which is too restrictive
Your proposal is more targeted (selective exclusion of specific directories vs. all-or-nothing), so it may still be distinct enough to warrant its own issue. Please review and confirm whether this addresses a different enough use case.
Activity
github-actions commentedon May 9, 2026
This issue might be a duplicate of existing issues. Please check:
skills.auto_discoveryconfig option or env varYour proposal is more targeted (selective exclusion of specific directories vs. all-or-nothing), so it may still be distinct enough to warrant its own issue. Please review and confirm whether this addresses a different enough use case.
github-actions commentedon Jul 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.