Guides evaluation-driven development (EDD) process for agent skills...
Run evaluation-driven development cycle for agent skills.
Create evaluations BEFORE writing documentation. This ensures skills solve real problems.
Evaluation scenarios are saved to tests/scenarios.md as the final step of /creating-effective-skills workflow.
Measure Claude's performance WITHOUT the skill:
Create just enough content to address the gaps:
REQUIRED: Use the Skill tool to invoke creating-effective-skills before writing any skill content. This ensures proper naming, description format, and structure from the start.
Note: This step requires Claude Code CLI. Skip if using Claude.ai.
REQUIRED: Use the Skill tool to invoke evaluating-skills-with-models with the skill path.
This will:
tests/scenarios.mdAfter evaluation: Document recommended model in skill's metadata.
REQUIRED: Use the Skill tool to invoke improving-skills when observations reveal issues.
Before considering the skill complete:
REQUIRED: Use the Skill tool to invoke reviewing-skills to verify compliance with best practices.
After all reviews pass, output instructions for user to validate in a fresh session:
## Test Your Skill
Run this command in a new terminal to test with a fresh Claude session:
claude --model {recommended_model} "{evaluation_query}"
After testing, paste the output file or result back to this session for final confirmation.
Replace:
{recommended_model}: Model determined in Step 4 (e.g., sonnet){evaluation_query}: A representative query from your evaluationsIdentify gaps -> Create evaluations -> Baseline -> Write minimal -> Model eval (sub-agents) -> Review -> User validation
| Observation | Indicates |
|---|---|
| Unexpected file reading order | Structure not intuitive |
| Missed references | Links need to be explicit |
| Repeated reads of same file | Move content to SKILL.md |
| Never accessed file | Unnecessary or poorly signaled |