Skills: nested skills in skills/*/SKILL.md not discovered

[goffity]

Problem

When a skill uses a skills/ subdirectory to organize sub-skills (each with its own SKILL.md), Claude Code does not recursively discover these nested skills. Only the parent SKILL.md is detected.

Structure

~/.claude/skills/dev-km/
├── SKILL.md                    # user-invocable: false (parent)
└── skills/
    ├── mem/SKILL.md            # user-invocable: true
    ├── td/SKILL.md             # user-invocable: true
    ├── distill/SKILL.md        # user-invocable: true
    ├── commit/SKILL.md         # user-invocable: true
    └── ... (27 sub-skills)

Expected Behavior

Claude Code should recursively discover sub-skills inside skills/*/SKILL.md and register them as invocable commands (e.g., /dev-km:mem, /dev-km:td, or just /mem, /td).

Actual Behavior

Only the parent dev-km skill is listed. The 27 sub-skills with user-invocable: true are not discovered or available as commands.

Current Workaround

A manual install-symlinks.sh script creates individual symlinks for each sub-skill:

ln -s ~/.agents/skills/dev-km/skills/mem ~/.claude/skills/mem
ln -s ~/.agents/skills/dev-km/skills/td ~/.claude/skills/td
# ... for all 27 skills

This is fragile and requires re-running after every skill update.

Suggestion

Support recursive skill discovery, or provide a way for a parent skill to declare its sub-skills directory so Claude Code can automatically register them.

[github-actions]

Found 3 possible duplicate issues:

1. [FEATURE] Recursive skill discovery - scan subdirectories in ~/.claude/skills/ #18192
2. [FEATURE] Recursive skill discovery in ~/.claude/skills/ for skill collections #20805
3. [FEATURE] Add support for subdirectories in skills #10238

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.