anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Allow configuring additional skill directory paths #8512

New Issue
Closed
opened 2026-02-16 18:10:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:10:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @nickwood on GitHub (Feb 4, 2026).

Originally assigned to: @thdxr on GitHub.

Currently, skills are only discovered from a fixed set of hardcoded paths:

  • .opencode/skills/
  • ~/.config/opencode/skills/
  • .claude/skills/ / ~/.claude/skills/
  • .agents/skills/ / ~/.agents/skills/
    This makes it difficult to combine skills from multiple sources (e.g., personal skills + a shared team repo + community skill collections) without resorting to symlink workarounds.

Proposed solution:

Add a config option to specify additional skill directories:
{
skill: {
paths: [
/path/to/shared-repo/skills,
/path/to/community-skills
]
}
}
These would be searched in addition to the existing default locations.

Use cases:

  • Maintaining personal skills separately from team/org shared skills
  • Using skills from a git repo without symlinking
  • Distributing skill collections independently from OpenCode config
  • Easier testing of skills during development

Current workaround:

Symlinking directories to one of the supported paths, which is fragile and requires manual setup per machine.

Originally created by @nickwood on GitHub (Feb 4, 2026). Originally assigned to: @thdxr on GitHub. Currently, skills are only discovered from a fixed set of hardcoded paths: - .opencode/skills/ - ~/.config/opencode/skills/ - .claude/skills/ / ~/.claude/skills/ - .agents/skills/ / ~/.agents/skills/ This makes it difficult to combine skills from multiple sources (e.g., personal skills + a shared team repo + community skill collections) without resorting to symlink workarounds. Proposed solution: Add a config option to specify additional skill directories: { skill: { paths: [ /path/to/shared-repo/skills, /path/to/community-skills ] } } These would be searched in addition to the existing default locations. Use cases: - Maintaining personal skills separately from team/org shared skills - Using skills from a git repo without symlinking - Distributing skill collections independently from OpenCode config - Easier testing of skills during development Current workaround: Symlinking directories to one of the supported paths, which is fragile and requires manual setup per machine.
yindo closed this issue 2026-02-16 18:10:09 -05:00
yindo commented 2026-02-16 18:10:09 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 4, 2026):

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

  • #8533: Allow custom skills directories via config (similar feature request)
  • #11189: Configurable skills search paths & TUI settings management (comprehensive proposal for the same feature)

The #11189 issue provides additional context with a detailed proposal including JSON configuration and TUI-based management for skills search directories. Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 4, 2026): This issue might be a duplicate of existing issues. Please check: - #8533: Allow custom skills directories via config (similar feature request) - #11189: Configurable skills search paths & TUI settings management (comprehensive proposal for the same feature) The #11189 issue provides additional context with a detailed proposal including JSON configuration and TUI-based management for skills search directories. Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8512
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?