agentleFS
holaroluwaholaroluwa/outbound-skills/skills/copywriting-first-touch/SKILL.md

copywriting-first-touch

Skill0 starsChanged 46 days agoMITView on GitHub

Write a signal-led cold email under 75 words, a subject line and a low-friction CTA, from a prospect name, the signal you spotted, and your offer angle. Use when the user wants a "cold email", "first touch", "opener", or pastes a prospect plus a reason to reach out. Pulls ICP, pain, value props, and offer from outreach-brief.md and writes in a human voice, not AI-corporate. Reach for this whenever the user is starting a cold sequence.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    If there's no real signal, say so.

    line 15
  2. Distinctive:

    Keep the body under 75 words.

    line 22
  3. Distinctive:

    No em-dashes. Use a full stop or a comma.

    line 25
  4. Distinctive:

    No corporate filler: no "I hope this finds you well", "I wanted to reach out", "leverage", "synergy", "circle back", "touch base", "add …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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: First Touch

The first email's only job is to earn a reply. Short, about them, led by a real signal, asking for almost nothing. This skill writes that.

Input needed

  • Prospect name and company.
  • The signal: the specific, true reason you're reaching out now (a hire, a post, a launch, a trigger).
  • The offer angle, or read the offer and pains from outreach-brief.md.

If there's no real signal, say so. A fake "loved your post" opener is worse than no opener.

Method

  1. Open on the signal, in their world, not yours. The first line is about them.
  2. Bridge to one pain (section 6 of the brief) in their own language.
  3. One sentence of relevant proof or value, not the whole offer.
  4. A low-friction CTA: a question or "worth a look?", never "book a 30-minute demo."
  5. Keep the body under 75 words. Cut every word that isn't pulling weight.

Voice rules (non-negotiable)

  • No em-dashes. Use a full stop or a comma.
  • No corporate filler: no "I hope this finds you well", "I wanted to reach out", "leverage", "synergy", "circle back", "touch base", "add value".
  • Short sentences. Write like a human who respects their time. Specific over smooth.

Output

  • 3 subject-line options (under 5 words, lowercase is fine, curiosity or specificity, no clickbait).
  • The email body, under 75 words.
  • One line naming the signal used, so it's easy to swap per prospect.

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.