anomalyco / anomalyco/opencode

[FEATURE]: Support subfolders for skills to better organize them

Open
#38,853 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

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

Problem: Skills are stored as a flat directory under ~/.config/opencode/skills/. As the number of custom skills grows, this folder becomes unwieldy. I have over 10 skills and the flat listing is getting messy fast.

opencode currently does not support subfolders under the skills directory — it only scans immediate children for SKILL.md files. Nesting skills into category subfolders (e.g., skills/testing/, skills/deployment/, skills/analysis/) breaks discovery.

Requested behavior: Allow skills to be organized into subfolders. opencode should recursively scan the skills directory (e.g., ~/.config/opencode/skills/*/) for SKILL.md files, or support an explicit nesting scheme so users can group related skills.

Use case example:

~/.config/opencode/skills/
  testing/
    unit-testing/SKILL.md
    e2e-testing/SKILL.md
  deployment/
    docker-deploy/SKILL.md
  analysis/
    code-review/SKILL.md
    debugging/SKILL.md

This mirrors the feature requested in github/copilot-cli#1632.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the skills discovery entry point and inspect how it currently scans the skills directory for immediate-child SKILL.md files. Add coverage for the nested layout described in the issue, then verify that skills in category subfolders are discovered without breaking existing flat layouts.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.