review-prose

Installation
SKILL.md

Review Prose

Produce durable technical prose that is concrete, natural, and easy to read, with claims calibrated to the evidence. Preserve the author's meaning, voice, and established technical terms. Use neighboring prose as the style reference where available instructions are silent.

Choose the requested mode

  • Draft: Write from verified source material and the user's constraints.
  • Audit: Identify material problems without rewriting the copy.
  • Revise: Reconstruct weak passages while preserving the author's meaning.

Use draft when the request requires new copy, revise when it asks to change existing copy, and otherwise audit. A request to publish or submit existing copy is not revision authorization. For a revision, change only what improves fidelity, clarity, or naturalness, and do not flatten an intentional voice into generic professional prose.

Review in risk order

  1. Source fidelity: Verify names, links, quantities, attribution, causal claims, consequences, and requested constraints. Preserve code blocks, commands, file paths, identifiers, quoted error text, numbers, and links exactly unless the user requests a change or a verified source requires correction. Distinguish sourced facts, author-provided claims, and inference. Never invent benefits, implementation details, validation, or follow-up work to make the copy sound complete. In a draft, use supported claims and calibrate their certainty to the evidence. In a revision, preserve an author-provided claim when no source contradicts it and report the verification gap outside the copy. When a source contradicts a draft or revision, correct the copy to the sourced fact and report the change outside the copy; never swap wording silently. In an audit, report contradictions and verification gaps without changing the copy.
  2. Active policy: Apply any available user or project instructions, especially their communication, public-copy, draft-file, and external-action rules. When present, those instructions own house style; do not replace them with this skill's preferences.
  3. Reader value: Lead with the result, behavior, or concern. Keep the detail a future reader needs; remove unnecessary process narration and descriptions of obvious layout. Preserve useful source credits, conventions the reader cannot infer, and caveats that affect decisions. Describe current behavior in reference docs and code comments. Keep history that explains a constraint or belongs in an artifact about changes.
  4. Naturalness: Edit structure and cadence only after the copy is true and useful.
Installs
4
Repository
webpro/skills
GitHub Stars
18
First Seen
Sep 23, 2026