skills/abdulsamad94/plot-consistency-checker/SKILL.md
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.
npx skillsauth add aiskillstore/marketplace plot-consistency-checkerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Ask the user to provide:
Build comprehensive trackers for:
| Event | Chapter | Time/Date | Duration | Notes |
| ------------------- | ------- | ----------------- | ---------- | ------------- |
| [Event description] | Ch. X | [When it happens] | [How long] | [Key details] |
| Character | Location | Action | Chapter | Consequences |
| --------- | -------- | --------------- | ------- | --------------- |
| [Name] | [Where] | [What they did] | Ch. X | [What resulted] |
| Plot Thread | Introduced | Developments | Resolution | Status |
| ------------- | ---------- | ------------ | ---------- | ------------- |
| [Thread name] | Ch. X | Ch. Y, Z | Ch. XX | Open/Resolved |
| Rule/Law | Established | Used | Broken? | Chapter References |
| ------------------ | ----------- | -------- | ------- | ------------------ |
| [Rule description] | Ch. X | Ch. Y, Z | Yes/No | [List chapters] |
Check the following categories:
Present findings in this format:
# 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?
User: "Can you check my first 5 chapters for consistency? My beta readers said something felt off with the timeline."
Analysis Output:
# 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 as 5 days' journey in Ch. 1) in what appears to be overnight.
**Evidence**:
- Chapter 2, para 15: "As the sun set over Riverhold, Kael mounted his horse and began the long journey to the Capital."
- Chapter 2, para 23: "He made camp that first night under a canopy of stars."
- Chapter 3, para 1: "The next morning, Kael rode through the Capital gates."
**Impact**: Readers who remember the 5-day distance will be confused. Breaks geographical consistency.
**Suggested Fix**:
Option 1: Add a time skip - "After five days of hard riding, Kael finally..."
Option 2: Add magical transport that was established earlier (teleportation, portal, etc.)
Option 3: Revise Ch. 1 to make it 1-2 days' journey instead
---
### 2. Character Knowledge Violation
**Type**: Character Inconsistency / Plot Hole
**Location**: Chapter 4, para 18
**Problem**:
Princess Elara knows about the assassination plot, but there's no scene where she learns this information.
**Evidence**:
- Chapter 4, para 18: "'I know you're planning to kill the king,' Elara said coldly."
- No prior scene shows: someone telling her, her overhearing, or her discovering evidence
**Impact**: Readers will re-read looking for the reveal they missed. Feels like a plot hole.
**Suggested Fix**:
Option 1: Add a scene in Ch. 3 where Elara overhears the plotting
Option 2: Add internal monologue in Ch. 4: "After weeks of piecing together whispers and stolen glances, she finally had confirmation..."
Option 3: Make her accusation a bluff/guess and show her reaction to their guilty faces confirming it
---
## Moderate Issues
### 3. Eye Color Inconsistency
**Type**: Character Physical Description
**Location**: Chapter 1 vs. Chapter 5
**Problem**:
Kael's eye color changes from blue to green.
**Evidence**:
- Chapter 1, para 7: "His blue eyes reflected the ocean."
- Chapter 5, para 12: "She looked into his startling green eyes."
**Impact**: Character description inconsistency breaks immersion.
**Suggested Fix**:
Choose one color and useFind & Replace. Consider unique eye color as character identifier.
---
[etc.]
---
## Timeline Visualization
Day 1 (Chapter 1):
Day 2 (Chapter 2-3):
Day 3 (Chapter 3-4):
Day 4 (Chapter 5):
**Recommendation**: Insert time skip or explain rapid travel.
---
## Unresolved Plot Threads
1. **The Mysterious Informant** (Introduced: Ch. 1, para 15)
- Status: Dangling
- Last Mention: Ch. 1, para 20
- Reader Expectation: This shady character will return or be revealed as important
- Recommendation: Either bring them back in Ch. 6-7 or establish in Ch. 1 they're just a one-time contact
2. **Kael's Sister's Illness** (Introduced: Ch. 2, mentioned in flashback)
- Status: Unresolved
- Last Mention: Ch. 2
- Reader Expectation: This is his motivation, should stay relevant
- Recommendation: Have Kael reference it periodically; maybe he's doing this mission for money to cure her
---
## Priority Fixes (Top 5)
1. **Impossible Travel Time (Critical)** - Major timeline break
2. **Princess's Unexplained Knowledge (Critical)** - Plot hole
3. **Eye Color Change (Moderate)** - Easy fix but noticeable
4. **Unresolved Informant Thread (Moderate)** - Decide if relevant
5. **Missing Motivation (Moderate)** - Why does Kael care about this mission?
User: "I'm writing in first person from Ava's perspective. Can you check if I accidentally head-hopped?"
Analysis Output:
# Plot Consistency Analysis Report - POV Check
## Executive Summary
- **Declared POV**: First Person (Ava's perspective)
- **POV Violations Found**: 3
- **Overall POV Consistency Score**: 7/10
---
## POV Violations
### 1. Character Thought Access Violation
**Type**: POV Violation
**Location**: Chapter 3, paragraph 8
**Problem**:
Narrator reveals Jake's internal thoughts/feelings that Ava couldn't know.
**Evidence**:
> "I watched Jake from across the coffee shop. He seemed nervous, his fingers drumming the table. He was worried I'd say no to his invitation, remembering how his ex had always refused his suggestions."
**Why It's a Problem**:
Ava can't know:
- That Jake is nervous (she can observe behavior but can't confirm internal state)
- What specifically he's worried about
- His memories of his ex
**What Ava CAN Know**:
- Observable behaviors (drumming fingers)
- What Jake tells her verbally
- Her own interpretations and guesses
**Suggested Fix**:
> "I watched Jake from across the coffee shop. His fingers drummed the table—a nervous habit I'd noticed before. Was he worried I'd say no? Maybe he'd dealt with too many rejections before. I decided to put him out of his misery."
(Shows Ava _observing_ and _inferring_, not magically knowing)
---
### 2. Omniscient Narrator Slip
**Type**: POV Violation
**Location**: Chapter 5, paragraph 14
**Problem**:
Narrator provides information about a character not present that Ava couldn't know yet.
**Evidence**:
> "While I was meeting with my editor, Jake was at home finding the letter I'd hidden in my desk drawer."
**Why It's a Problem**:
Ava isn't present for this scene and doesn't learn about it until later (Ch. 7). In first person POV, you can't show scenes the narrator didn't witness unless it's framed as them learning about it later.
**Suggested Fix**:
Option 1: Remove this line entirely; reveal Jake found the letter when Ava discovers it
Option 2: Frame as flashback/retrospective: "I didn't know it then, but while I was meeting with my editor, Jake was at home finding the letter..."
Option 3: Switch to alternating POV (requires full revision to add Jake's first-person chapters)
---
### 3. Impossible Knowledge
**Type**: POV Violation / Plot Hole
**Location**: Chapter 6, paragraph 22
**Problem**:
Ava knows specific dialogue from a conversation she wasn't part of.
**Evidence**:
> "'We need to tell her,' Sarah said to Marcus.
> 'Not yet,' he replied. 'She's not ready.'
> I had no idea they were talking about me, but I'd find out soon enough."
**Why It's a Problem**:
If Ava wasn't there and hasn't been told about this conversation yet, she can't quote it verbatim. The last sentence tries to justify it but doesn't fix the logical impossibility.
**Suggested Fix**:
Option 1: Remove this scene entirely; show Ava discovering later that they'd been discussing her
Option 2: Frame as Sarah telling Ava later: "Sarah later confided in me: 'We had a whole conversation about whether to tell you...'"
Option 3: Make Ava present but hidden: "I froze outside the door when I heard Sarah's voice..."
---
## What's Working Well
✓ Chapters 1, 2, 4, and 7-10 maintain perfect first-person POV
✓ Ava's voice is consistent and distinct
✓ You do a great job showing Jake's feelings through his actions and Ava's interpretations
✓ The internal monologue feels natural and adds personality
---
## POV Best Practices Reminder
When writing first person (Ava's POV), she can share:
- ✓ Everything she directly experiences (sees, hears, smells, touches, tastes)
- ✓ Her own thoughts and feelings
- ✓ Her interpretations and guesses about others ("He seemed angry" not "He was angry")
- ✓ Information told to her by other characters
- ✓ Things she learns about later (if framed as "I later found out...")
She CANNOT share:
- ✗ Other characters' internal thoughts/feelings as fact
- ✗ Scenes she's not present for (unless doing retrospective framing)
- ✗ Dialogue/events she didn't witness and hasn't been told about
- ✗ Information she has no way of knowing
---
## Recommended Reading Order for Fixes
1. Fix Ch. 5, para 14 first (biggest logic problem)
2. Fix Ch. 6, para 22 second (affects later plot)
3. Fix Ch. 3, para 8 last (minor, easy fix)
After generating the report, Claude should ask:
"I've completed the consistency analysis. Would you like me to:
Before Submitting for Analysis:
Using the Analysis:
Before finalizing the consistency report:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.