Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
SkillScore95Maintained
Automatic
◆AI Engineer pack
Last verified 8/21/2026
What it changes
Passed 21 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill95%
Checks it passed that the model alone missed
Recommends the `/refine` command
Recommends the `/fortify` command
Recommends the `/streamline` command
and 3 more in the full report
6 fixed15 passed either way1 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+52%
Agent turns
0%
Response time
-33%
Model gemini-3.6-flashMeasured 8/21/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Our agent pipeline has no error handling for external API failures and records no execution logs for production debugging. Which command addresses error handling and observability?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends the `/fortify` command
Missed
Passed
case-10 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md217 linessingle file
MANDATORY — Context Gathering Protocol
Before applying any workflow guidance, gather context:
Check for Maestro context in the project root
First check .maestro/context.md (v2 layout)
Then check .maestro.md (v1 layout — backward compatible)
If it exists → read it and use the workflow context within
If it doesn't exist → tell the user: "No workflow context found. Run /teach-maestro to set up project-specific context for better results."
Check for decision history (optional)
If .maestro/decisions.jsonl exists → read the last 5 decisions for session continuity
If it doesn't exist → proceed without it (no error)
Minimum viable context (if no .maestro.md):
What AI model(s) are being used?
What is the workflow's primary task?
Are there existing prompts, tools, or agents to work with?
What are the quality/speed/cost priorities?
DO NOT proceed without at least understanding the model, task, and priorities.
Maestro — AI Agent Workflow Mastery
This skill provides the foundational knowledge for designing, building, and maintaining
production-grade AI agent workflows. All Maestro commands build on these principles.
Core Principles
Structure over improvisation — Workflows should be deliberate, not emergent
Constraints are features — Explicit boundaries prevent failure modes
Measure, don't assume — Every workflow needs evaluation, not just testing
Appropriate complexity — Match the solution to the problem, not the ambition
Graceful degradation — Every component should fail safely