Agent Skills: Polish

Use when a draft's parts are all written but the seams between them are abrupt — smooths the transitions between sections so the piece reads as one continuous argument, not a stack of blocks. Owns the connective craft: handing momentum from one section to the next (problem→agitate→solve, story→lesson→call-to-action, feature→benefit→proof). TRIGGER when a draft is structurally complete and has cleared the strategy gate, and the sections need bridging. DO NOT TRIGGER for writing new copy from a brief (copywriting), running ship-gate checks (editing), or fixing a single line's clarity (that's the line check).

UncategorizedID: heyJordanParker/dotfiles/polish

Install this agent skill to your local

pnpm dlx add-skill https://github.com/heyJordanParker/dotfiles/tree/HEAD/packages/claude/profiles/copywriter/skills/polish

Skill Files

Browse the full folder contents for polish.

Download Skill

Loading file tree…

packages/claude/profiles/copywriter/skills/polish/SKILL.md

Skill Metadata

Name
polish
Description
Use when a draft's parts are all written but the seams between them are abrupt — smooths the transitions between sections so the piece reads as one continuous argument, not a stack of blocks. Owns the connective craft: handing momentum from one section to the next (problem→agitate→solve, story→lesson→call-to-action, feature→benefit→proof). TRIGGER when a draft is structurally complete and has cleared the strategy gate, and the sections need bridging. DO NOT TRIGGER for writing new copy from a brief (copywriting), running ship-gate checks (editing), or fixing a single line's clarity (that's the line check).

Polish

The parts are written. The headline lands, the sections each make their point, the call-to-action is sharp. What's missing is the connective tissue between them — the reader hits the end of one section and the start of the next with a jolt, because nothing carries them across. Polish is the last pass before the gate clears: it makes the seams disappear so the piece reads as one argument moving in one direction, not a stack of good blocks.

Polish never adds an argument, a claim, or a proof point — the writer did that already. It works only on the joins.

What a seam needs

A reader crosses a section break carrying momentum. The break either keeps that momentum or spends it. A good transition does three things at once:

  • Closes the prior beat so the reader feels the point landed, not abandoned.
  • Opens a question the next beat answers so the reader has a reason to keep going.
  • Holds the through-line so every section feels like the same argument, not a new one.

A seam fails when the next section restates what the reader already knows, when it jumps to a new idea with no bridge, or when it drops the momentum and makes the reader start over.

The common joins

Each structure has the same handful of seams every time. Bridge them on their own terms.

  • Problem → agitate → solve. The agitation inherits the exact problem just named, not a broader one; the solution answers the agitation's sharpest line, not the original problem in general. The reader should feel the temperature rise, then break.
  • Story → lesson → call-to-action. The lesson falls out of the story's specific ending, never arrives as a separate claim; the call-to-action is the lesson made actionable, the obvious next move for someone who just believed it.
  • Feature → benefit → proof. The benefit is the feature's outcome in the reader's terms; the proof backs the exact benefit just promised, placed where the doubt spikes.
  • Section → section down a long page. Each section ends pointing at the next — a line that closes its own point and leans forward. The page reads as one descent, never a list.

How to bridge

  • Carry a word. End a section on a charged word and open the next on it, or its echo. The repetition is the handrail the reader holds across the gap.
  • Ask the question the next section answers. A one-line question at a seam turns a break into a pull.
  • Cut the throat-clearing. Most rough seams are a section that opens by re-introducing its own topic. Delete the warm-up; start on the point and the join tightens itself.
  • Match the energy. A flat sentence after a sharp one reads as a stall. Keep the cadence moving across the break, then vary it inside the next section.
  • Never bridge with filler. "Furthermore", "in addition", "that being said", "but here's the thing" are the absence of a transition, not a transition. If the only bridge you can find is a connective adverb, the two sections aren't actually in sequence — reorder them or cut one.

What you return

The piece with its transitions smoothed, and the seams that were rough named — the section break, what jolted, the bridge you made. You touch only the joins and the throat-clearing around them. If a section's content itself is the problem — a missing claim, a weak point, an unbacked promise — that's a strategy or line failure, not a seam. Flag it; don't paper over it with a smoother transition.