check-continuity

Validate chapter alignment with book continuity trackers and generate structured reports.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/bonjohen/tasty --skill check-continuity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-continuity
Source: https://github.com/bonjohen/tasty/tree/main/.claude/skills/check-continuity
Command: npx skills add https://github.com/bonjohen/tasty --skill check-continuity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that chapters and the book's continuity tracker are consistent, cross-referencing timeline data, character states, narrative stages, and objects to surface discrepancies and ensure coherent storytelling across the book.

Core Features & Use Cases

  • Cross-checks chapters against the continuity.md and section outlines to confirm alignment of events and states.
  • Reports inconsistencies, missing entries, and potential narrative gaps, with actionable resolutions.
  • Suitable for authors and editors who need to maintain a consistent narrative arc across chapters.

Quick Start

Check continuity for a specific book and chapter range by providing the book name and the target chapters, for example mybook 40-43.

Frequently Asked Questions about check-continuity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check narrative continuity across chapters of my book?

Narrative continuity is validated by cross-referencing specified chapter files against a continuity tracker and section map to detect timeline, character state, object, and narrative stage discrepancies. You provide the book name and chapter range to generate a structured report of inconsistencies.

What is a continuity tracker and how does it validate storytelling?

A continuity tracker is a document recording timeline data, character states, narrative stages, and objects to ensure coherent storytelling. Validation works by reading chapter files and cross-referencing them against this tracker to surface discrepancies, missing entries, and narrative gaps.

Can I validate character states and timeline data for a specific range of chapters?

Yes, you can validate character states and timeline data for a specific range by providing the book name and target chapters, such as 40-43. The process reads the specified chapter files and compares them against the book's continuity documentation to identify inconsistencies and narrative gaps.

What file formats do I need to set up before validating narrative gaps?

You need to set up markdown files for your chapters, a continuity tracker document, and a section map. Specifically, the validation reads chapter files formatted as chNN.md, a continuity.md file, and a section_map.md file to cross-reference data and report narrative gaps.

What does a structured continuity report include when checking book chapters?

A structured continuity report includes identified inconsistencies, missing entries, and potential narrative gaps found between the chapters and the continuity tracker. It provides actionable resolutions to help authors and editors maintain a consistent narrative arc across the book.