storyledger structure
Your book's shape on one page. Chapter lengths, POV balance, tension, where each theme and thread lives and goes quiet, how chapters open and close, and what the draft does differently from your outline.
$10
Works with the AI Agents you already use
storyledger structure
Example session with this skill installed
Perform a full structural edit on the manuscript in the /drafts folder. Check against the outline in outline.md and track the "Inheritance" plot thread.
- Read your context and instructions
- Compiled the storyledger structure
I have completed a full structural edit of the manuscript in /drafts. I ran scan-structure.js across 24 chapters and scan-presence.js to track the "Inheritance" thread using the keywords: will, lawyer, estate, uncle.
StoryLedger Structure Report
Mode: Full Structural Edit
Word Count: 82,400
POV Share: Elias (62%), Sarah (38%)
| Chapter | Word Count | POV | Tension | Hook | Closing |
|---|---|---|---|---|---|
| 1 | 3,200 | Elias | 4 | Action | Question |
| 2 | 4,100 | Sarah | 3 | Atmosphere | Sleep |
| 3 | 2,800 | Elias | 6 | Dialogue | Revelation |
| 4 | 3,500 | Elias | 5 | Character | Trailing |
Key Findings
S-001: Sagging Middle. Tension ratings for Chapters 10 through 14 show a flatline at 2/10. These chapters focus heavily on travel with no progress on the "Inheritance" thread.
S-002: POV Gap. Sarah is absent from Chapter 8 through Chapter 15 (approx. 22,000 words). Consider inserting a Sarah POV scene in the Chapter 12 slot to maintain her arc.
S-003: Thread Resolution. The "Inheritance" thread (tracked keywords: will, estate) goes quiet after Chapter 18 and has no presence in the finale.
S-004: Cliche Hook. Chapter 2 opens with a weather description (cliche_weather). Recommend starting with Sarah's reaction to the letter instead.
Next steps
- Review the proposed
purposeandtensiontags for Chapters 10-14 and approve writing them to frontmatter. - Review the
Inheritancekeyword list; I suggest adding "attorney" and "safe-box" for better tracking. - Open
structure/report.mdto see the full sparklines and plan-vs-draft comparison.
Connects securely to your tools. The creator never sees your data.
About this skill
Novelists and editors often struggle to see the "forest for the trees" when finishing a long manuscript. You can easily miss a sagging middle, a dropped plot thread, or a POV character that disappears for eighty pages. StoryLedger Structure provides a developmental edit that maps your book's shape on a single page, identifying structural flaws before you start your next draft.
What it does
- Pacing Analysis generates sparklines for chapter lengths and tension levels to visualize the book's flow.
- POV Monitoring calculates POV share and detects gaps where specific characters go quiet for too long.
- Thread Tracking maps themes and plot threads across chapters to identify unresolved arcs or missing motifs.
- Hook Auditing flags repetitive chapter openings or weak closings, including cliches like waking up or weather descriptions.
- Outline Comparison identifies discrepancies between the draft and the original plan, flagging moved or missing scenes.
How it works
- Manuscript Scan identifies chapter files or splits a single-file manuscript based on headings.
- Structural Measurement runs scripts to quantify word counts, dialogue percentages, and narrative perspective.
- Presence Mapping tracks specific keywords and character aliases to visualize where plot threads live and die.
- Report Generation produces a comprehensive
structure/report.mdwith stable issue IDs, sparklines, and cited developmental entries.
Frameworks & tools
This skill uses Node 18+ to run scanning scripts (scan-structure.js and scan-presence.js) and outputs standard Markdown reports compatible with GitHub-flavored Markdown.
Why this beats prompting it yourself
Generic prompts often lose track of long-range dependencies in 80k-word manuscripts. This tool uses specialized scripts to extract hard data on length, presence, and dialogue, ensuring your developmental feedback is grounded in math rather than just a shallow read of the final chapters.
Use cases
- Auditing a first draft to find where the narrative tension flats out.
- Ensuring a secondary plot thread is consistently developed throughout the middle chapters.
- Balancing screen time between multiple protagonists in a complex ensemble cast.
- Identifying "throat-clearing" chapters that fail to advance the story or establish a hook.
Known limitations
Dialogue detection may struggle with straight single quotes lacking punctuation. Designed for English-language manuscripts. Scene detection requires specific markers or visible breaks like *** to be accurate.
English only. Dialogue detection may misread straight single quotes without punctuation. Split-file manuscripts preferred over one-file books for chapter-level accuracy.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
File Scopes