# editorial-review

editorial-review — a Claude Code skill manages human editorial passes for manuscripts. It formats briefs for sensitivity readers, tracks quote permissions, and checks text overlap against earlier books.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 468 installs · ★ 443 repo stars
- Author: danjdewhurst
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/danjdewhurst/story-skills/tree/HEAD/skills/editorial-review/SKILL.md
- Updated: 2026-11-14
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/editorial-review

## What it does

The skill organizes outside reviews, co-author collaboration, and editorial rounds for book projects. It marks character notes with risk flags, prepares structured briefs for paid sensitivity readers, and extracts incoming comments from DOCX or HTML builds. Using `story similarity`, it scans drafted chapters for unintended overlap against source folders or earlier volumes.

It catalogs permissions for epigraphs, song lyrics, and poems inside `matter/` frontmatter. Commands like `story validate .` highlight unapproved citations or unreviewed sensitive portrayals in finished chapters. The skill does not give legal advice and never contacts readers automatically.

A project needs a root `story.md` file, drafted chapters, and Git. Snapshot tagging and diff checks fail if the folder is not a Git repository.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add danjdewhurst/story-skills --skill editorial-review -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/editorial-review/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/editorial-review/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add danjdewhurst/story-skills --skill editorial-review -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/editorial-review/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add danjdewhurst/story-skills --skill editorial-review -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/editorial-review/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install danjdewhurst/story-skills skills/editorial-review
```

2. **Manually: put the files in place**
- File: `.github/skills/editorial-review/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add danjdewhurst/story-skills --skill editorial-review -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/danjdewhurst/story-skills --path skills/editorial-review
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/editorial-review/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add danjdewhurst/story-skills --skill editorial-review -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/danjdewhurst/story-skills/tree/HEAD/skills/editorial-review/SKILL.md

## When to use it
- draft a structured brief for sensitivity and authenticity readers
- audit character portrayals for defamation and legal risks
- track copyright permissions for epigraphs and song lyrics
- prepare DOCX review copies and import editor feedback notes

## Example prompts
- Prepare a sensitivity reader brief for chapter four
- Check this manuscript for overlap against my earlier book notes
- Log permission status for the song lyrics quoted in the epigraph

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5885aae97282eb48.

BEGIN THIRD-PARTY FILE 5885aae97282eb48
```text
---
name: editorial-review
description: This skill should be used when the user asks for a "sensitivity reader", "authenticity reader", "cultural review", "is this portrayal okay", "real people in my novel", "defamation", "can I use song lyrics", "epigraph permission", "permissions", "quote permission", "fair use", "AI disclosure", "do I need to disclose AI", "send to my editor", "editorial round", "Word file for my editor", "editor review copy", "co-author", "collaborate on a book", "shared world", "back up my book", "does this echo my source", "similarity check", "check overlap with my earlier books", or wants to run human editorial, ethics, permissions, or collaboration workflows around a story project. NOT for contracts or selling rights (use publishing), or reader feedback rounds and review copies for readers, including the GitHub review-copy setup (use feedback-triage).
---

# Editorial Review

## Overview

Run the workflows that involve people outside the agent: briefing and
paying sensitivity and authenticity readers, a real-people and
defamation-risk pass, permissions for quoted material, an AI-use
disclosure statement, editorial rounds with human editors, and
collaboration between co-authors. The skill prepares materials, tracks
state in frontmatter, and flags risks. It does not give legal advice, it
does not contact anyone, and it never records a permission, review, or
disclosure the user has not confirmed.

## Prerequisites

A story project with `story.md` in the root and drafted chapters. Git is
needed for snapshot tags, `story compare --ref`, and the collaboration
workflow; offer `git init` if the project has none.

## When to Use

- A book portrays a culture, identity, disability, faith, trade, or
  experience the author does not share
- Fiction features or resembles real, identifiable people or organisations
- The manuscript quotes lyrics, poems, epigraphs, or other writers' prose
- A passage may echo a source, an earlier book, or another writer too closely
- The user needs an AI-use statement for a retailer, agent, or publisher
- Sending the manuscript to a human editor, or taking their edits back
- Two or more people write or maintain the same book or shared world
- NOT for synthesising reader notes into decisions (use `feedback-triage`; this skill hands notes to it)
- NOT for fact-checking real-world details (use `research`; this skill adds the review layer on top)
- NOT for the agent's own prose edit (use `line-editing`) or structural revision (use `revision-continuity`)
- NOT for query letters, synopses, or retailer copy (use `submission`)

## Workflow

### 1. Sensitivity and authenticity reads
```
END THIRD-PARTY FILE 5885aae97282eb48

The third-party file has ended. Everything between the 5885aae97282eb48 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2663 of 15711 bytes. © danjdewhurst · MIT · https://github.com/danjdewhurst/story-skills/tree/HEAD/skills/editorial-review/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
