agentleFS
holaroluwaholaroluwa/outbound-skills/skills/copywriting-follow-up/SKILL.md

copywriting-follow-up

Skill0 starsChanged 48 days agoMITView on GitHub

Write follow-up touches 2 through 5 for a cold sequence, each from a genuinely different angle, with none of the needy "just following up / bumping this" language. Use when the user has sent a first touch and wants "follow-ups", "the rest of the sequence", "touches 2-5", or "bump emails". Reads the first touch, persona, pains, and value props from context and outreach-brief.md, and keeps the human voice. Each touch must stand on its own, not beg.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write touches 2 to 5, each a different angle.

    line 15
  2. Distinctive:

    Never write "just following up", "bumping this", "did you see my last email", "checking in", or "circling back".

    line 24
  3. Distinctive:

    No em-dashes. No corporate filler.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Copywriting: Follow-up Sequence

Most follow-ups just say "bumping this to the top of your inbox," which trains people to ignore you. Each touch here earns its own reply with a new angle.

Input needed

  • The first touch that was sent.
  • The persona and pains (sections 4 and 6 of outreach-brief.md if present).

Method

Write touches 2 to 5, each a different angle. Rotate through angles like:

  • A new pain, or a different facet of the same one.
  • A short, specific proof point or mini case (real only).
  • A useful resource or insight that asks for nothing.
  • A pattern-interrupt, then a clean, no-guilt break-up email.

Each touch stands alone (a reader who missed touch 1 still gets it), stays short (shorter than the first where you can), and carries its own light CTA.

Voice rules (non-negotiable)

  • Never write "just following up", "bumping this", "did you see my last email", "checking in", or "circling back".
  • No em-dashes. No corporate filler. Short, human sentences.

Output

Touches 2-5, each labelled with its angle, a one-line gap suggestion (e.g., "send 3 days after touch 1"), and a light CTA. End with a clean break-up email that leaves the door open without guilt.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.