plot-consistency-checker
Analyzes narrative plot points, timelines, and story events to identify inconsistencies, plot holes, continuity errors, and pacing issues. Use when the user needs help ensuring their story remains logically consistent and well-paced.
What this skill does
# Plot Consistency Checker ## Purpose This skill helps authors maintain narrative consistency by tracking plot points, character actions, timelines, and world-building details. It identifies contradictions, plot holes, and pacing problems that could confuse readers or break story immersion. ## When to Use - User has written multiple chapters and wants to check for continuity errors - User is concerned about timeline inconsistencies - User wants to verify character motivations remain consistent - User needs help identifying plot holes - User requests a pacing analysis - User is revising their manuscript and wants to catch errors ## Instructions ### Step 1: Gather Story Information Ask the user to provide: - **Story Synopsis**: Brief overview of the main plot - **Chapters/Scenes**: The content to analyze (can be full manuscript or specific sections) - **Character List**: Main and supporting characters - **World Rules**: Any magical systems, technology, or world-specific rules - **Timeline**: Story duration and key event dates/times - **Point of View (POV)**: Who tells the story and how (first person, third limited, omniscient) ### Step 2: Create a Story Tracking System Build comprehensive trackers for: #### A. Timeline Tracker ```markdown | Event | Chapter | Time/Date | Duration | Notes | | ------------------- | ------- | ----------------- | ---------- | ------------- | | [Event description] | Ch. X | [When it happens] | [How long] | [Key details] | ``` #### B. Character Action Tracker ```markdown | Character | Location | Action | Chapter | Consequences | | --------- | -------- | --------------- | ------- | --------------- | | [Name] | [Where] | [What they did] | Ch. X | [What resulted] | ``` #### C. Plot Thread Tracker ```markdown | Plot Thread | Introduced | Developments | Resolution | Status | | ------------- | ---------- | ------------ | ---------- | ------------- | | [Thread name] | Ch. X | Ch. Y, Z | Ch. XX | Open/Resolved | ``` #### D. World Rules Tracker ```markdown | Rule/Law | Established | Used | Broken? | Chapter References | | ------------------ | ----------- | -------- | ------- | ------------------ | | [Rule description] | Ch. X | Ch. Y, Z | Yes/No | [List chapters] | ``` ### Step 3: Analyze for Inconsistencies Check the following categories: #### A. Timeline Inconsistencies - Events happening out of order - Impossible timeframes (character travels 100 miles in 1 hour without explanation) - Age/birthday contradictions - Seasonal discrepancies - Day/night continuity errors #### B. Character Inconsistencies - Motivations changing without explanation - Skills appearing/disappearing randomly - Physical descriptions contradicting earlier mentions - Knowledge they shouldn't have (or forgetting what they should know) - Personality shifts that aren't part of character arc - Characters being in two places at once #### C. Plot Holes - Unresolved plot threads (Chekhov's gun fired but never established) - Questions raised but never answered - Easy solutions the characters should have tried but didn't - Coincidences that are too convenient - Missing cause-and-effect connections #### D. World-Building Contradictions - Magic/technology working differently in different scenes - Geography changes (forest becomes desert with no explanation) - Rules established then broken without acknowledgment - Historical events contradicting each other #### E. POV Violations - First person narrator knowing things they couldn't know - Third limited showing thoughts of non-POV characters - Omniscient narrator suddenly not knowing something - Head-hopping mid-scene #### F. Pacing Issues - Too much time on minor events, rushing major ones - Long stretches with no conflict or tension - Too many events crammed into short timeframes - Uneven chapter lengths without stylistic purpose ### Step 4: Generate Consistency Report Present findings in this format: ```markdown # Plot Consistency Analysis Report ## Executive Summary - **Total Issues Found**: [Number] - Critical: [X] (breaks story logic) - Moderate: [Y] (confusing but fixable) - Minor: [Z] (easily overlooked) - **Overall Consistency Score**: [X/10] - **Most Common Issue Type**: [Category] --- ## Critical Issues ### 1. [Issue Title] **Type**: Timeline Inconsistency / Character Error / Plot Hole / etc. **Location**: Chapter [X], pages/paragraphs [reference] **Problem**: [Clear description of the inconsistency] **Evidence**: - Chapter X, para Y: "[Quote or description]" - Chapter Z, para W: "[Contradicting quote or description]" **Impact**: [Why this matters to the reader/story] **Suggested Fix**: [Specific recommendation on how to resolve] --- ### 2. [Next Issue] ... ## Moderate Issues [Same format as Critical] ## Minor Issues [Same format, can be more brief] --- ## Timeline Visualization ``` Week 1: Day 1: [Events] - Ch. 1-2 Day 2: [Events] - Ch. 3 [ISSUE: Character teleports from City A to City B instantaneously] Day 3: [Events] - Ch. 4-5 Week 2: [etc.] ``` --- ## Character Tracking Summary ### [Character Name] **Chapters Present**: [List] **Key Actions**: [Brief list] **Inconsistencies Found**: [X] - Chapter Y vs. Chapter Z: [Description] --- ## Unresolved Plot Threads 1. **[Thread Name]** (Introduced: Ch. X) - Status: Dangling - Last Mention: Ch. Y - Reader Expectation: [What readers will expect resolution of] - Recommendation: [Resolve in Ch. Z or remove setup in Ch. X] --- ## Pacing Analysis ### Chapter-by-Chapter Breakdown | Chapter | Word Count | Events | Tension Level | Pacing | |---------|------------|--------|---------------|--------| | 1 | 3,500 | Setup, inciting incident | Medium | Good | | 2 | 5,000 | Travel, conversation | Low | Too slow | | 3 | 2,000 | Major revelation, action | High | Too rushed | **Pacing Recommendations**: - Chapter 2: Consider cutting 1,000 words of exposition; add minor conflict - Chapter 3: Expand action scene by 1,000 words to give proper weight --- ## World-Building Consistency ### Magic System: [Name] **Established Rules**: 1. [Rule 1] - Ch. [X] 2. [Rule 2] - Ch. [Y] **Violations**: - Ch. [Z]: Character does [action] which violates rule #1 - FIX: Either establish exception or revise action --- ## POV Consistency Check **Declared POV**: Third Person Limited (Character A's perspective) **Violations**: - Ch. [X], para [Y]: Narrator reveals Character B's thoughts - Quote: "[Example]" - FIX: Show Character B's feelings through actions/dialogue only --- ## Positive Observations [List things that are working well] - Timeline for Chapters 1-5 is perfectly consistent - Character X's arc is well-maintained - World rules are clearly established in Ch. 2 --- ## Priority Fixes (Top 5) 1. **[Most critical issue]** - Breaks story logic 2. **[Second most critical]** - Major reader confusion 3. [etc.] --- ## Questions for Author [List ambiguities or decisions the author needs to make] 1. In Chapter X, is [event] supposed to be a dream sequence? Current text is unclear. 2. Character Y seems to change motivation in Chapter Z—is this intentional character development or an error? ``` ## Examples ### Example 1: Fantasy Novel Timeline Issue **User**: "Can you check my first 5 chapters for consistency? My beta readers said something felt off with the timeline." **Analysis Output**: ```markdown # Plot Consistency Analysis Report ## Executive Summary - **Total Issues Found**: 8 - Critical: 2 (breaks story logic) - Moderate: 4 (confusing but fixable) - Minor: 2 (easily overlooked) - **Overall Consistency Score**: 6/10 - **Most Common Issue Type**: Timeline Inconsistencies --- ## Critical Issues ### 1. Impossible Travel Time **Type**: Timeline Inconsistency **Location**: Chapter 2 (para 15) to Chapter 3 (para 1) **Problem**: Kael travels from Riverhold to the Capital (established a
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.