Skip to content
TrustedSkillsbeta
Back to all skills

Story Consistency Monitor

Checked
wordflowlab·vlatest·other·MIT

Ensures narratives remain logically sound and consistent across chapters/sections, flagging contradictions for writers.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wordflowlab/novel-writer-skills --skill story-consistency-monitor -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wordflowlab

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wordflowlab/novel-writer-skills at 5bc9b373ff.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5bc9b373ff
Manifest
templates/skills/quality-assurance/consistency-checker/SKILL.md
Scanned
1 file, 312 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The story-consistency-monitor skill analyzes narrative text to detect contradictions, character inconsistencies, and plot holes. It ensures that details established early in a manuscript remain accurate throughout the writing process.

When to use it

  • Identify factual errors where a character's age or location changes between chapters.
  • Validate that plot points introduced in previous scenes are resolved logically later on.
  • Maintain continuity of specific world-building rules, such as magic systems or technology limits.
  • Review long-form drafts before final editing to catch overlooked discrepancies.

Key capabilities

  • Detects contradictions in character descriptions and backstories.
  • Flags unresolved plot threads or missing logical connections.
  • Tracks consistency of timelines and dates across the narrative.
  • Highlights deviations from established setting rules or tones.

Example prompts

  • "Scan this chapter for any inconsistencies with the character profiles defined in Chapter 1."
  • "Identify any plot holes or unresolved story threads in the last three scenes."
  • "Check if the timeline of events matches the calendar dates mentioned earlier in the book."

Tips & gotchas

This tool is most effective when used on drafts that have already undergone basic structural editing. It relies on clear, explicit details provided in the text; vague descriptions may result in fewer detected inconsistencies.