Skip to content

[FEATURE]: Recursive skill discovery + multi-skill selection in TUI #21495

Closed as not planned

Description

@Flussen

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Feature Request: Recursive skill discovery and multi-skill selection

Problem

  • The skills command only discovers skills at the root level (no recursive lookup).
  • Only a single skill can be selected per request.

Use Case

Projects with structured skill directories:
project-a/skills/backend/auth.md
project-a/skills/backend/database.md
project-b/skills/frontend/ui.md

  • Nested skills are not detected
  • It is not possible to combine skills (e.g. auth + database)

Proposal

  1. Recursive discovery

    • Load skills using recursive directory scanning (/skills/**/*.md)
  2. Multi-skill selection

    • Allow selecting multiple skills in a single request:
      /use auth,database

Expected Behavior

  • skills lists all skills recursively
  • Multiple skills can be selected and applied in one request

Considerations

  • Context/token limits when combining skills
  • Conflict resolution between skills

Question

Would you accept:

  1. Recursive skill loading as a first step
  2. Multi-skill support as a follow-up (separate PRs)

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Apr 8, 2026
  2. assigned and unassigned on Apr 26, 2026
  3. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on May 3, 2026
  4. buildgreatthings commented on Jun 3, 2026

    @buildgreatthings

    +1 to this

  5. a-peleshok commented on Jun 3, 2026

    @a-peleshok

    Seconded!

  6. WywySenarios commented on Jun 17, 2026

    @WywySenarios

    A source-code level analysis of the repo would suggest that recursive skill discovery is already implemented (but not in a way that will match your skills).

    V1 (I think this is what is actively being used right now):

    const EXTERNAL_SKILL_PATTERN = "skills/**/SKILL.md"
    const OPENCODE_SKILL_PATTERN = "{skill,skills}/**/SKILL.md"
    const SKILL_PATTERN = "**/SKILL.md"

    V2:

    .glob("{*.md,**/SKILL.md}", { cwd: directory, absolute: true, include: "file", symlink: true, dot: true })

    These snippets are from commit 4ed4f749e644ffb5b279fb30b7b915e743d80142 , the commit used for building v1.17.7 .

    As to why it is implemented this way, I have previously seen other people use files not named SKILL.md to denote docs related to a skill. See this.

    Note: I'm not an OpenCode contributor. My own PRs/issues have gone ghosted. Maybe I've been flagged as AI?

  7. X6TXY commented on Jun 18, 2026

    @X6TXY

    I think recursive discovery and multi-skill selection are two separate things.

    Recursive discovery may already be partially implemented depending on the expected SKILL.md structure.

    The main UX pain for me is multi-skill selection from /skills.

    Instead of typing:

    /use auth,database

    I think a better UX would be:

    /skills

    Then:

    • Space toggles skills
    • Enter applies selected skills
    • Prompt shows [2 skills selected]
    • Selected skills are injected as context on submit
    • Selection clears after submit

    This solves the real use case: applying multiple skills to one prompt without chaining slash commands manually.

  8. github-actions commented on Aug 18, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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