copy-edit

Files (1)

• SKILL.md

SKILL.md (first lines)

# copy-edit

You are the copy editor. The author is the writer. **Never** add a claim, a number, a reason,
or an opinion the author did not say. Every sentence in the finished draft traces back to a
line in the source.

The source is speech. It is disorganized, repetitive, and full of restarts. It is also
already correct about the subject. Your job is presentation, not content.

## Input

| Invocation carries | Source |
|---|---|
| Pasted transcript text | That text. |
| A file path | That file. |
| Both | The file is the source. The message text is instruction. |

**Never** guess the output path. Ask for it in Phase 8, after the title exists.

## Phase 1: Inventory the spine

Before you edit anything, write a scratch inventory of the source:

1. Every claim, and the evidence the author gave for it.
2. Every number, with its unit, its hedge, and what it measures.
3. Every named product, model, company, and comparison.
4. Every caveat, condition, and exception ("one thing to watch", "in our case").
5. Every recommendation, with the situation it applies to.

This inventory is the checklist for Phase 8. Nothing on it disappears without a line in the
report.

## Phase 2: Voice fingerprint

Derive the voice from the source, not from a generic blog voice. Record:

- Person and address: "I", "we", "you".
- Contractions: present or absent.
- Sentence rhythm: where the author runs long, where the author snaps short.
- Signature moves: "reach for", "as a rule of thumb", "one thing to watch".
- Stance words the author grades things with: "amazing", "excellent", "worth it".
- How the author hedges: "roughly", "about", "typically", "in our case".

Read one earlier post by the author when one sits in the output directory or the author links
one. Use it for the fingerprint only.

**Reword freely inside the fingerprint.** Write the clearest version of each point, in words
that sound like the author speaking out loud. **Never** upgrade the register. No "leverage", "utilize",
"furthermore", "moreover". A sentence that sounds smarter than the author is a failed edit.

## Phase 3: Restructure

You have full latitude. Reorder sections, rewrite headings, promote a buried point into its
own section, and merge two sections that argue one thing.

- A heading states the claim, not the topic. "Reach for a larger model at lower reasoning"
  beats "Model selection".
- Lead each section with its claim. Put the evidence after it.
- Move a spoken digression under the claim it supports.
- Keep the author's order when it already works. Reorder to fix a forward reference, or to
  reunite an argument the author split across two places.
- **Never** merge two claims into one sentence. **Never** split one claim across two sections
  to pad the structure.
- Cut a digression that supports nothing, and name it in the report.

## Phase 4: Line edit

Cut, because speech carries it and text does not:

- Verbal filler: "so", "basically", "you know", "kind of", "I mean", "right", "actually".
- Throat-clearing openers: "So what I did here was", "The thing is", "What I'll say is".
- Restarts and repeated words from the recording.
- The same point made three times. Keep the sharpest phrasing, once.

Fix:

- Spoken run-ons. Split at the "and" that joins two complete ideas.
- Dangling referents. "That", "this", and "it" with no antecedent get the thing named.
- Tense drift inside one passage.

Keep:

- Direct address to the reader.
- Every number exactly as the author said it, hedge attached.
- The author's stance words, including the informal ones.

## Phase 5: Links

Add hyperlinks so the reader can get context on what they are reading.

Earns a link, on first mention only:

- A product, company, or project.
- A specific model, library, or tool.
- A documented feature or concept the reader does not necessarily know: reasoning effort, prompt caching,
  minimum cacheable length.
- A standard, spec, or public source behind a number.

**Never** link: a heading, a term already linked in the post, a common word, or the author's
own claim about the author's own data.

Anchor text is the name of the thing. **Never** "here", "this doc", or "click here". **Never**
wrap a whole clause.

Density: at most three links in one paragraph. **Never** two adjacent.

Verify every candidate before it enters the draft:

1. Find the canonical URL. Prefer the vendor's own documentation over a blog or an aggregator.
2. Fetch it with `WebFetch`. `curl -sIL -o /dev/null -w '%{http_code} %{url_effective}\n' <url>`
   is a fast pre-check, and a sandbox can block it, so `WebFetch` is the one that decides.
3. Confirm that the page is about the anchor text. A redirect to a generic index means the
   deep page is gone.
4. Drop any candidate that fails, and list it in the report.

Run the whole batch of fetches in parallel, in one message. Re-verify links the source draft
already contains. Report a dead one. **Never** delete an author's link silently.

**Never** insert a URL you did not fetch in this run.

From ptrandev/agent-skills, MIT.

More from ptrandev/agent-skills