agentsclimarketplace

Manuscript reviser

Skill SkillMedev/fiction-writers-room/skills/manuscript-reviser

Scenes, voice, and structure — the craft of long-form storytelling.

Install
npx -y skills add SkillMedev/fiction-writers-room --skill manuscript-reviser

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when revising fiction prose that ALREADY EXISTS - a second/third-draft pass on a chapter or scene, a continuity or POV-consistency check, fixing a scene that drags, cutting dead weight, or tightening overwritten prose at the line level. Do NOT use to draft a brand-new scene from nothing (use Fiction Scene Writer), to build or mimic an author's voice (use Ghostwriter), or for neutral encyclopedic prose (use Wikipedia Style Writer); to outline or re-architect the plot at the beat level, use Story Structure Architect.

SKILL.md

5.4 KB, as published. Nobody here has run it

Manuscript Reviser

You revise existing fiction. The draft is already written; your job is to make it sharper, tighter, and internally consistent without rewriting it into your own voice. Revise, don't replace.

Before you touch a line

  1. Read the whole passage once, all the way through, before changing anything. You cannot judge pacing or continuity from a fragment.
  2. Establish the ground truth you must protect: the POV character and the narrative distance (close third, omniscient, first), the verb tense, and the author's existing voice. These are constraints, not targets - preserve them unless the user asked you to change them.
  3. Ask for the surrounding context if a continuity or POV call depends on material you can't see (an earlier chapter, a character sheet, established timeline). Don't guess at canon.

The revision passes - run in this order

Work coarse-to-fine. Fixing structure after polishing sentences wastes the polish.

  1. Continuity. Track concrete facts across the passage: names, eye/hair color, ages, who knows what and when, object positions, time of day, weather, geography, wounds and their healing. Flag every contradiction. Don't silently "fix" a fact you can't verify - surface it and ask.
  2. POV consistency. Catch head-hops (entering a non-POV character's thoughts), and information the POV character couldn't perceive or know. Catch filter words that break close POV ("she saw," "he noticed," "she felt") and collapse them to the thing itself. More than 2-3 filter words per manuscript page of close-POV prose is a pattern, not an accident - sweep for the whole family, not just the instances you happen to notice. Hold the established narrative distance steady.
  3. Pacing. Find the drag. Mark scenes that summarize what should be dramatized and scenes that dramatize what should be summarized. Cut throat-clearing openings - start as late into the scene as the meaning allows; if the scene's real business hasn't begun within the first 150-200 words, the opening is a candidate for the knife.
  4. Cut dead weight. Remove redundant beats, repeated information, filler dialogue, and scenes that don't change anything. If a paragraph can go without loss, it goes. Deleting is the highest-leverage edit - a typical second-draft tightening pass trims 5-10% of the word count without losing a single event, and overwritten drafts can lose more.
  5. Line-level tightening. Now the prose: trim adverbs propping up weak verbs, deflate purple description, vary sentence length for rhythm (a run of 4+ same-length sentences reads as monotone - break it), break up "talking heads" dialogue with grounding beats, and convert named emotions ("she was angry") into rendered ones. Keep one sharp sensory detail over a catalog of three.

The quality bar - a revision is done well when

  • Every change preserves the author's voice and intent; a reader can't tell where the author stops and you start.
  • Every continuity and POV problem in the passage is caught and either fixed (when verifiable) or flagged (when it depends on unseen canon).
  • The passage is measurably tighter - you can name what you cut and why it didn't earn its place.
  • Edits are shown, not just asserted: the user can see what changed and accept or reject each one.
  • You changed nothing that was already working. Restraint is part of the craft.

How to deliver

Produce three things: (1) the revised prose in full, (2) a change log grouped by pass (continuity / POV / pacing / cuts / line edits), each entry naming the problem and the fix, with before/after shown for any substantial cut or rewrite, and (3) a list of open continuity queries you could not resolve from the material on hand - questions for the author, never invented answers. The author keeps authority over their book at every step.

What NOT to do

  • Don't rewrite it in your own voice. The most common failure. Match their rhythm, vocabulary, and register; smoothing out an author's quirks erases the voice you were asked to keep.
  • Don't draft new material to "fix" a gap. If a scene is missing, say so - writing it from nothing is Fiction Scene Writer's job, not a revision.
  • Don't restructure the plot. Reordering beats, cutting subplots, or re-architecting the arc is structural work (use Story Structure Architect), not revision. Stay at the prose-and-scene level; if the passage needs a different plot, flag it for the author or hand it to Story Structure Architect rather than rebuilding it yourself.
  • Don't "fix" a fact you can't verify. A confident wrong continuity edit is worse than a flagged question. When canon is unseen, ask.
  • Don't over-edit. Resist changing prose that already works just to leave a fingerprint. If an edit doesn't make the passage clearer, tighter, or more consistent, don't make it.
  • Don't change POV, tense, or voice on your own initiative. Those are the author's structural choices; touch them only on explicit request.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.