publishing
This skill should be used when the user asks to "self-publish", "publish my book", "ISBN", "copyright page", "book metadata", "BISAC", "keywords", "KDP", "IngramSpark", "Draft2Digital", "go wide", "Kindle Unlimited", "print interior", "trim size", "paperback", "ebook", "EPUB", "cover wrap", "spine width", "pricing", "launch plan", "ARC team", "advance readers", "newsletter", "reader magnet", "Amazon ads", "BookBub", "rights", "foreign rights", "audio rights", "film rights", "publishing contract", or wants to take a finished manuscript through production, distribution, launch, and rights management. It owns contracts and rights sales; NOT for permission to quote lyrics, epigraphs, or other material in the book (use editorial-review).
danjdewhurst · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add danjdewhurst/story-skills --skill publishingAbout this skill
name: publishing description: This skill should be used when the user asks to "self-publish", "publish my book", "ISBN", "copyright page", "book metadata", "BISAC", "keywords", "KDP", "IngramSpark", "Draft2Digital", "go wide", "Kindle Unlimited", "print interior", "trim size", "paperback", "ebook", "EPUB", "cover wrap", "spine width", "pricing", "launch plan", "ARC team", "advance readers", "newsletter", "reader magnet", "Amazon ads", "BookBub", "rights", "foreign rights", "audio rights", "film rights", "publishing contract", or wants to take a finished manuscript through production, distribution, launch, and rights management. It owns contracts and rights sales; NOT for permission to quote lyrics, epigraphs, or other material in the book (use editorial-review).
Publishing
Overview
Take a final manuscript into readers' hands. This skill fills the
publishing metadata in story.md, writes the copyright page, builds and
checks the ebook and print interior, walks the author through
distribution, pricing, and launch, and keeps an inventory of the rights
the author holds. Planning files live under publishing/ in the story
project. The author makes every account, upload, purchase, payment, and
signature; this skill prepares, checks, and records.
Prerequisites
A story project whose manuscript is final or nearly so. Verify story.md
exists and read title, status, author or authors, genre,
series, book-number, cover, and any publishing fields already set. If
status is not complete, say that metadata and launch planning can start
now but the files must be rebuilt after the last revision.
When to Use
- Filling retailer metadata: ISBN, publisher, date, description, keywords, BISAC subjects, language, cover alt text, AI disclosure
- Writing the copyright page or checking epigraph and lyric permissions
- Building and checking the EPUB or the print interior; choosing trim size
- Choosing retailers and exclusivity, setting prices, planning a launch
- Recording rights, reviewing a contract offer, drafting a rights one-sheet
- NOT for query letters, agent submission, synopsis, or blurb drafting
(use
submission; this skill reuses its blurb) - NOT for audiobook scripts, screenplays, translations, or other formats
(use
adaptation) - NOT for revising the manuscript (use
revision-continuity)
Hard Rules
- Never invent an ISBN, publisher or imprint name, publication date, price,
review, endorsement, sales figure, award, or bestseller claim. Ask, or
leave a
[TODO: author to supply]placeholder. - Never assert current retailer specs, royalty rates, or fees as fact. They change. Give the working figure as a starting point and tell the author to check the retailer's current spec before relying on it.
- Legal, tax, and contract matters are not legal or tax advice. Flag issues, explain why they matter, and recommend an agent, a publishing lawyer, an accountant, or an author organization's contract-vetting service.
- Never create accounts, upload, buy, sign, or send. The author does.
ai-disclosuremust say what actually happened. Ask the author how AI tools were used; never minimise it.
Workflow
1. Readiness
story validate .
story links .
story continuity .
story prose .
story wordcount . --write
story build . --format metadata
The metadata sheet lists every missing field in its readiness checklist.
Report it with the validate findings. validate warns about
permission: pending only once the story status is complete, and
about a research note with a risk but no reviewed-by only when a final
or complete chapter uses it, so also search the files directly before
publication:
grep -l "permission: pending" matter/*.md
grep -l "^risk:" research/*.md
Report every pending permission, and every risky note without
reviewed-by, whatever the chapter status. If story passes . shows unfinished revision passes, say so
before production starts.
2. Metadata
Fill the story.md fields with references/metadata-checklist.md:
isbn, publisher, publication-date, language, description,
keywords, subjects, copyright, cover-alt, ai-disclosure, and
authors for co-written books. Take the description from
submission/blurb.md when it exists (the submission skill drafts it).
Rebuild the sheet and repeat until the checklist is clean:
story validate .
story build . --format metadata
3. ISBNs and copyright page
-
Explain the ISBN choices in
references/metadata-checklist.md: one ISBN per format and edition, who issues them in the author's country, and the trade-offs of a free retailer ISBN. Record the ebook or print ISBN the author supplies inisbn. -
Create the copyright page and fill it from
references/copyright-page.md:story add matter "Copyright" --order 0Use an
orderlower than every other front page so it sits first (behind the title page);story add matterotherwise takes the next free number. Setheading: false. Without this page, every build except Shunn generates a minimal one fromcopyright; write it by hand when the book needs credits, permissions, or a Library of Congress line. -
For each epigraph, lyric, or quoted page in
matter/, setpermission(not-needed,pending,granted,public-domain),rights-holder, andcredit. Quoting song lyrics almost always needs permission.
4. Ebook
story build . --format epub
The EPUB carries accessibility metadata, language, semantic chapter and
matter markup, a landmarks nav, the cover with cover-alt, and the
metadata fields. If the author has EPUBCheck or Ace by DAISY installed,
run them on the file in dist/ (java -jar epubcheck.jar <file>.epub,
ace <file>.epub) and fix errors before upload. Ask the author to open it
in at least one reading app and in the retailer's previewer.