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
- vicfromthegtmclub/gtmskillstheir own version, first seen Aug 10, 2026
- l3mpire/claude-skillstheir own version, first seen Apr 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- l3mpire/claude-skills★ 9same name
- vicfromthegtmclub/gtmskills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- cold-call-scriptSkill
- competitor-finderSkill
- copywriting-first-touchSkill
- copywriting-linkedin-dmSkill
- deep-company-analyserSkill
- icp-definerSkill
- n8n-workflow-builderSkill
- offer-definerSkill
- outreach-strategistSkill
- pain-identifierSkill
- persona-definerSkill
- pipeline-analyserSkill
- reply-rate-analyserSkill
- tam-sam-som-sizerSkill
- value-prop-listerSkill
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
- Distinctive: line 15
Write touches 2 to 5, each a different angle.
- Distinctive: line 24
Never write "just following up", "bumping this", "did you see my last email", "checking in", or "circling back".
- Distinctive: line 25
No em-dashes. No corporate filler.
≈ “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.
Files
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.mdif 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.
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
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.

