maestro:define-mission-skills

To create custom Mission Control skills, you define a validated SKILL.md file with required YAML frontmatter (name, description, argument-hint) and procedural instructions, then register it in a project or global skills directory for runtime discovery and workflow execution.

A SKILL.md file is used to define and register custom skills in Maestro. It contains YAML frontmatter for runtime lookup, optional dependency declarations, work procedure phases, and specific handoff conditions to return control to the orchestrator during mission execution.

Store project-scoped custom skills in the `.maestro/skills/` directory within your project, and store global skills in the `~/.maestro/skills/` directory. Both locations allow the Maestro CLI to discover and validate your skill definitions during workflow execution.

Validation rules enforce consistency between the skill's filename and its YAML frontmatter name. The system also verifies Maestro CLI availability, checks for directory existence, and requires clear work procedure sections and return-to-orchestrator conditions before successfully registering the skill.

Yes, you need the Maestro CLI installed and available. The skill registration process applies CLI and filesystem prerequisite checks to verify the environment, validate naming consistency, and ensure the skill is correctly structured for mission orchestration.