Skip to content
TrustedSkillsbeta
Back to all skills

Story Check

Checked
bybren-llc·vlatest·writing·MIT

Story Check analyzes your narrative for consistency, plausibility, and potential plot holes, ensuring a smoother, more engaging read.

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 bybren-llc/story-systems-template --skill story-check -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

bybren-llc

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 bybren-llc/story-systems-template at 4a9e30c641.

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

Scanned
4 files, 533 lines
Copies in repo
2 — all of them scanned
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

What it does

The story-check skill analyzes narrative text to identify potential inconsistencies or areas needing improvement. It helps ensure internal logic and coherence within a story, flagging issues related to character actions, plot progression, and worldbuilding details. The tool is designed for writers seeking feedback on their creative work.

When to use it

  • Reviewing drafts: Use story-check after completing a draft of a short story or novel chapter to catch overlooked errors in logic.
  • Character consistency checks: Verify that character actions and motivations align with established personalities throughout the narrative.
  • Worldbuilding validation: Ensure details about the fictional world remain consistent and avoid contradictions.
  • Plot hole detection: Identify potential gaps or inconsistencies in the plot's progression.

Key capabilities

  • Narrative analysis
  • Consistency checking
  • Logic verification
  • Character action assessment
  • Worldbuilding detail validation

Example prompts

  • "Analyze this story excerpt for any logical inconsistencies."
  • "Check if character X’s actions in chapter 3 align with their established personality."
  • "Verify the consistency of the magic system rules described in these paragraphs."

Tips & gotchas

The skill's effectiveness depends on the clarity and detail provided within the narrative text. It is best used as a supplementary tool alongside human review, not a replacement for it.