Skip to content

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

Closed

Description

@colobas

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?

Activity

  1. github-actions commented on Dec 27, 2025

    @github-actions
    Contributor

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

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

  2. anntnzrb commented on Dec 31, 2025

    @anntnzrb
    Contributor

    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.

  3. rekram1-node commented on Dec 31, 2025

    @rekram1-node
    Collaborator

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

  4. rekram1-node commented on Dec 31, 2025

    @rekram1-node
    Collaborator

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

  5. rekram1-node commented on Dec 31, 2025

    @rekram1-node
    Collaborator

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

  6. anntnzrb commented on Dec 31, 2025

    @anntnzrb
    Contributor

    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

  7. rekram1-node commented on Dec 31, 2025

    @rekram1-node
    Collaborator

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

  8. anntnzrb commented on Dec 31, 2025

    @anntnzrb
    Contributor

    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.

  9. rekram1-node commented on Jan 18, 2026

    @rekram1-node
    Collaborator

    Yes that works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions