maestro-skill-author

Create or repair Maestro built-in skill definitions with validated SKILL.md frontmatter and registry rebuilding.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-skill-author-leonardo-corte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-skill-author
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.claude/skills/maestro-skill-author
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill maestro-skill-author-leonardo-corte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill authoring guide solves confusion and build failures when creating or updating Maestro built-in skills—especially when skills don’t load, don’t appear in skill lists, or reference files fail to embed.

Core Features & Use Cases

  • Correct SKILL.md authoring: Define required frontmatter fields (name, description) with the proper on-disk slug encoding and validation rules.
  • Reference architecture guidance: Organize supplemental content in reference/ files and multi-step reference/steps/step-N-* files without breaking loader expectations.
  • Build-time embedding + registry validation: Ensure the generated registry embeds skill content correctly by rebuilding and following naming/alias/deprecation requirements.

Quick Start

Use this guide to create or fix a Maestro built-in skill by editing the root SKILL.md frontmatter and reference files, then run the required build step so the skill appears in maestro skill-list.

Frequently Asked Questions about maestro-skill-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Maestro skill not appear in the skill list after building?

Maestro skills fail to load when SKILL.md frontmatter is missing required fields or uses incorrect URL-escaped directory naming. Rebuilding the skill registry after fixing the on-disk slug encoding and validation rules ensures the skill appears in maestro skill-list.

How do I structure reference and step files for multi-step workflows in Maestro?

Multi-step workflows in Maestro require organizing supplemental content in reference/ files and naming step files as reference/steps/step-N-* to meet loader expectations. Consistent file naming conventions ensure correct embedding and discovery during the skills build.

What frontmatter fields are required for a valid Maestro built-in skill definition?

Valid Maestro built-in skills require the name and description fields in the SKILL.md YAML frontmatter. Strict formatting rules and correct on-disk slug encoding must be applied before rebuilding the skill registry to pass validation.

How do I fix reference files failing to embed during the Maestro skills build?

Reference files fail to embed when directory naming is not URL-escaped correctly or step file naming conventions are broken. Correct the SKILL.md frontmatter formatting and reference architecture, then run the required build step to update the generated registry.

Do I need to run a build step every time I update a Maestro skill definition?

Yes, a required build step must be run after editing SKILL.md frontmatter or reference files. This rebuilds the skill registry, embeds the updated content correctly, and makes the skill discoverable during the maestro skill-list execution.