Manuscript editorial router

Skill dinaf2026-web/manuscript-editorial-suite/manuscript-editorial-router

Genre-agnostic editorial team for novelists — 8 Claude Code skills (publisher critique, continuity, fair-play, prose immersion, KDP listing, canon ledger) driven by an auto-detected per-book profile.

Install

npx -y skills add dinaf2026-web/manuscript-editorial-suite --skill manuscript-editorial-router

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

Routes a broad or ambiguous editorial request to the right pass(es) in the Manuscript Editorial Suite. Use when the ask spans more than one kind of feedback or it's unclear which is wanted — "review my book", "give me editorial feedback", "is this ready", "go over this chapter", "full editorial pass", "what should I check". Picks among manuscript-publisher-critique, manuscript- continuity-audit, manuscript-fair-play-audit, manuscript-prose-immersion-audit, and manuscript-listing-critique, runs them in the right order for the book's genre, and hands off. Does not itself critique, score, or rewrite — it only dispatches.

SKILL.md

5.6 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

Manuscript Editorial Router

Decide which critique pass(es) the request needs, then run them. Do not produce a critique yourself — your output is a routing decision plus the dispatched skill(s). If the request already clearly names one pass, skip the routing prose and run it.

STEP 0 — Resolve the project profile

From the current working directory, walk up the parent folders for .manuscript/profile.md.

Found → read it. Its genre and passes decide which passes are even applicable (e.g. fair-play only for mystery/crime/thriller).
Not found → invoke manuscript-profile-setup to create one, then continue. If the author declines, route with genre-general defaults and say so.

The five passes

Pass	Skill	Use when the ask is about…
Craft & acquisitions	`manuscript-publisher-critique`	whole-story quality, "is it good / would a publisher take this", scoring, an editor's letter
Continuity / canon	`manuscript-continuity-audit`	contradictions of the book's bible, drifted details, internal inconsistency
Mystery logic	`manuscript-fair-play-audit`	clue fairness, plant→payoff, "does the solution hold up" (mystery/thriller only)
Line craft	`manuscript-prose-immersion-audit`	line-level immersion (diagnosis only): "line audit", "is this immersive", "talking heads", info-dumping, filter words
Sales surface	`manuscript-listing-critique`	blurb / back-cover / Amazon description / categories / keywords

Supporting (not a critique pass): manuscript-canon-ledger — the living, versioned canon store the continuity pass reads before auditing. Route directly to it for ledger maintenance: "update the ledger", "record a canon change", "is this canon", "resolve open question", "seed the ledger from book N".

Routing rules

Disambiguate overlapping phrases by object, not verb:
- "would this sell" + a manuscript/chapter → manuscript-publisher-critique;
  - a blurb/description/listing → manuscript-listing-critique.
- "check the plot logic / does it hold up" about clues and the solution → manuscript-fair-play-audit; about overall craft → publisher-critique.
- "did I get the details right / does this break canon" → continuity-audit.
- "line audit / is this immersive / kill the info-dumping" → prose-immersion-audit (line-level, diagnosis only), vs. a macro "is the voice working overall" → publisher-critique's Voice row. A request to rewrite prose is neither — route it to the author's writing/voice skill.
Manuscript vs. listing is the first fork. Selling copy or metadata → manuscript-listing-critique and nothing else. Story content (scene, chapter, outline, manuscript, query) → one of the other four.
Gate by genre. Only run manuscript-fair-play-audit if the profile's genre is a mystery/crime/thriller (or fair-play is in passes). For a memoir, literary novel, or romance with no puzzle, skip it and say why.
Order when multiple passes apply (run sequentially, report each separately):
1. manuscript-continuity-audit — catch canon/consistency breaks first; they cap the craft grade.
2. manuscript-fair-play-audit — if there's a mystery to judge.
3. manuscript-prose-immersion-audit — the line-level craft pass on the scenes.
4. manuscript-publisher-critique — the macro craft/acquisitions read, last, so it can reference the prior findings. manuscript-listing-critique is independent — run it only for listing material.
Broad asks default to a full pass. "Review my book / is this ready / full editorial pass" on a manuscript → continuity → (fair-play if applicable) → prose-immersion → publisher, in that order. For a long manuscript, prose-immersion can sample representative scenes — say which it sampled.
Only one obvious pass? Skip the routing explanation and invoke it directly.
Genuinely ambiguous and consequential? Ask one short clarifying question (e.g. "craft read, canon check, mystery-logic check, line audit, or listing copy?") rather than guessing.

Running a selected pass

After selecting the pass(es), for each one load that skill's SKILL.md and its referenced files, then follow that skill's required output exactly. Do not produce a critique from the router body alone or paraphrase a pass's format — the value is in each skill's own report structure. Run the passes in the order decided above and present each skill's output as its own clearly-labeled section.

Output

Lead with a one-line routing decision — which pass(es), in what order, and why — then load and run them. Example: "This spans continuity and craft → running continuity-audit first, then publisher-critique." Keep the routing note to one or two sentences; the value is in the passes, not the dispatch.