sethshoultes/authors-continuity
skills/authors-continuity/SKILL.md
Check a draft for continuity violations against the project bible. Usage - /authors-continuity <file> [author]. Reads the draft and every bible file; fans out to 1-2 authors; returns flagged inconsistencies - character detail drift (eye color changes, age contradictions), timeline contradictions, voice rule violations, invented-term misuse. Use before sharing a chapter with beta readers or merging it into the main manuscript.
testing
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add sethshoultes/great-authors-plugin authors-continuityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 6:55 PM52.0s1 file scanned
SKILL.md
- name:
- authors-continuity
- description:
- Check a draft for continuity violations against the project bible. Usage - /authors-continuity <file> [author]. Reads the draft and every bible file; fans out to 1-2 authors; returns flagged inconsistencies - character detail drift (eye color changes, age contradictions), timeline contradictions, voice rule violations, invented-term misuse. Use before sharing a chapter with beta readers or merging it into the main manuscript.
/authors-continuity <file> [author]
Audit a draft for continuity violations against the bible.
When to use
- Before sharing a chapter with beta readers — catch the drifts you missed.
- After a long break from a project, when your own memory of the bible is fuzzy.
- When two chapters disagree and you can't tell which one is wrong.
Not for: generic editorial feedback (use /authors-edit); craft gut-check (use /authors-critique).
Instructions for Claude
When this skill is invoked:
-
Parse arguments:
- First positional: file path (required). If missing, ask for a file.
- Optional: author name. If not provided, pick based on the project's genre (from
project.md): fiction → King; nonfiction → McPhee; essay → Didion; speculative → Le Guin; literary/mythic → McCarthy. Default if ambiguous: King.
-
Verify file exists and
.great-authors/exists in its parent directory. If no bible, tell the user/authors-continuityrequires a project bible — run/authors-project-initfirst. -
Dispatch the selected author via the
Agenttool:subagent_type: <author>-persona- Prompt:
CONTINUITY AUDIT MODE. The draft to audit is below. Your job is NOT to edit for craft; it's to catch continuity violations against the project bible. Read these first: - .great-authors/project.md - .great-authors/voice.md - .great-authors/characters/*.md (all character files) - .great-authors/places/*.md (all place files) - .great-authors/timeline.md - .great-authors/glossary.md - .great-authors/scenes/*.md (prior scene cards) - The most recent entry in .great-authors/journal/ (if any) Then read the draft and identify: - CHARACTER DRIFT: any detail about a character that contradicts their bible entry (physical, voice, backstory, relationship). - TIMELINE CONTRADICTION: events placed in sequences that conflict with timeline.md. - VOICE RULE VIOLATION: the draft breaks rules in voice.md (or establishes a new voice rule not yet in the bible). - GLOSSARY MISUSE: an invented term used differently from its glossary definition. - SCENE CONTRADICTION: the draft establishes something that contradicts a prior scene card. Output format: - **Violations found:** N - For each violation, one entry: - **Type:** <CHARACTER DRIFT | TIMELINE | VOICE | GLOSSARY | SCENE> - **Draft says:** "<quote from the draft>" - **Bible says:** "<quote from the relevant bible file>" (or path reference) - **Severity:** high (breaks plot or established fact) / low (probably a minor drift) If no violations, say so in one sentence: "No continuity violations found — the draft is consistent with the bible." Draft to audit: <full file contents>
-
Consolidate. If one author was dispatched, pass through their output with a top-line summary. If two were dispatched (user passed two authors or you auto-picked two for a mixed-genre piece), merge and dedupe the violation list.
-
Output format:
# /authors-continuity on <filename> **Auditor:** <author name> **Violations found:** N **Highest severity:** <high/low> ## Violations ### 1. <type>: <one-line summary> - **Draft says:** "<quote>" - **Bible says:** "<quote>" (`<bible-file>`) - **Severity:** <high/low> ### 2. ... ## Next step (One sentence — which violation to fix first, and whether a journal entry or bible edit is needed to resolve it.) -
Output to stdout. Do not modify the manuscript.
Notes
- The sub-agent will read MANY bible files. This is intentional — continuity demands full context.
- If the bible is sparse (few characters, no scenes yet), the audit will be quick and likely clean.
- If the draft establishes something not in the bible at all (a new character, a new invented term), flag it as "CANDIDATE BIBLE ADDITION" not as a violation. Offer to run
/authors-build-characteror similar. - Fan-out is unusual here — most runs will use one auditor. Multiple only if the user explicitly passes two authors.
Related Skills
sethshoultes/authors-rewrite
documentation
VerifiedTrustedCommunity
Dispatch a named author persona as a sub-agent to rewrite an existing manuscript file from scratch with full bible context. Usage - /authors-rewrite <file> <author>. Use when an existing chapter or scene needs more than a critique pass — when the prose itself isn't working and a clean rewrite by the named author is required. The skill assembles a self-contained brief (bible files, prior/next chapters, architecture beats, voice rules), dispatches the author, and confirms save.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-orchestrate-novel
tools
VerifiedTrustedCommunity
Top-level autonomous workflow for writing a novel end-to-end with the great-authors plugin. Composes existing skills (project-init, build-character, build-place, build-relationship, draft, channel, rewrite, continuity, critique, edit, debate, journal, consolidate) into a multi-phase pipeline with human checkpoints. The human provides direction (premise, genre, characters, voice); the AI orchestrator dispatches author personas as sub-agents to do the work. Use when a user wants the full great-authors pipeline run for them with minimal hand-holding — analogous to great-minds-plugin's agency-* workflows. Usage - /authors-orchestrate-novel, optionally with --phase <N> to run a single phase or --resume to continue from the last checkpoint.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-corpus-critique
data-ai
VerifiedTrustedCommunity
Run ONE editor across MULTIPLE files in parallel, then consolidate into a corpus-level pattern report. Surfaces patterns no per-file critique catches — voice drift, recurring tics, structural failures that only become visible across multiple pieces. Usage - /authors-corpus-critique <author> <path-or-glob> [<path-or-glob>...]. Different from /authors-critique (N authors on 1 file). This is 1 author on N files.
SKILL.mdUpdated Apr 27, 2026
sethshoultes/authors-project-init
tools
VerifiedTrustedCommunity
Initialize the per-project memory bible (.great-authors/) in the current working directory. Creates project.md, voice.md, timeline.md, glossary.md, and empty characters/, places/, scenes/ directories. Use when the user is starting a new writing project (novel, essay collection, long-form nonfiction) and wants author personas to have persistent context across sessions.
SKILL.mdUpdated Apr 25, 2026