agentleFS
chianglianglinchianglianglin/novel-writer/.claude/skills/novel-review/SKILL.md

novel-review

Skill0 starsChanged 6 months agoMITView on GitHub

Run a four-pass literary review of a chapter — produces a scored editorial report with specific improvement directives, and optionally applies rewrites and saves an improved version.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run a four-pass literary review of a chapter, produce a scored editorial report with specific improvement directives, then optionally apply …

    line 8
  2. Distinctive:

    Run each pass independently.

    line 24
  3. Distinctive:

    Ask: "Should I apply the CRITICAL and IMPORTANT fixes and save a revised version?"

    line 74
  4. Distinctive:

    If no: stop here.

    line 82
  5. Very specific:

    If the revision added any world facts, character details, or themes not already in the wiki, offer to append them.

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Novel Review

Run a four-pass literary review of a chapter, produce a scored editorial report with specific improvement directives, then optionally apply rewrites and save an improved version.

Step 1: Load context

Accept --chapter N or a file path. If no argument, use the most recent chapter in ./output/.

Read:

  • The target chapter file
  • ./wiki/characters.md
  • ./wiki/plot.md
  • ./wiki/world.md
  • ./wiki/themes.md
  • The previous chapter file if it exists (for continuity)

Step 2: Four-pass review

Run each pass independently. For each pass, produce:

  • A score 0–100
  • A list of specific findings with line-level references where possible

Pass 1 — Voice & Prose Evaluate: sentence rhythm and variety, word-level precision, paragraph transitions, overused words or phrases, moments where the prose is especially strong or weak.

Pass 2 — Narrative Coherence Evaluate: does the chapter achieve the goals stated in its brief (the chapter header)? Do characters behave consistently with their wiki entries? Are plot events internally consistent? Does the emotional arc land?

Pass 3 — World-building Consistency Evaluate: do all details (physical, cultural, magical) match ./wiki/world.md? Any contradictions, anachronisms, or facts introduced without wiki backing?

Pass 4 — Pacing & Structure Evaluate: are scene beats well-proportioned? Does the chapter open strongly and close with impact? Does it sag in the middle? Is the chapter-level emotional journey complete?

Step 3: Editorial report

Print this report in full:

╔══════════════════════════════════════════╗
  Novel Review — Chapter [N]
╠══════════════════════════════════════════╣
  Voice & Prose:         [score]/100
  Narrative Coherence:   [score]/100
  World Consistency:     [score]/100
  Pacing & Structure:    [score]/100
  Overall:               [average]/100
╠══════════════════════════════════════════╣
  CRITICAL — must fix:
    • [specific issue with location/line]
    • ...

  IMPORTANT — should fix:
    • [specific issue]
    • ...

  MINOR — nice to fix:
    • [specific issue]
    • ...

  STRENGTHS — keep these:
    • [what's working well]
    • ...
╚══════════════════════════════════════════╝

Step 4: Apply rewrites (ask user)

Ask: "Should I apply the CRITICAL and IMPORTANT fixes and save a revised version?"

If yes:

  • Apply all CRITICAL and IMPORTANT directives to produce a revised chapter
  • Preserve the chapter's voice, characters, and plot events — only improve execution
  • Save the revised version as ./output/chapter-[N]-revised.md (never overwrite the original)
  • Print a brief diff summary: what paragraphs changed and why

If no: stop here.

Step 5: Wiki update (if revision introduced new facts)

If the revision added any world facts, character details, or themes not already in the wiki, offer to append them. Follow the same wiki-append format used by /novel-write.

Step 6: Report

═══════════════════════════════════════════
  Novel Review Complete
═══════════════════════════════════════════
  Chapter reviewed:  chapter-[N].md
  Overall score:     [score]/100
  Revised file:      chapter-[N]-revised.md  (if created)
═══════════════════════════════════════════

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.