[FEATURE]: Add configurable skill paths

[yg-codes]

Problem

Currently, skill file locations are hardcoded to a fixed set of paths:

• Project: .opencode/skills/, .claude/skills/, .agents/skills/
• Global: ~/.config/opencode/skills/, ~/.claude/skills/, ~/.agents/skills/

Users cannot add custom paths for skill discovery, such as ~/.claude/plugins/marketplaces.

Proposed Solution

Add a configuration option in opencode.json to specify additional skill directories:

{
  "skills": {
    "paths": [
      "~/.claude/plugins/marketplaces",
      "~/shared-skills"
    ]
  }
}

Use Cases

1. Plugin marketplaces: Users could maintain a separate directory for community-shared skills
2. Team-shared skills: Organizations could point to a shared location for team-specific skills
3. Skill development: Easier to develop and test skills in a separate directory before moving to final location

Current Workaround

Using symlinks, but this is manual and doesn't scale well for multiple directories.

Related

• https://opencode.ai/docs/skills/

---

• I have searched for similar feature requests and found related issues ([FEATURE]: Allow custom skills directories #8533, Feature Request: Configurable skills search paths & TUI settings management #11189, [FEATURE]: Configurable search paths for commands and agents (parity with skills) #14240), but this issue provides additional context and use cases

[github-actions]

Thanks for updating the issue! It now follows the contributing guidelines and the needs:compliance label has been removed. Your feature request is good to go.

[Eckii24]

Already in place?
#9640

[yg-codes]

Thanks @Eckii24 for the pointer!

You're right - I see that PR #9640 (feat: support config skill registration) already implements this feature. The PR was merged on 2026-01-29 and allows configuring skill paths via:

{
  "skills": {
    "paths": ["~/my-skills", "./relative/skills", "/absolute/path"]
  }
}

This covers all the use cases I mentioned (plugin marketplaces, team-shared skills, skill development).

Closing this as completed - the feature is already available in the dev branch.