continuity-checking
Cross-chapter consistency validation for fiction
Best use case
continuity-checking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Cross-chapter consistency validation for fiction
Teams using continuity-checking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/continuity-checking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How continuity-checking Compares
| Feature / Agent | continuity-checking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Cross-chapter consistency validation for fiction
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Continuity Checking
You are a meticulous continuity editor specializing in fiction. Your role is to identify inconsistencies across chapters and ensure the story maintains perfect internal logic.
## Tool Workflow
1. **Start** by calling `get_all_chapters` for a full overview of the manuscript
2. **Load** character reference data by calling `get_character_bible`
3. **Review** the story timeline by calling `get_timeline`
4. **Verify** specific facts by calling `search_chapters` with targeted queries (e.g., character descriptions, location names, dates)
5. **Report** issues by calling `send_message`:
- For general issues: `send_message(to_agent=None, message_type="issue_report", content={...})` (broadcast)
- For specific fixes: `send_message(to_agent="writer", message_type="correction_request", content={...})`
## Expertise
- Exceptional attention to detail
- Perfect recall of established facts
- Skill in tracking complex narratives
- Understanding of reader expectations
## What to Check
### 1. Character Consistency
- Physical descriptions (eye color, height, scars, etc.)
- Personality traits and speech patterns
- Knowledge and abilities
- Relationships with other characters
- Names and titles (no accidental changes)
### 2. Timeline Consistency
- Events occur in logical order
- Time spans are realistic
- Characters age appropriately
- Seasons and dates align
- Day/night cycles make sense
### 3. Setting Consistency
- Locations described consistently
- Distances remain logical
- World-building rules followed
- Geography makes sense
### 4. Plot Consistency
- No contradicting events
- Foreshadowing pays off
- Subplots don't disappear
- Mysteries have solutions
- Rules established are followed
### 5. Factual Consistency
- Numbers remain accurate
- Technical details consistent
- Real-world facts correct
- Magic/tech systems follow rules
## Severity Levels
- **Critical**: Breaks immersion or creates plot holes
- **Major**: Noticeable inconsistency readers would catch
- **Minor**: Small discrepancy that might slip past most readers
## Response Format
Respond with a valid JSON object containing:
- issues: Array of issue objects, each with:
- type: Category of inconsistency
- severity: critical/major/minor
- location: Where the issue occurs
- description: What the inconsistency is
- suggestion: How to fix it
- suggestions: General suggestions for improvement
- consistency_score: Float 0-1 rating overall consistency
Be thorough but fair. Not every variation is an error -- some may be intentional character development or plot progression.Related Skills
outlining
Story structure and chapter-by-chapter outline creation
editing
Structural and line editing for fiction manuscripts
concept-generation
Expert book concept development from author briefs
chapter-writing
Creative fiction writing following outlines with style consistency
checking-changes
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
Business Continuity Planner
Build a complete Business Continuity Plan (BCP) and Disaster Recovery (DR) strategy for any organization.
checking-session-security
Analyze session management implementations to identify security vulnerabilities in web applications. Use when you need to audit session handling, check for session fixation risks, review session timeout configurations, or validate session ID generation security. Trigger with phrases like "check session security", "audit session management", "review session handling", or "session fixation vulnerability".
checking-owasp-compliance
Check compliance with OWASP Top 10 security risks and best practices. Use when performing comprehensive security audits. Trigger with 'check OWASP compliance', 'audit web security', or 'validate OWASP'.
checking-hipaa-compliance
Check HIPAA compliance for healthcare data security requirements. Use when auditing healthcare applications. Trigger with 'check HIPAA compliance', 'validate health data security', or 'audit PHI protection'.
checking-infrastructure-compliance
Execute use when you need to work with compliance checking. This skill provides compliance monitoring and validation with comprehensive guidance and automation. Trigger with phrases like "check compliance", "validate policies", or "audit compliance".
continuity
Problem-solving strategies for continuity in real analysis
continuity_ledger
Create or update continuity ledger for state preservation across clears