Template for commands that implement a structured recipe: validate preconditions, then execute numbered steps. Fork this and replace the placeholder content. The 'Context Validation Checkpoints' section is the key pattern, forcing Claude to verify preconditions before starting.
SkillScore88Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆AI Engineer pack
Last verified 10/8/2026
What it changes
Passed 21 of 24 test cases with the skill, and 5 of 24 without it.
Without skill21%
With skill88%
Checks it passed that the model alone missed
The final step is titled Confirm completion.
The final step includes a list of modified files.
The Arguments section explicitly handles $ARGUMENTS[0].
and 28 more in the full report
17 fixed4 passed either way2 still failing1 broke1 errored
Pass-rate lift
+67 pp
Tokens
+4%
Agent turns
0%
Response time
-35%
Model gemini-3.6-flashMeasured 10/8/2026v321 of 25 cases passed with skill · 24 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
I need a structured AI command recipe document for executing safe database schema updates. Please generate a complete command specification that defines clear usage scenarios, mandatory pre-execution sanity checkpoints, step-by-step procedures with validation checks for each phase, standard error handling rules, and argument parsing options.
What was checked, without and with the skill
Checked
Without skill
With skill
The document contains a section detailing scenarios when NOT to apply the command.
Missed
Passed
Context validation checkpoints are formatted as Markdown checkboxes using `* [ ]`.
Missed
Passed
Error handling is presented in a Markdown table with Situation and Response headers.
Missed
Passed
case-01 · gemini-3.6-flash · 10/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md70 linessingle file
Recipe command template
This is a template. Replace all [placeholder] content with your specifics.
When to use
[Describe the exact situation where this command applies]
[Describe when NOT to use it, with a common misuse case]
Context validation checkpoints
Before executing any step, verify all of these are true. If any checkpoint fails, stop and explain why to the user.
[Precondition 1: e.g., "The target branch exists and is up to date with main"]
[Precondition 2: e.g., "No uncommitted changes in the affected files"]
[Precondition 3: e.g., "Required config file exists at path X"]
[Precondition 4: e.g., "Necessary permissions or credentials are available"]
Recipe steps
Step 1: [Action name]
[Clear instructions for this step. Be specific about what to read, what to check, what to write.]
Validation: [How Claude verifies this step completed correctly before moving to Step 2]