Editorial Review
Runs the human-in-the-loop parts of publishing a book: sensitivity reads, real-people/defamation passes, quote permissions, AI-use disclosure, editor rounds, review copies and co-author collaboration.
What it does
This skill handles every workflow in a story project that involves people outside the agent:
- Sensitivity & authenticity reads — finds the chapters, characters and research notes that touch lived experience the author lacks, builds a paid-professional brief (specific questions, deadline, fee), exports DOCX/HTML for the reader, then records outcomes in
reviewed-by - Real-people & defamation pass — lists identifiable people and organisations, classifies each portrayal, flags risky ones with
risk: [defamation], and explicitly says this is flagging, not legal advice - Permissions — tracks epigraphs, lyrics, poems and extracts with
permission,rights-holderand the exactcreditline; warns that lyrics almost always need clearance and fair use is narrow - AI-use disclosure — asks how AI was actually used, drafts a short honest statement into
ai-disclosure, and surfaces it on the retailer metadata sheet - Editor rounds — snapshot tags (
sent-to-editor-1), Word/Shunn builds, chapter-by-chapter transfer of accepted edits back into markdown, and a diff of how deep the round went - Review copies & collaboration — HTML with clickable paragraph anchors, GitHub Pages / issue templates, per-author branches, CODEOWNERS for shared worlds, remote pushes as backup
Guardrails are explicit: nothing is recorded, committed, pushed or published without your confirmation.
Who it's for
- Novelists portraying a culture, disability, faith or trade they don't share
- Authors whose fiction features real or recognisable people and organisations
- Writers wanting to quote lyrics or poetry and unsure about clearance
- Self-publishers sending manuscripts to a human editor and merging edits back
- Co-authors or shared-world teams managing a book in git
Examples
- "Prepare a sensitivity reader brief for chapter 4 about the Deaf community in 1980s Glasgow" → research note with
risk: cultural, a brief with questions/fee/deadline, plus a DOCX for the reader - "My novel features a real politician — is this okay?" → list of identifiable people, portrayal classification, risk flags, and a recommendation to get a publishing lawyer's review
- "I need an AI disclosure statement for a retailer" → a short, confirmed statement written into
story.mdand included instory build . --format metadata
· · · 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 Claude 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 /tmp/story-skills && mkdir -p ~/.claude/skills && cp -r /tmp/story-skills/skills/editorial-review ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repository:
git clone https://github.com/danjdewhurst/story-skills.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy this skill:
cp -r story-skills/skills/editorial-review ~/.claude/skills/ - Optionally copy the companion skills it hands off to (
feedback-triage,revision-continuity,line-editing,submission,story-maintenance). - For the Story CLI, run
bun run story -- --helpinside the repo checkout, or use the bundled fallbacknode skills/story-maintenance/scripts/story.js. - Make sure your manuscript project has
story.mdat its root, and rungit initif you want snapshot tags and the collaboration workflow. - Restart Claude Code and test with a prompt like "draft a sensitivity reader brief for chapter 4".