writing
Installation
SKILL.md
Writing
Infer what the prose needs from the request — never ask which mode:
- Existing draft → revise, copyedit, or diagnose. Load
references/revising.md. - New piece → structure, draft, or persuade. Load
references/drafting.md. - Genre identifiable — memo (PRD/RFC), technical doc, talk/pitch, narrative? Also load
references/genres.md.
Core principle: serve a named reader, not taste. Critique: every finding names a concrete reader, the cost it inflicts ("a scanner can't find the ask"), and a fix; a preference-only note is labeled preference or dropped. New work: decide what the reader needs before polishing how it reads — most weak writing is a structure or audience problem wearing a sentence-level disguise.
Invariants
- Narrative honesty — never let persuasion bend facts. Apply narrative or persuasive shape only where the tension is real: no invented stakes, villains, or crises; a reversal must reflect an actual change of fortune; "because of that" must reflect actual causation. Before any dramatic beat, ask: is this tension already in the material? If not, cut the beat. Genuinely additive content gets answer-first structure, not a forced arc.
- Voice guard — tightening is triage, not dogma. Keep hedges that encode calibrated uncertainty ("we think X" ≠ "X"); keep deliberate rule-breaking that aids clarity; a cut that changes meaning or register is offered with the trade-off named, never imposed. If every writer comes out sounding identical, the edit failed.
- Report a before/after word ratio on every tightening pass.