manuscript-cinematic-scene-audit
dinaf2026-web/manuscript-cinematic-scene-audit
Claude Code skill: a cinematic blocking & scene-population auditor — reads any manuscript scene like a film director (who's in the room, blocking, camera test, voiceover).
Instalação
npx convez-ai dinaf2026-web/manuscript-cinematic-scene-audit1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
manuscript-cinematic-scene-audit — Claude Code Skill
A cinematic blocking and scene-population auditor for any narrative manuscript. It reads each scene the way a film director reads a screenplay before shooting — tracking every body in the room, every environmental detail a camera would see, all movement and physical continuity, the emotional reactions that would register on an actor's face, and the internal debate a character would voice in voiceover.
The test: after any paragraph, could a reader close their eyes and draw the scene — who's there, where they stand, what the space looks like, and what everyone feels?
It diagnoses and flags; it does not rewrite prose.
Runs standalone or as part of the suite. It works on its own — if there's no
.manuscript/profile.mdand the suite'smanuscript-profile-setupskill isn't installed, it simply asks you for the POV character, cast, and any special-trait characters (or audits straight from the page). For the full multi-pass workflow, install the Manuscript Editorial Suite.
What it catches
- Scene population — characters who vanish without exiting, appear without entering, or are forgotten while others interact ("did we forget anyone?").
- Blocking & movement — teleporting characters, lost positions, impossible simultaneous actions, untracked navigation for characters with spatial/mobility/ sensory traits, dropped animal characters.
- Environment on camera — floating-void scenes with no established space; a named setting that isn't actually present.
- Emotional register — reactions a camera would need that aren't on the page; emotions named in narration but not shown in body/face/behavior.
- The voiceover test — decisions, suspicions, and inner conflict the POV character should be processing but isn't.
Output is a per-scene audit + a pass summary with STOP / FIX / NOTE severities.
How it knows your book
On run it walks up from your working folder for .manuscript/profile.md (the
Manuscript Editorial Suite profile). From it the
skill pulls the POV character(s), the cast, and any characters with special spatial,
mobility, sensory, or non-human traits to track. No project is hard-coded — if
there's no profile, it audits from what's on the page and says so.
Install
# Windows (PowerShell)
Copy-Item .\manuscript-cinematic-scene-audit "$env:USERPROFILE\.claude\skills" -Recurse -Force
# macOS / Linux
cp -r manuscript-cinematic-scene-audit ~/.claude/skills/
Then ask Claude: "cinematic pass on chapter 3", "who's in the room in this scene?", or "read this like a director."
Part of a suite
This is one pass in the Manuscript Editorial Suite (continuity, fair-play, prose-immersion, publisher, listing). It runs standalone, or alongside the others via the suite's router.
Related repos
- manuscript-editorial-suite — the full editorial team this pass belongs to.
- manuscript-editorial-router — the 6-pass router that dispatches to this pass.
- manuscript-editorial-suite-plugin — install everything as one Claude Code plugin.
Author
License
MIT