editorial-review
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).
danjdewhurst · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add danjdewhurst/story-skills --skill editorial-review技能说明
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 (userevision-continuity) - NOT for query letters, synopses, or retailer copy (use
submission)
Workflow
1. Sensitivity and authenticity reads
-
Find what needs a read: characters, settings, and research notes that touch lived experience the author lacks. Mark the research notes that ground them by adding
culturalto the note'srisklist (addmedical,legal, or others as they apply), or open one:story add research 'Deaf community in 1980s Glasgow' --accuracy must-be-accurate --method expert-review --risk cultural --used-in chapter-04 -
Prepare the brief with
references/sensitivity-reader-brief.md: which chapters, which characters, specific questions, the author's research so far, deadline, and fee. Sensitivity reading is paid professional work; help the user budget and find readers, never suggest asking community members to work for free. -
Build what the reader receives:
story build . --format docxfor readers who comment in Word, orstory build . --format htmlfor paragraph-anchored notes. Areader-panelround's sensitivity persona can point at passages to put in the brief, but it is not a sensitivity read: never record it inreviewed-byor treat it as clearing a portrayal. -
Record the returned notes as a feedback round (
feedback/round-{N}/) and synthesise them through thefeedback-triageskill. When the reader's notes are incorporated, add them to the research note'sreviewed-by(name or role, with their consent to be named). -
story validate .warns when a note with anyriskis used in afinalorcompletechapter and has noreviewed-by.
2. Real-people and defamation pass
For fiction that uses real people, real organisations, or recognisable
portraits, follow references/real-people-and-permissions.md: list every
real or recognisable person, classify each portrayal, and flag the risky
ones in a research note by adding defamation (or legal) to its
risk list. Say
plainly that this is a flagging exercise, not legal advice, and recommend
a publishing lawyer's review before publication whenever a living person
or a real organisation is shown doing something discreditable.
3. Permissions for quoted material
- Find every quotation of someone else's work: epigraphs, lyrics,
poems, extracts, and in-text quotes. Each epigraph or quoted page
usually lives in
matter/. - Record state in the matter file's frontmatter:
permission(not-needed,pending,granted,public-domain),rights-holder, andcredit(the exact credit line the rights-holder requires). - Apply the cautions in
references/real-people-and-permissions.md: song lyrics almost always need permission, fair use is a narrow and uncertain defence, and public-domain status depends on country and date. Never setgrantedorpublic-domainwithout the user's confirmation and, forgranted, the rights-holder's name. story validate .warns when a matter page ispendingand the story iscomplete, and whengrantedhas norights-holder. Whatever the status,story exportand the builds leave apendingpage out (the review copy too) and warnpermission-pending-left-out, unless--include-pendingis given.
4. Overlap with other text
When the user worries that a passage echoes a source, an earlier book, or another writer too closely, compare the chapters with that text:
阅读完整来源 ↗