Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/subagent-testing
Test skills via TDD in fresh subagents.
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 15 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the primary objective of Phase 3 (REFACTOR) during subagent evaluation of an architecture advice tool?
| Checked | Without skill | With skill |
|---|---|---|
| Focuses on testing anti-rationalization patterns and verifying guardrail effectiveness under pressure | Missed | Passed |
The instructions your model reads when the skill loads.
Test skills with fresh subagent instances to prevent priming bias and validate effectiveness.
abstract:skill-authoring)abstract:skills-eval)Fresh instances prevent priming: Each test uses a new Claude conversation to verify the skill's impact is measured, not conversation history effects.
Running tests in the same conversation creates bias:
Three-phase TDD-style approach:
Test without skill to establish baseline behavior.
Test with skill loaded to measure improvements.
Test skill's anti-rationalization guardrails.
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.