MCPInstall

story-review

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.

Installs
675
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/haowjy/creative-writing-skills --skill story-review
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads story-review automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Story Review

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:

  • Editorial review — holistic third-party book-editor pass. What kind of revision does this draft need, and in what order?
  • Developmental edit — structure, promise, causality, pacing, character arc. Is the draft the right shape?
  • Line edit — voice, rhythm, clarity, texture. Does the prose move well?
  • Copyedit — grammar, usage, punctuation, consistency. Is it correct?
  • Proofreading — final surface pass. What slipped through?

Each level has a dedicated resource with method and checklist:

  • resources/editorial-review.md
  • resources/developmental-edit.md
  • resources/line-edit.md
  • resources/copyedit.md
  • resources/proofreading.md

For 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.

FAQ

What does the story-review skill do?

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.

How do I install story-review?

Run npx skills add https://github.com/haowjy/creative-writing-skills --skill story-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/story-review/ (personal) or .claude/skills/story-review/ (project).

Which AI agents can use story-review?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is story-review safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains story-review?

It is published by haowjy in haowjy/creative-writing-skills. It has 675 recorded installs.

More from haowjy/creative-writing-skills

View all →

writing-principles

haowjy/creative-writing-skills

What fiction readers want (reader reward channels) and the specific ways LLM training damages them. Load when drafting prose, critiquing, or diagnosing why a passage feels flat.

Docs & Writing1K installs

creative-writing-craft

haowjy/creative-writing-skills

Craft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.

Docs & Writing788 installs

llm-writing

haowjy/creative-writing-skills

Load before writing or revising human-facing text. Choose words deliberately, ground the piece in the reader's context, and remove default LLM phrasing before the final draft.

Docs & Writing751 installs

writing-staffing

haowjy/creative-writing-skills

Dispatch reference for composing writing teams. Teaches which extra skills to attach, which files to pass, which resources to reference, and when to fan out versus run parallel lanes. Load when staffing a workflow.

Docs & Writing724 installs

story-planning

haowjy/creative-writing-skills

Planning work before prose: creative direction, story-planning, outlining, and story architecture. Load when deciding what should happen or how a story should be structured.

reader-sim

haowjy/creative-writing-skills

Read as a specified first-time reader persona and report the felt experience. Use for skill-only workflows when a draft needs persona-bound reader-response signal instead of analytical critique.

Docs & Writing548 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.