Editorial Review
Runs the human-in-the-loop pre-publication workflows: sensitivity reads, real-people/defamation flagging, quote permissions, AI disclosure, editor rounds, and co-author collaboration.
Content & WritingIntermediate★ 364⑂ 58AI score 8/10Last updated: Oct 27, 2026
What it does
This skill orchestrates the parts of publishing a book that require real people, not just the agent.
- Sensitivity / authenticity reads: locates the chapters, characters, and research notes that touch lived experience the author lacks, builds a paid brief (specific questions, deadline, fee), and logs returned notes as a feedback round. It explicitly refuses to treat an AI
reader-panelpersona as a sensitivity read. - Real-people & defamation pass: lists every identifiable person or organisation, classifies portrayals, tags risky ones
defamation/legal, and insists this is flagging, not legal advice — recommending a publishing lawyer. - Permissions: tracks
permission(not-needed/pending/granted/public-domain),rights-holder, and exact credit lines in matter-file frontmatter; pending pages are left out of builds with a warning. - Overlap checks:
story similarity . --against <file|folder|git-ref>reports shared word runs with both locations, while forbidding claims like "original" or "plagiarism-free". - AI-use disclosure: drafts a short, honest statement for
story.mdand includes it on the retailer metadata sheet. - Editor rounds: git snapshot tags (
sent-to-editor-1), DOCX/Shunn builds, chapter-by-chapter transfer of accepted edits, andstory compare --refto show the depth of the round. - Review copies & collaboration: paragraph-anchored HTML copies for non-technical readers, plus per-author branches, PRs, CODEOWNERS and remote backups.
Who it's for
- Novelists who keep a book as a markdown project driven by the Story CLI
- Authors portraying cultures, identities, disabilities or faiths outside their own experience
- Self-publishers dealing with lyrics, epigraphs, or real people in fiction
- Co-author teams or shared-world collaborators
Example uses
- "I need a sensitivity reader for the Deaf community chapters" → it finds the affected chapters and research notes, drafts the brief, and builds a Word copy for the reader.
- "Can I use these song lyrics as an epigraph?" → warns that lyrics almost always need permission, records
permission: pendingplus rights-holder, and keeps the page out of builds until confirmed. - "Does this passage echo book one too closely?" → runs
story similarity . --against ../book-one --min-words 12and lists each shared run with locations, leaving the judgement to the author.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/danjdewhurst/story-skills/HEAD/skills/editorial-review/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on AI Skill Mart. Copy the skills/editorial-review folder from the GitHub repo danjdewhurst/story-skills into my ~/.claude/skills/editorial-review/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/danjdewhurst/story-skills.git && mkdir -p ~/.claude/skills && cp -r story-skills/skills/* ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the skills repository:
git clone https://github.com/danjdewhurst/story-skills.git - Create your Claude Code skills directory:
mkdir -p ~/.claude/skills - Copy the skills across. Because this one references shared conventions and a fallback CLI inside
story-maintenance, copy all of them:cp -r story-skills/skills/* ~/.claude/skills/ - Verify:
ls ~/.claude/skills/editorial-reviewshould showSKILL.mdand areferences/folder. - (Recommended) Install Node.js. Without a global
storycommand, the skill falls back tonode .../story-maintenance/scripts/story.js. - Start Claude Code inside your book folder (the one containing
story.md); rungit initif it isn't a repo yet, since snapshots and collaboration need git. - Trigger it with prompts like "draft a sensitivity reader brief", "do I need permission for these lyrics", or "build a Word file for my editor".
View source on GitHub ↗License: MIT