Skills
A skill is a written instruction manual that Claude follows for one job, like "turn this
chapter into a narration script". Each one is a folder with a SKILL.md file (the instructions) and
sometimes a small program for the mechanical parts. Together, 12 skills cover the whole path from idea to audiobook.
How a skill works
- You ask"Check chapter 2 for speech flow."
- Claude picks the skillEvery skill has a short description of when to use it. Claude matches your request to it.
- It follows the stepsClaude does the parts that need judgement and runs scripts for the mechanical parts.
- It stops and hands backYou see the result and decide. Nothing goes further without your OK.
Who does what
- Claude judgement: reads, writes, decides what to flag
- Script mechanical: same input, same output, every time
ours written for this project · vendored copied unchanged from rhavekost/author-toolkit (MIT), so they can be updated from the original.
Writing
Stage 0ours
story-seed
A brainstorming partner for the very start. It turns a one-line idea into a set of choices (twists, heroes, endings) and helps the author choose.
A one-line premise→seed.md, with the author's choices, open ideas, rejected ideas and parked ideas kept apart
Claude
Stage 1–5ours
fantasy-novella
The project manager and the main writer. It knows the order of the work, keeps each book's files tidy, and writes the chapters.
An idea, then the story bible and outline→Chapter files (ch01.md …) plus notes on facts, names and progress
Claude
Stage 2vendored
story-structure
Maps where the big turning points of the story should fall, so the middle doesn't sag and the ending lands.
The story bible→outline.md, with every chapter and the turning point it carries
Claude
Stage 1, 4, 5vendored
fiction-workshop
A team of editors in a box. It interviews the author to build the story bible, edits like a professional, and tests the book on a reader who has never seen it.
The author's answers, then the full manuscript→story-bible.md, edit notes, and a fresh-reader report
Claude
Stage 1, 4vendored
character-archetypes
Checks that every important character has a clear, distinct job in the story, such as mentor, rival or gatekeeper.
The character list in the story bible→Notes on each character's role and how to sharpen it
Claude
Stage 4vendored
prose-mechanics
A sentence-level proofreader for style. It finds repeated words, weak verbs, monotonous sentence lengths and other habits that wear on a reader.
Finished chapters→A list of findings, each with where it is and how serious it is
Claude
Stage 3, 4vendored
avoid-ai-writing
Finds and removes the tell-tale habits of AI-generated text, so the prose sounds like a person wrote it.
A chapter→A list of AI-sounding phrases, or a cleaned-up chapter
Claude
Voice
Stage 6ours
speech-flow
Fixes the text so it sounds right when read aloud. A listener can't see commas, italics or where a sentence is heading.
A finished chapter→A table of suggested fixes; once approved, the corrected chapter
ScriptClaude
Stage 7ours
narration-prep
Turns each chapter into a script the voice engine can read correctly, with names spelled out phonetically and pauses written in.
A finished chapter, plus the pronunciation list→A script file (audio/ch01.txt …)
ClaudeScript
Stage 8ours
kokoro-narrate
The narrator. It reads the scripts aloud with a free AI voice that runs on this laptop, with no cloud service.
Script files→One audio file per chapter (audio/ch01.wav …)
Script
Stage 9ours
listen-check
A robot proof-listener. It transcribes the finished audio and compares it with the script, so problems come back as a short list of timestamps instead of 90 minutes of listening.
The chapter audio and its script→A list of moments to listen to (chapter, time, what was expected, what was heard)
ScriptClaude