child-skill

Packaging a reusable workflow in a subdirectory involves encapsulating a focused capability in a self-contained directory. You must include a valid SKILL.md frontmatter entry with a name and description for proper discovery and activation.

A nested skill is a specialized workflow isolated in its own subdirectory for clean reuse. You need one when a parent workflow requires a small, dedicated helper to perform a clearly scoped job without mixing concerns.

Yes, a valid SKILL.md frontmatter entry with a name and description is required for discovery and activation of a subdirectory skill. This ensures the nested skill unit can be properly identified and invoked.

To handle a specific task without mixing concerns, invoke the nested skill from the parent workflow to perform the clearly scoped job. Ask the assistant to use this skill to handle the nested task in the child skill directory.

Yes, the isolated subdirectory skill works with parent workflows as a self-contained helper. The parent workflow can invoke this skill when it needs a contained helper to perform one clearly scoped operation.