Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
.claude/skills/saffron-health-technical-writing/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-17 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-01 | ✗→✓ | ▲ Improved | -27% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -5% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -10% | 0% |
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.
Other measured skills in the registry, with their headline benchmark lift.