storyledger bible

    1

    Turn a manuscript or a blank page into a story bible of plain files you own. Every fact drawn from your draft cites file and line, and nothing already recorded is overwritten without your say.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    storyledger bible

    Example session with this skill installed

    I've finished the first three chapters of my fantasy novel in the /chapters folder. Can you build a story bible for the characters and locations mentioned so far?

    • Read your context and instructions
    • Compiled the storyledger bible

    I have analyzed the first three chapters in /chapters using the entity extraction script. I found 4 characters and 2 locations. I have filtered out common nouns and confirmed the following candidates based on the manuscript text.

    Extraction Results

    EntityTypeFirst SeenStatus
    Elara VanceCharacterch1.md:12Proposing file: characters/elara_vance.yml
    KaelenCharacterch1.md:45Proposing file: characters/kaelen.yml
    The Iron SpireLocationch2.md:8Proposing file: locations/iron_spire.yml
    Captain HarlCharacterch2.md:104Proposing file: characters/captain_harl.yml
    OakhavenLocationch3.md:22Proposing file: locations/oakhaven.yml
    MiriCharacterch3.md:56Proposing file: characters/miri.yml

    I also noted a potential conflict: Elara is described as having "grey eyes" in Chapter 1, but "blue eyes" in Chapter 3. I have recorded the Chapter 1 value and added a note about the Chapter 3 discrepancy.

    Next steps

    1. Confirm if Elara and "Lady Vance" are the same person so I can merge their aliases.
    2. Approve the creation of these 6 files in the bible workspace.
    3. Let me know if you want to add any world rules established in these chapters.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Keeping track of character eye colors, world rules, and plot threads across a hundred thousand words is a manual, error-prone chore. This skill automates the construction and maintenance of a story bible, extracting facts directly from your manuscript and storing them in version-control-friendly YAML files.

    What it does

    • Entity extraction reads your draft to identify characters, locations, and named groups.
    • Evidence-based recording logs every fact with a specific file:line citation from your text.
    • Conflict detection flags instances where your draft contradicts itself or your planned notes.
    • Revision syncing checks existing citations against new drafts to find facts that no longer match the prose.
    • Worldbuilding scaffolding generates structured files for world rules, plot threads, and timelines.

    How it works

    1. Build by running the extraction script on your manuscript folder to identify candidates for the bible.
    2. Review the proposed list of names and places to confirm which entities deserve a dedicated file.
    3. Import existing prose notes to merge your creative intent with what is already on the page.
    4. Update entries as you write, ensuring no existing data is overwritten without confirmation.
    5. Check the bible against revised chapters to identify broken citations or narrative drift.

    Frameworks & tools

    This skill uses Node.js (version 18+) for entity extraction scripts. It manages data in a structured workspace of YAML files following a specific schema for characters, locations, and plot events.

    Why this beats prompting it yourself

    Generic prompts often hallucinate details or lose track of specific citations over long contexts. This tool uses a dedicated extraction script and a strict "cite-or-it-did-not-happen" logic to ensure your bible remains a ground-truth record of your manuscript.

    Use cases

    • Build a series bible from a finished trilogy to ensure consistency in a sequel.
    • Track character physical descriptions across a draft to avoid continuity errors.
    • Sync your worldbuilding notes with a revised draft after major plot changes.
    • Look up established facts about minor characters without manual searching.

    Known limitations

    Extraction scripts require .md or .txt formats. Citations are limited to 300 per check before requiring manual reading. Node.js must be available in the execution environment.

    Requires manuscript in .md or .txt format. Node.js 18+ needed for automated extraction. Bible citations are capped at 300 per automated check.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    chapters/**
    manuscript/**
    draft/**
    *.md
    *.txt
    characters/**
    locations/**
    world/**
    plots/**
    world-rules/**
    timeline/**
    continuity/contradictions.md
    Listed7 days ago
    Updated5 days ago

    What's inside

    Frequently Asked Questions

    The skill requires manuscript files in .md (Markdown) or .txt formats. It runs on Node.js (v18+), making it compatible with AI agents that have access to a local or cloud-based terminal environment.

    Every extracted fact includes a specific file-and-line citation from your manuscript. If you change a character's description in a later chapter, the skill flags the original citation as "stale" or "conflicting" so you can choose which version to keep as the ground truth.

    No, the skill uses a "cite-or-it-did-not-happen" logic that prioritizes facts found in your text. While it can import your creative notes, it won't invent new lore or fill in gaps unless it finds supporting evidence in your manuscript.

    You receive the full entity extraction scripts, the structured YAML schema for your bible, and the workspace configuration. This allows your AI agent to build, update, and query your story's data without you having to manually search through thousands of words.

    Because the bible is stored as structured YAML files, you can easily track changes using Git or other version control tools. This makes it ideal for authors who want to see exactly how their worldbuilding evolved alongside their draft history.

    New in Writing & Content