Feature request: Recursive skill discovery in .claude/skills/

Problem

Skill discovery in .claude/skills/ is not recursive, which breaks a common pattern for sharing skills across projects via symlinks.

Expected Behaviour

Skills should be discoverable at any depth under .claude/skills/, or at minimum follow symlinks to directories containing SKILL.md files.

Current Behaviour

Only skills at .claude/skills/<skill-name>/SKILL.md are discovered.

A symlink like .claude/skills/master -> /path/to/shared/skills/ containing multiple skill directories is not scanned recursively, so none of those skills are discovered.

Use Case

Many organisations want to share skills across multiple projects. A common pattern is:

# Shared skills repository
shared-skills/
├── git-issue/SKILL.md
├── code-review/SKILL.md
└── deploy/SKILL.md

# Project A
project-a/.claude/skills/
└── shared -> /path/to/shared-skills/  # Single symlink to share all skills

# Project B  
project-b/.claude/skills/
└── shared -> /path/to/shared-skills/  # Same symlink

This pattern doesn't work because Claude Code doesn't scan subdirectories.

Current Workaround

Create individual symlinks for each skill:

project-a/.claude/skills/
├── git-issue -> /path/to/shared-skills/git-issue/
├── code-review -> /path/to/shared-skills/code-review/
└── deploy -> /path/to/shared-skills/deploy/

This is tedious and requires updating every project when a new shared skill is added.

Proposed Solution

Either:

1. Recursive scanning: Scan all subdirectories under .claude/skills/ for SKILL.md files
2. Follow directory symlinks: When a symlink points to a directory, scan that directory for skill subdirectories
3. Configurable depth: Allow users to specify scan depth in settings

Option 1 or 2 would solve the use case with minimal complexity.

Environment

• Claude Code CLI
• macOS

🤖 Generated with Claude Code