storyledger scene drafter
Draft your next scene with the whole story in view. A context packet from your own files (people, places, rules, threads, timeline, the prose just before) and three drafts in your voice, each listing the facts it used.
$10
Works with the AI Agents you already use
storyledger scene drafter
Example session with this skill installed
Draft chapter 4, scene 2 from my beats. Use the current character files for Elias and Sarah. Keep the word count around 1200.
- Read your context and instructions
- Compiled the storyledger scene drafter
I have gathered the context for Chapter 4, Scene 2. I analyzed the characters/elias.md and characters/sarah.md files, current plot threads regarding the "Stolen Seal," and the style guide in STYLE_GUIDE.md.
Scene Drafts for Chapter 4
I have generated three alternative drafts in the drafts/ folder:
- Draft A: Internalized Tension (
drafts/ch4_s2_alt_A.md)
Focuses on Elias's sensory experience and his hesitation to confront Sarah. Higher internal monologue ratio. - Draft B: Direct Confrontation (
drafts/ch4_s2_alt_B.md)
Fast-paced dialogue starting in media res. Minimal description, focusing on the power dynamic shift. - Draft C: Atmospheric Lean (
drafts/ch4_s2_alt_C.md)
Uses the "Heavy Rain" world rule to set the tone, delaying the dialogue until the end of the scene.
---
draftOf: "04-the-docks.md:scene2"
alternative: "A - Internalized Tension"
contextFiles: ["characters/elias.md", "characters/sarah.md", "world/rules.md"]
---
The rain didn't just fall; it claimed the docks. Elias adjusted his collar, the damp wool itching against his throat. Sarah stood by the crane, her silhouette sharp against the grey. She didn't turn when he approached.
"You're late," she said. Her voice had that edge he'd noted in the archives—the one that suggested she already knew the answer to the question she hadn't asked yet.
... [Full Scene Text] ...
**Facts used**
- Elias's nervous habit of adjusting his collar: `characters/elias.md:14`
- Sarah's "edge" in her voice: `characters/sarah.md:42`
- Weather (Heavy Rain rule): `world/rules.md:08`
- NEW: The specific smell of the wet wool (not in bible).
Next steps
- Review the
NEW:tags in the Facts used list to see if you want to add those details to your bible. - Use the command
move-draft --file drafts/ch4_s2_alt_A.mdto merge your preferred version into the manuscript. - Request a revision of Draft B if you want Sarah to be more aggressive.
Connects securely to your tools. The creator never sees your data.
About this skill
Writing the next scene of a novel often feels like a blind leap that leads to continuity errors and inconsistent tone. This skill acts as a focused drafting assistant that builds a comprehensive context packet from your existing manuscript and story bible to produce grounded, high-quality alternatives.
What it does
- Context Synthesis extracts character profiles, location details, active plot threads, and hard world rules into a single packet.
- Continuity Guardrails checks for open contradictions in your files to ensure new prose doesn't break established facts.
- Style Matching analyzes preceding prose for rhythm, diction, and sentence length to mimic your specific authorial voice.
- Fact Citation lists the specific files and line numbers used for every plot point or character detail in the draft.
- Alternative Drafting generates three distinct versions of a scene based on your beat sheet, varying in emotional beat or narrative focus.
How it works
- Identify the Target by locating the specific chapter and scene markers (or beat sheets) you want to transform into prose.
- Build Context via the included Node script which crawls your project folder to gather all relevant backstory and style guides.
- Draft Alternatives which are written to a dedicated
drafts/folder, ensuring your main manuscript remains untouched. - Review Citations to verify which facts were pulled from your story bible and which details are marked as
NEW:inventions.
Frameworks & tools
This skill requires Node.js 18 or later to execute the context-building scripts. It is designed to work with local Markdown-based manuscript structures, character bibles, and timeline files.
Why this beats prompting it yourself
Generic prompts often produce "machine prose" filled with stock metaphors and tidy resolutions. This skill enforces a strict "no-cliché" policy and grounds every sentence in your specific project data, preventing the AI from hallucinating characters or breaking your world's "hard rules."
Use cases
- Turn a rough bulleted beat sheet into 2,000 words of atmospheric prose.
- Draft a difficult conversation from two different character perspectives to see which lands.
- Ensure a new scene respects a complex "hard" magic system defined in your world-building files.
- Resume a story after a long break by automatically summarizing the last three chapters for context.
Known limitations
Large story bibles may be truncated if they exceed word budgets, prioritized by relevance. Manuscripts without clear chapter headings or scene markers may require manual targeting.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Context budgets may truncate long character entries. Requires Node.js 18+. Works best with Markdown files. Unstructured manuscripts may need manual scene markers.
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 buying a skill.
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
Skill works without node, but the helper script saves a lot of tokens.
Permissions
File Scopes