Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
99
100%
Does it follow best practices?
Impact
97%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Tutorial voice, goal-first, concrete steps
First-person plural voice
0%
30%
Goal statement at start
80%
100%
Visible result per step
50%
100%
Narrative expectation phrases
90%
100%
Concrete single path
100%
100%
Minimal explanation
80%
100%
No embedded reference material
100%
100%
No type mixing (explanation)
100%
100%
No 'you will learn' phrasing
90%
100%
Closing accomplishment statement
100%
100%
How-to guides: conditional imperatives, assumes competence
'How to' titles
60%
100%
Conditional imperatives
100%
100%
Assumes competence
90%
100%
Concise and on-target
100%
100%
Allows alternatives
100%
100%
No embedded concept explanations
80%
100%
No tutorial content
100%
100%
Links out for depth
40%
100%
Practical completeness
100%
100%
Two or more guides produced
100%
100%
Reference and explanation type separation
Reference: neutral tone
100%
100%
Reference: consistent patterns
100%
100%
Reference: mirrors API structure
100%
100%
Reference: includes examples
100%
100%
Reference: no how-to content
100%
100%
Explanation: 'About' framing in title
100%
100%
Explanation: design context
100%
100%
Explanation: makes connections
100%
100%
Explanation: admits opinion or perspective
100%
100%
Explanation: no step-by-step instructions
100%
100%
Type separation maintained
100%
100%
40067f1
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.