hermes

Build a self-editing checklist

Builds a personal self-editing checklist from samples of someone's writing and feedback they have received, ordered by their most frequent issues, with a quick test for each.

context

Generic editing checklists fail because they list thirty things the writer already does well and bury the three they always get wrong. A personal checklist is built from evidence: the issues that actually recur in this person's writing and the comments readers keep making. Each item is short, ordered by how often it bites, and paired with a fast mechanical test ("search for 'just'", "read only the first sentence of each paragraph") so it is used in two minutes before sending, not admired once and forgotten.

task

Build my personal self-editing checklistOnly if [WRITING_TYPE] is given: for .

writing samples

Only if [FEEDBACK_RECEIVED] is given:

feedback received

  1. If there are no samples, ask for them and stop. If there is only one sample or fewer than about 400 words in total, continue but say the checklist is provisional and will improve with more samples.
  2. Analyse the samples for recurring issues at three levels: structure (main point late, missing ask, weak openings or endings, paragraphs with several ideas), sentences (length, hedging, passive voice that hides the actor, nominalisations, filler, repetition) and mechanics (specific spelling, punctuation or agreement errors that repeat). Count occurrences and note which samples they appear in.
  3. Read the feedback. Map each comment to an issue you found, or add it as an issue if the samples show it. If feedback is not borne out by the samples, or contradicts them, say so rather than adding it.
  4. Rank the issues by frequency across samples, weighted up when readers have also complained about them. Keep the eight to twelve that matter most; drop one-offs.
  5. Write one checklist item per issue: the check as a short question, a quick test the writer can run in under a minute, and the fix, each with a before and after taken from their own samples.
  6. Note two or three strengths that appear consistently, so the writer does not edit them out.
constraints
  • Every item must be backed by evidence from the samples or the feedback. No generic advice that does not apply to this writer.
  • Quote the writer's own sentences for examples; you may shorten them with an ellipsis.
  • Fit the checklist to the writing type: a hedging check matters in a proposal; a citation check only if the samples need citations.
  • If the samples have few real problems, produce a shorter checklist and say so.
output format

Your top issues

A table: Rank | Issue | How often (for example "11 times across 3 of 3 samples") | Also raised in feedback (yes or no) | Example from your writing.

Self-editing checklist

A numbered list of checkboxes in rank order. Each: - [ ] The check as a question, then "Test:" one line, then "Fix:" one line with before → after.

Strengths to keep

Two or three bullets with an example each.

How to use it

Two or three lines: when to run it, in what order (structure first, then sentences, then mechanics), and when to update it.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Writing and communication
category
Editing
level
Beginner
made for
Writer / author, Student, Anyone, personal use, People manager
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install build-self-editing-checklist --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill build-self-editing-checklist -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the writing-communication plugin
claude plugin install hodios-writing-communication@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Editing
PromptEditing

Capture a writing voice profile

Analyses samples of a person's writing into a reusable voice profile of sentence habits, vocabulary, tone, structure and dos and don'ts, then drafts a test paragraph in that voice.

capture-writing-voice
PromptEditing

Critique a draft

Gives honest, ranked feedback on any draft across purpose, structure, argument, clarity and voice without rewriting it, and ends with the three changes that would matter most.

critique-draft
PromptEditing

Tighten prose

Tightens prose by cutting filler, redundancy and weak verbs toward a target reduction while keeping the author's voice, meaning and necessary qualifiers, and reports what it cut.

tighten-prose
PromptEditing

Proofread a text

Corrects grammar, spelling, punctuation and consistency errors in the chosen English variety, preserving the author's voice, and lists each change with the rule behind it.

proofread-text
PersonaEditing

Editor

Editor who serves the reader and the author's intent, edits at the right level with structure before lines, and explains every change so the author can accept, reject or learn from it.

editor
PromptEditing

Rewrite a text for tone

Rewrites a text in a target tone or register, such as warmer, firmer or more formal, without changing its facts, asks or commitments, and shows which tone dials moved.

rewrite-for-tone