Install any skill in seconds. Free to start, no credit card required.
Get Started Free →saffron-health/technical-writing
Guide for writing effective technical documentation, specs, and markdown files.
Passed 19 of 22 test cases with the skill, and 6 of 22 without it.
and 13 more in the full report
14 fixed5 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please rewrite this draft section about running integration tests in our repository. It should explain how to execute the test suite, reference our main architecture doc rather than re-explaining the system architecture, and show the exact CLI commands needed.
| Checked | Without skill | With skill |
|---|---|---|
| Contains no markdown bold syntax | Missed | Passed |
| Specifies language identifiers on fenced code blocks | Passed | Passed |
| References the architecture document without repeating system architecture details | Passed | Passed |
The instructions your model reads when the skill loads.
Assume readers are at least as smart as you, so do not over-explain. State information once and move on.
Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.
Always use relative file paths: docs/testing.md, not /Users/name/project/docs/testing.md.
Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.