Fiction Forge Cold Read — Novel Continuity Audit

    1

    Read your novel in order with a persistent continuity ledger. Find timeline, character-knowledge, and object-custody errors without rewriting your prose.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Fiction Forge Cold Read — Novel Continuity Audit

    Example session with this skill installed

    Use Fiction Forge Cold Read on this complete, synthetic three-chapter demonstration. Assess only the text below, in order. This is a simple travel story with no magical movement of objects. Leave the prose unchanged and return the charter, ledger, issue log, batch report, and final verdict in this chat; no file tools are available. The line numbers below are source locators.

    Chapter 1 — The Chest

    1. At dawn on Monday, Mara placed the only brass key inside the iron chest and sealed its lid with wax.
    2. The chest stayed in her locked cottage. She and Ivo left and did not return.
    3. “The gate is one full day's walk away,” Ivo said.
    4. They walked until sunset and slept beside the road.

    Chapter 2 — The Gate

    1. At dawn on Tuesday, Mara and Ivo reached the gate.
    2. Mara took the same brass key from her pocket and unlocked it.
    3. Beyond the gate, a bell rang beneath the earth.
    4. “We'll find its keeper,” she said.

    Chapter 3 — The Bell

    1. That afternoon, they followed the sound into a cellar.
    2. An old woman stood beside a small bronze bell.
    3. “I ring it for travelers,” she told them.
    4. Mara thanked her and went back to the road with Ivo.
    • Read your context and instructions
    • Compiled the fiction forge cold

    Illustrative assessment of the complete synthetic example above.

    Charter

    Assessment-only cold read of the complete three-chapter synthetic demonstration, in supplied order. Source revision: the text in this request; locations use its supplied chapter/line numbers. Reader: a first-time reader of a simple travel story. Seed: no magical object movement, as specified by the author. Reader mode: first-time assessment using only the supplied text and author constraints. One batch covers all 12 numbered lines. No manuscript edits or local file writes were performed.

    Reader ledger

    NEXT: COMPLETE — supplied Chapters 1–3, all 12 numbered lines.

    SectionRecorded state and evidence
    CoverageChapters 1–3 fully read; no missing or partial chapters in the supplied demonstration.
    Position / clockMonday dawn: cottage (1:1). Monday sunset: roadside camp (1:4). Tuesday dawn: gate (2:1). Tuesday afternoon: cellar, then road (3:1–4). No supported timeline contradiction.
    PromisesP1: find the underground bell's keeper (2:3–4); paid by the woman beside the bell who says she rings it (3:2–3). No unresolved explicit promise at this ending.
    Character knowledgeMara and Ivo encounter the bell together (2:3). They hear the woman's account together (3:1–3). Her stated purpose is a dialogue claim, not independently verified world history.
    Prop custodyBrass key: placed in sealed chest (1:1), which remains at cottage (1:2); inexplicably in Mara's pocket (2:2). Preserve both observations as conflicting state. Bronze bell: beside woman in cellar (3:2).
    Already explainedKey storage and cottage departure (1:1–2); bell and search for keeper (2:3–4). No supported redundant exposition.
    PROTECTNo intentional ambiguity or motif specified. Do not invent a hidden magical transfer to explain the key.
    Questions / dismissed concernsTravel duration: dismissed as an issue. Walking for a day and reaching the gate the next dawn after a roadside sleep is compatible with the text. The small mystery of the bell receives an on-page answer.
    Batch verdictClear travel sequence and a compact setup/payoff. One object-custody contradiction interrupts trust.

    Issue log

    The following entry uses the source's supplied chapter/line numbers:

    CR-001 | 2:2 | BLOCKER | CONT | “Mara took the same brass key from her pocket and unlocked it.” | I flipped back to 1:1–2: the key was sealed in a chest left at the cottage, and the travelers did not return. The same key now appears in her pocket without a supported transfer. | Establish that Mara takes the key before departure, or revise the earlier storage event so its later use is consistent. | SCENE

    Batch 01 report

    Chapter 1: CLEAN within the checked scope. Establishes the object state and travel schedule clearly. The key becomes a fact to carry forward, not yet a defect.

    • Chapter 2: CR-001 breaks object continuity. The underground bell provides a clear reason to keep reading.

    Chapter 3: CLEAN within the checked scope. Identifies the keeper and answers the immediate question raised at the gate.

    Reader response: I would continue to the cellar because the bell is a concrete curiosity, but the key's unexplained appearance makes the gate opening feel unearned.

    Ledger checkpoint: All sections updated; exact coverage recorded; NEXT marked complete for this demonstration. No part boundary needs a separate seam assessment.

    Final verdict

    One supported continuity defect: the key's custody. Preserve the economical journey and the bell's clear setup/payoff. The supplied timeline is coherent. There is no evidence here for broad claims about voice quality, novel-scale pacing, or AI authorship.

    Ranked findings

    CR-001 — BLOCKER / SCENE: Repair the key transfer or earlier storage event, then re-read the departure and gate scenes together. No other active findings; no duplicates, fixes, or retractions.

    This is the complete assessment of the supplied miniature, not a claim about an unseen novel. The source remains unchanged. All notes are returned here; none were saved to disk.

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

    About this skill

    A character knows a secret they never learned. A journey takes three days in one chapter and one night in another. An important object changes hands without a scene showing it. These are the problems a chapter-by-chapter pass can miss.

    Fiction Forge Cold Read guides your agent through a sequential manuscript read with a rolling record of what happened, when, who knows it, and what the reader is still waiting to see resolved.

    What you get

    • A reader charter and coverage record, so you know exactly what was assessed.
    • A persistent ledger for timelines, character knowledge, object custody, and promises, with a resume marker for later sessions.
    • An append-only issue log with source quotes, locations, reader impact, severity, and a suggested repair direction.
    • Batch reports that record strengths and chapters with no supported findings.
    • A final editorial verdict and prioritized, deduplicated findings.

    How it works

    Your agent reads the manuscript in order and carries the ledger forward. It checks suspected contradictions against earlier evidence, separates character beliefs from established facts, and preserves deliberate ambiguity and motifs.

    The default is assessment only. Your manuscript stays unchanged. Pattern counts are not treated as proof of AI authorship.

    Optional MCP integration

    The skill explains when to use fiction-forge's five MCP context tools and when their future-chapter or outline information would spoil the cold read. The MCP server is optional and separately configured. The core read requires no Python packages, API key, or network access.

    Requirements and limits

    Use an agent with access to your manuscript and persistent notes. Markdown or plain text is recommended; other formats need the host's extraction tools. Chat-only agents can assess supplied excerpts and return notes but cannot save files themselves. Your chosen model/provider costs still apply. No guarantee of finding every error or of compatibility with every agent.

    The author's official companion skill for the open-source fiction-forge toolkit. Source, setup, and methodology: https://github.com/geobond13/fiction-forge

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 5 days ago

    • Free to download with an account

    Listed5 days ago

    What's inside

    Frequently Asked Questions