Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Passed 21 of 21 test cases with the skill, and 11 of 21 without it.
and 12 more in the full report
11 fixed11 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When an agent encounters a Red Flag trigger during execution, such as 'I already manually tested it', what exact action must the agent take regarding its written code?
| Checked | Without skill | With skill |
|---|---|---|
| The response instructs the agent to delete the code and start over with TDD. | Missed | Passed |
The instructions your model reads when the skill loads.
| | "Too simple to test" | Simple code breaks. Test takes 30 seconds. | | "I'll test after" | Tests passing immediately prove nothing. | | "Tests after achieve same goals" | Tests-after = "what does this do?" Tests-first = "what should this do?" |
### Create Red Flags List
Make it easy for agents to self-check when rationalizing:
```markdown
## Red Flags - STOP and Start Over
- Code before test
- "I already manually tested it"
- "Tests after achieve the same purpose"
- "It's about spirit not ritual"
- "This is different because..."
**All of these mean: Delete code. Start over with TDD.**
Add to description: symptoms of when you're ABOUT to violate the rule:
description: use when implementing any feature or bugfix, before writing implementation code
Follow the TDD cycle:
Run pressure scenario with subagent WITHOUT the skill. Document exact behavior:
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.