skills/story-review/SKILL.md
Review work after prose exists: editorial review, craft critique, continuity/voice review, copyediting, proofreading, and synthesis of reader-sim signal. Load when diagnosing a draft rather than rewriting it.
npx skillsauth add haowjy/creative-writing-skills story-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Analytical review of existing prose. This skill is for diagnosis, not
rewriting. Keep /reader-sim separate when the task needs a felt first-time
reader experience rather than analytical critique.
Choose the review level before reading. Start big before small unless the caller explicitly asks for a late-stage pass. The edit levels move from structural to surface, and each assumes the levels above it are stable:
Each level has a dedicated resource with method and checklist:
resources/editorial-review.mdresources/developmental-edit.mdresources/line-edit.mdresources/copyedit.mdresources/proofreading.mdFor adversarial craft critique (as opposed to editorial review), load:
resources/prose-critique.md — methodology and focus-area routing.resources/prose-critique/ — deep resources per focus area (structure,
character, voice, prose, continuity).When review incorporates reader-sim data:
resources/reader-sim-signal.md — how to interpret and synthesize
reader-sim output alongside analytical critique.tools
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
development
Load when building a static HTML artifact — single page or multi-page site — to make structured information explorable through layout and navigation.
testing
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
development
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.