overview

a map of the twelve skills — what each one takes in, and what it writes.

twelve Claude Code skills. each one takes source material of some kind and writes companion material for it — documentation, guides, manuals, summaries, reports.

what usefully distinguishes them is not what they are about, but what they are pointed at: one paper, several sources, a corpus, a person, a room, or nothing yet written.

about one paper

write-paper-guide explains it, to one named reader. write-critical-guide assesses it, and reaches no verdict. write-correspondence-guide places it in the literature around it, and is a provisional draft. write-paper-repairs works out what would fix what the assessment found. write-review-and-repair runs the last two end to end.

the first two are siblings, and the difference is the test for any sentence: if it explains the paper to someone who wants to understand it, that is the reading guide; if it weighs the paper for someone who has to judge it, that is the critical guide.

across several sources

write-topic-guide synthesizes them into one exposition — for when no single source carries it. write-study-guide routes a reader through a corpus that already has the exposition, so its work is selection and triage rather than explanation. write-body-of-work-summary covers one mathematician’s program across their papers.

all three pre-summarize their sources into notes first, and write from the notes. the notes are kept as a deliverable.

original writing

write-pure-math-paper and write-technical-report. both audit their material before writing a word, and in both the audit is a gate: nothing gets claimed that the inventory or the evidence ledger cannot support.

a project, or a room

write-manual documents a project. write-workshop-state-guide reports where live work stands, dated and commit-stamped, on the room’s own confidence ledger.

what they share

third person about the work, always. a guide is not a contribution, and a summary is not a survey. each output is a self-contained directory carrying its own Makefile, its own copy of the converter, and a STYLE.md recording the voice it was written in — so it survives a plugin update and rebuilds anywhere.