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

Does opencode actually support finding skills at .claude/skills? #3921

New Issue
Closed
opened 2026-02-16 17:41:56 -05:00 by yindo · 9 comments
yindo commented 2026-02-16 17:41:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @colobas on GitHub (Dec 27, 2025).

Originally assigned to: @rekram1-node on GitHub.

Question

I was looking for where in the code the search in .claude/skills is being enabled, but the only reference I found to the claude directory is this commented out test which makes me think opencode isn't actually looking in .claude/skills folders?

What I'm actually interested is in being able to configure the directory where opencode looks. (e.g. making it .agent/skill rather than .opencode/skill), but that doesn't seem to be possible at the moment?

Originally created by @colobas on GitHub (Dec 27, 2025). Originally assigned to: @rekram1-node on GitHub. ### Question I was looking for where in the code the search in `.claude/skills` is being enabled, but the only reference I found to the claude directory is [this commented out test](https://github.com/sst/opencode/blob/7aecb43e846eea4c383a29bf6a224db909ac474a/packages/opencode/test/skill/skill.test.ts#L104-L131) which makes me think opencode isn't actually looking in `.claude/skills` folders? What I'm actually interested is in being able to configure the directory where opencode looks. (e.g. making it `.agent/skill` rather than `.opencode/skill`), but that doesn't seem to be possible at the moment?
yindo closed this issue 2026-02-16 17:41:56 -05:00
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 27, 2025):

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

  • #6177: Skill discovery doesn't match Claude Code's skills/ directory structure - directly addresses the .claude/skills question
  • #6171: Inconsistency in docs for where to install skills - covers the configuration/directory inconsistency
  • #6013: [FEATURE]: Add Skill Configuration to Config Type - related to configurable skill paths

Feel free to ignore if these don't address your specific case.

@github-actions[bot] commented on GitHub (Dec 27, 2025): This issue might be a duplicate of existing issues. Please check: - #6177: Skill discovery doesn't match Claude Code's skills/ directory structure - directly addresses the .claude/skills question - #6171: Inconsistency in docs for where to install skills - covers the configuration/directory inconsistency - #6013: [FEATURE]: Add Skill Configuration to Config Type - related to configurable skill paths Feel free to ignore if these don't address your specific case.
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@anntnzrb commented on GitHub (Dec 31, 2025):

This is partially addressed by PR #6539 which adds skills.path config for custom directories.

The PR adds custom paths alongside defaults (additive). If you need to disable/replace default paths entirely, that would be a separate feature request.

@anntnzrb commented on GitHub (Dec 31, 2025): This is partially addressed by PR #6539 which adds `skills.path` config for custom directories. The PR adds custom paths alongside defaults (additive). If you need to disable/replace default paths entirely, that would be a separate feature request.
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 31, 2025):

It does read claude skills, for the project and global yep

@rekram1-node commented on GitHub (Dec 31, 2025): It does read claude skills, for the project and global yep
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 31, 2025):

If u wanna add custom dirs, I recommend using: OPENCODE_CONFIG_DIR

@rekram1-node commented on GitHub (Dec 31, 2025): If u wanna add custom dirs, I recommend using: `OPENCODE_CONFIG_DIR`
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 31, 2025):

We could update it to support comma separated values or something but rn thats the cleanest solution I think, cc @anntnzrb

@rekram1-node commented on GitHub (Dec 31, 2025): We could update it to support comma separated values or something but rn thats the cleanest solution I think, cc @anntnzrb
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@anntnzrb commented on GitHub (Dec 31, 2025):

We could update it to support comma separated values or something but rn thats the cleanest solution I think, cc @anntnzrb

#6539 - see usage examples

@anntnzrb commented on GitHub (Dec 31, 2025): > We could update it to support comma separated values or something but rn thats the cleanest solution I think, cc [@anntnzrb](https://github.com/anntnzrb) #6539 - see usage examples
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 31, 2025):

Yeah I was saying instead of adding new configs fields we can just improve the already supported env var that handles this stuff already

@rekram1-node commented on GitHub (Dec 31, 2025): Yeah I was saying instead of adding new configs fields we can just improve the already supported env var that handles this stuff already
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@anntnzrb commented on GitHub (Dec 31, 2025):

Hey @rekram1-node, following up on your suggestion to enhance OPENCODE_CONFIG_DIR with comma-separated values.

Here's what I'm proposing:

Usage

# Single path (backwards compatible)
export OPENCODE_CONFIG_DIR="~/my-config"

# Multiple paths with tilde expansion
export OPENCODE_CONFIG_DIR="~/my-config,/shared/team-config"

Expected Directory Structure

Each path should follow the standard .opencode/ structure:

OPENCODE_CONFIG_DIR="~/my-config,/shared/team-config"
                          │
              ┌───────────┴───────────┐
              ▼                       ▼
   ┌──────────────────┐    ┌──────────────────┐
   │  ~/my-config/    │    │ /shared/team-    │
   │  ├── agent/      │    │ config/          │
   │  ├── command/    │    │ ├── agent/       │
   │  ├── skill/      │    │ ├── command/     │
   │  └── plugin/     │    │ ├── skill/       │
   └──────────────────┘    │ └── plugin/      │
                           └──────────────────┘

Plural forms also work (agents/, commands/, skills/, plugins/).

Questions

  1. Does this match what you had in mind?
  2. Should the paths be loaded in order (left-to-right, later overrides earlier)?
  3. Any concerns with using comma as separator vs path.delimiter (: on Unix, ; on Windows)?

Let me know if this aligns with your vision before I proceed with the implementation.

@anntnzrb commented on GitHub (Dec 31, 2025): Hey @rekram1-node, following up on your suggestion to enhance `OPENCODE_CONFIG_DIR` with comma-separated values. Here's what I'm proposing: ## Usage ```bash # Single path (backwards compatible) export OPENCODE_CONFIG_DIR="~/my-config" # Multiple paths with tilde expansion export OPENCODE_CONFIG_DIR="~/my-config,/shared/team-config" ``` ## Expected Directory Structure Each path should follow the standard `.opencode/` structure: ``` OPENCODE_CONFIG_DIR="~/my-config,/shared/team-config" │ ┌───────────┴───────────┐ ▼ ▼ ┌──────────────────┐ ┌──────────────────┐ │ ~/my-config/ │ │ /shared/team- │ │ ├── agent/ │ │ config/ │ │ ├── command/ │ │ ├── agent/ │ │ ├── skill/ │ │ ├── command/ │ │ └── plugin/ │ │ ├── skill/ │ └──────────────────┘ │ └── plugin/ │ └──────────────────┘ ``` Plural forms also work (`agents/`, `commands/`, `skills/`, `plugins/`). ## Questions 1. Does this match what you had in mind? 2. Should the paths be loaded in order (left-to-right, later overrides earlier)? 3. Any concerns with using comma as separator vs `path.delimiter` (`:` on Unix, `;` on Windows)? Let me know if this aligns with your vision before I proceed with the implementation.
yindo commented 2026-02-16 17:41:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Jan 18, 2026):

Yes that works

@rekram1-node commented on GitHub (Jan 18, 2026): Yes that works
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#3921
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?