child-skill

You can expose smaller sub-skills within a larger skill by storing them in subdirectories. This hierarchical organization promotes modular design and allows parent workflows to discover, load, and compose these nested skills for extended capabilities.

Parent skill discovery and composition works by referencing a subskill's subdirectory path during activation. The framework reads the SKILL.md frontmatter at the root to identify the subskill, then loads any optional scripts, references, and assets directories automatically.

Yes, a SKILL.md file with frontmatter containing a name and description is required at the root to activate nested skills. This metadata-driven entry enables lightweight activation and allows the framework to recognize and load the subskill.

To invoke a child skill from a parent workflow, reference its subdirectory path and describe your task. This lightweight activation triggers the framework to load the skill along with its optional scripts, references, and assets directories.

During nested skill activation, the framework loads optional scripts, references, and assets directories if they exist. These directories provide additional processing logic and supporting materials for the subskill alongside the required SKILL.md frontmatter.

Use nested skills when you need to structure smaller sub-skills within a larger skill to promote reuse across projects. This pattern is ideal for hierarchical organization where parent skills require extended capabilities through modular composition rather than maintaining duplicated logic.