create-master-skill

Centralize shared resources like API references and error handling into a reusable master skill. Child skills dynamically load these resources instead of duplicating content, enforcing a DRY architecture across your integration workflows.

A master skill is a centralized resource library that stores shared setup guides, API references, and reusable scripts for integrations. You need one when multiple child skills share the same setup and error handling to prevent content duplication.

Provide the integration name to scaffold the repository structure under 00-system/skills/{integration}-master. The workflow automatically populates SKILL.md templates, references, and validation scripts to prepare the master skill for child skill consumption.

Master skills cannot be loaded directly by users. They are designed exclusively for child skills to reference, enabling progressive disclosure so shared resources are loaded only when a child skill needs them during execution.

Progressive disclosure reduces loaded context by having child skills fetch shared resources from the master skill only when needed. This minimizes execution overhead while maintaining access to centralized API references and error handling protocols.

No, you can scaffold a master skill independently by providing an integration name. It supplies templates and validation scripts to guide planning, research, build, and validation workflows for new integrations before child skills are developed.