[FEATURE] Name-based Skill Dependency Resolution
Resolved 💬 2 comments Opened Jan 22, 2026 by andpush Closed Feb 28, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Skills currently lack a way to reference other skills by name. To compose skills (e.g., extend frontend-design in a custom skill), authors must either:
- Hardcode paths (fragile: can be at user or project level, dependncies on OS)
- Instruct Claude to search multiple possible locations (not reliable)
- Copy the dependency skill's content (violating DRY)
- No way to express error or gracful handling "use this skill if available"
Proposed Solution
Add optional requires or depends field to SKILL.md frontmatter:
name: my-custom-frontend
description: Custom frontend skill with company design system
requires:
- frontend-design # resolved at runtime
- docx # optional: soft dependency
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
Related to https://github.com/anthropics/claude-code/issues/15944
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗