All skills
danjdewhurst avatar

/editorial-review

@ca69065

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 (use feedback-triage).

Use this Skill: https://skilld.dev/gh/danjdewhurst/story-skills/editorial-review

This session only. Nothing lands on disk.

referencessensitivity-reader-brief.md

≈1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sensitivity and Authenticity Readers

A sensitivity or authenticity reader is someone with lived or professional experience of what the book portrays, paid to read for inaccuracy, stereotype, and harm the author cannot see from outside. Sources and research notes (the research skill) cannot replace them.

When to suggest one

  • A POV or major character's identity, culture, faith, disability, illness, sexuality, or gender is one the author does not share
  • A setting, community, or historical trauma the author knows only from reading
  • A trade, institution, or experience the plot depends on (policing, nursing, prison, the military, addiction, immigration)
  • Portrayals of violence, abuse, or self-harm aimed at younger readers

One reader speaks for their own experience, not a whole community. For a central portrayal, two readers with different perspectives are better than one. An expert reader (a paramedic, a lawyer) checks technical accuracy; record them with method: expert-review on the research note.

Finding and paying readers

  • Search for professional sensitivity-reading services, editor directories, and writing organisations for the relevant community. Only name specific services the user or a verified search supplies.
  • Ask for the reader's rates, turnaround, and sample report. Fees are commonly quoted per manuscript, per word, or per hour; help the user budget from the reader's own quote, not a remembered figure.
  • Pay readers. Never suggest asking friends from a community, online groups, or strangers to do this work for free.
  • Agree in advance whether the reader wants to be credited (in acknowledgments and in reviewed-by) or kept anonymous.

Brief template

Save as feedback/briefs/{reader-kebab}.md or send as the body of the user's email. Keep briefs out of the feedback/round-{N}/ folders, which hold only reader feedback files and the synthesis.

# Reading brief: {Title}

**Book:** {genre, category (adult/YA/MG), form, word count}
**Logline:** {one sentence}
**What you are receiving:** {chapters or full manuscript; format: DOCX / HTML review copy}
**Deadline:** {date}   **Fee:** {agreed fee and payment terms}

## Why I am asking you
{The portrayal in question and why the author is outside it.}

## Characters and places to focus on
- {Character}: {role, how much page time, chapters}
- {Setting}: {chapters}

## Specific questions
1. {Does the family's Eid in chapter 6 ring true for a Glasgow Pakistani household in 1998?}
2. {Is the hearing character's reaction to BSL in chapter 4 plausible, or does it centre the wrong person?}
3. Anything else that pulled you out of the story or felt harmful.

## What I have researched
{Sources and research notes the portrayal relies on; decisions already made and why.}

## How to send notes
{Comments in the DOCX, or notes citing paragraph anchors like ch04-p12, plus a summary letter.}

## Credit
{Would you like to be named in the acknowledgments? Yes / no / role only.}

Specific questions get better notes than "is this okay?". Include what the author is most worried about.

Incorporating notes

  1. Record the notes as a reader file in feedback/round-{N}/ with feedback-template.md from the feedback-triage skill; quote the reader, do not paraphrase their judgement away.
  2. Synthesise through feedback-triage. Sensitivity notes carry the reader's expertise: decline one only with a recorded reason the author can defend, and never dismiss a note because it is inconvenient.
  3. Hand accepted changes to revision-continuity (events, character facts) or line-editing (wording).
  4. When incorporated, add the reader to each relevant research note's reviewed-by (name with consent, or role) and set status: verified if the note's findings now rest on sources and the review.
  5. Run story validate .: notes with a risk used in final chapters and no reviewed-by are warned.

A read is not a certificate. Tell the user that it lowers the chance of harm and error; it does not guarantee a reception.

Source: SKILL.md on GitHub

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill facilitates human-in-the-loop editorial workflows, such as sensitivity reads and author collaboration via Git. It utilizes a specialized 'story' CLI for project management and document building. The primary security consideration is the processing of untrusted external feedback and Word documents, which represents a surface for indirect prompt injection. The skill implements safety best practices by requiring user confirmation for all git operations and file modifications, and provides warnings regarding manuscript privacy on public hosting services.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Signed by skilld at ca69065. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for danjdewhurst/story-skills/editorial-review