maestro-skill-author

Solid

Create, update, or debug maestro built-in skills. Covers SKILL.md frontmatter, reference directory structure, step-file architecture, build-time embedding, naming conventions, alias management, and registry validation. Use when creating a new maestro built-in skill, modifying an existing SKILL.md, adding reference files, debugging skill loading failures, updating the skills registry, or working on the skills full port. Also use when frontmatter validation fails, skills don't appear in skill-list, or reference files fail to load.

AI & Automation 189 stars 21 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Maestro Skill Authoring Guide ## Skill Anatomy Every built-in skill is a directory under `skills/built-in/`: ``` skills/built-in/maestro%3A{name}/ SKILL.md (required -- frontmatter + content) reference/ (optional) {file}.md (reference documents) steps/ (for multi-step skills) step-01-{name}.md step-02-{name}.md ``` The directory name is the URL-escaped skill slug. For built-in `maestro:*` skills, replace `:` with `%3A` on disk while keeping the frontmatter name unchanged. ## SKILL.md Format ### Frontmatter (required) ```yaml --- name: maestro:{slug} description: "When to trigger and what this skill does. Be specific about contexts." argument-hint: "<track description>" --- ``` | Field | Required | Notes | |-------|----------|-------| | `name` | Yes | Must match the logical skill slug; the on-disk directory uses `%3A` instead of `:` | | `description` | Yes | Primary trigger mechanism -- be specific about when to use | | `argument-hint` | No | Shown in `skill-list` output. Bracket notation, not camelCase. | **Frontmatter rules:** - Delimiters are `---` on their own lines (lines 1 and 3+) - Simple `key: value` pairs only -- no multiline values - Quotes are stripped from values (`"value"` and `'value'` both work) - Missing `name` or `description` causes the skill to be skipped during build ### Body Content The body after frontmatter is pure markdown. Structure it for the agent that will read it: ...

Details

Author
ReinaMacCredy
Repository
ReinaMacCredy/maestro
Created
5 months ago
Last Updated
today
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category