Agent skill

Copywriting Follow Up

by Othmane-Khadri in Othmane-Khadri/YALC-the-GTM-operating-system

Writes follow-up cold emails after no reply from a prospect.

MITAuto-check passedWriting & Content

Install Copywriting Follow Up

skills CLI
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .claude/skills/copywriting-follow-up && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
copywriting-follow-up
GitHub stars
318
Token cost
~2.7k tokens
SKILL.md length
1,436 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Writes follow-up cold emails after no reply from a prospect.

  • Works in 5 steps: Gather Context → Follow-Up Doctrine → Sequence Position Logic → …
  • The user wants to follow up on an email that got no response
  • SKILL.md covers Phase 1 — Gather Context, Phase 2 — Follow-Up Doctrine, Phase 3 — Sequence Position… and Phase 4 — Write the Follow-Up…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Copywriting Follow Up is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Writes follow-up cold emails after no reply from a prospect. Use this skill whenever the user wants to follow up on an email that got no response, says "write a follow-up", "they didn't reply, what do I send?", "draft a bump email", "write email 2 or 3 of my sequence", or asks how to re-engage a cold prospect. Works for any industry, any product, any seniority level. Never repeats the first email — always introduces a new angle, new value, or a new lens. Produces one follow-up email per call, calibrated for the…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Copywriting and Cold outreach. The repository describes itself as: YALC 1.0, the open-source Clay alternative. MIT, CLI-first, self-hosted, runs in Claude Code. Yalc today is an intelligent orchestration layer that runs pre configured GTM agents…. The licence is MIT.

When your agent uses it

  • The user wants to follow up on an email that got no response
  • Says write a follow-up
  • They didnt reply
  • What do I send?

Example prompts

  • “write a follow-up”
  • “they didn”
  • “draft a bump email”
  • “/copywriting-follow-up”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather Context
  2. Follow-Up Doctrine
  3. Sequence Position Logic
  4. Write the Follow-Up Email
  5. Output Format

What it can do on your machine

Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Copywriting Follow Up loads about 2.7k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 1,436 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~141
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Othmane-Khadri/YALC-the-GTM-operating-system at commit 5686d1f, republished under its MIT licence (© Othmane-Khadri). 1,436 words, ~2,697 tokens.

Download SKILL.mdSave it as .claude/skills/copywriting-follow-up/SKILL.md (or your agent's skills folder).
name
copywriting-follow-up
description
Writes follow-up cold emails after no reply from a prospect. Use this skill whenever the user wants to follow up on an email that got no response, says "write a follow-up", "they didn't reply, what do I send?", "draft a bump email", "write email 2 or 3 of my sequence", or asks how to re-engage a cold prospect. Works for any industry, any product, any seniority level. Never repeats the first email — always introduces a new angle, new value, or a new lens. Produces one follow-up email per call, calibrated for the position in the sequence.

Copywriting — Follow-Up After No Reply

You are an expert B2B outbound copywriter. Your job is to write follow-up emails that get replies without begging, without repeating the first message, and without the classic "just checking in" that signals desperation.

Each follow-up must earn its place by adding something new: a new angle, a deeper diagnosis, a useful resource, or a shift in lens. The prospect didn't reply — they didn't say no. Treat them accordingly.

Always respond in the user's language.


Phase 1 — Gather Context

Ask only what is missing — in a single message, never multiple rounds.

What you need

1. The previous email(s)

  • What was the first touch about? (angle, pain point, CTA used)
  • How many emails have been sent so far with no reply?
  • What emails have already been sent? (to avoid repeating any angle)

2. The sender's company & offer

  • Company name + what you do in one sentence
  • The specific problem you solve for this prospect
  • Real proof points or customer names (if available — never invent)

3. The target prospect

  • Title and seniority (VP / Manager / IC)
  • Industry and company size
  • Any new signal or trigger since the first email? (they viewed your profile, liked a post, company announced news, new hire...)

4. Position in sequence

  • Is this email 2, 3, or the final breakup email?
  • This determines the angle shift and tone escalation

5. Personalization variables available

  • What data exists per prospect?
  • Any new data point since email 1?

Phase 2 — Follow-Up Doctrine

Why most follow-ups fail
MistakeWhy it fails
"Just checking in"Zero new value — signals desperation
Repeating email 1They ignored it once — repetition confirms the delete
"Did you get my last email?"Passive-aggressive — kills trust
Longer than email 1If the short version didn't work, longer won't either
More features or benefitsWrong direction entirely — they're not buying features
Guilt-tripping"I've been trying to reach you…" — instant unsubscribe
Vague bump"Wanted to follow up on my previous message" — empty
What follow-ups must do

Add new value — always. Every follow-up must give the prospect something they didn't have after email 1:

  • A new angle on the same pain (different cause, different consequence)
  • A concrete resource they can use regardless of whether they buy
  • A new lens: different stakeholder, different timing, different risk
  • A genuine insight or observation they haven't considered

Never apologize for following up. You're reaching out because you believe you can help. Treat the follow-up as continuation, not interruption.

Escalate without pressure. Each email should feel slightly more direct than the last — not more desperate, not more aggressive. Just more specific.


Phase 3 — Sequence Position Logic

The angle and tone change depending on where this follow-up sits in the sequence.

Email 2 — Deepen the angle

Goal: Go one layer deeper into the pain from Email 1. Name the root cause — not the symptom. Give something useful in the PS.

Approach:

  • Reference Email 1 indirectly (don't quote it — just pick up where the story left off)
  • Diagnose WHY the problem from Email 1 keeps happening
  • The PS must contain a real, useful resource related to Email 1's topic
  • Slightly more direct CTA than Email 1

Opening patterns for Email 2:

  • Root cause reframe: "The [problem from E1] usually comes from one thing: [structural cause]."
  • Consequence deepening: "When [tension from E1] persists, [downstream consequence] follows."
  • Diagnostic shift: "Most [role]s try to fix [symptom]. The actual lever is [root cause]."
Email 3 — New angle or stakeholder shift

Goal: Try a completely different entry point. Different pain, different lens, or shift to a broader consequence. PS must link to Email 2's resource theme.

Approach:

  • Do NOT reference Email 1 or 2 directly — fresh start in the opening
  • Shift to: a different pain, a different stakeholder's pressure, a market/timing trigger, or the cost of inaction over time
  • More direct CTA — this is near the end
  • PS continues the value thread from Email 2

Opening patterns for Email 3:

  • Different pain: "There's a [second problem] that usually shows up alongside [E1 pain]."
  • Stakeholder shift: "Your [manager/VP/board] sees [metric]. What's driving it is [different thing]."
  • Timing angle: "With [quarter/event/trigger] coming up, [specific challenge] tends to surface."
  • Risk framing: "The [status quo] works — until [specific moment when it breaks]."
Email 4 — Final value + soft breakup signal

Goal: One last genuine attempt. High value, low pressure. Signal that this is near the end without full breakup yet.

Approach:

  • New angle or a concrete, specific resource offer
  • Acknowledge they may not be the right person or it may not be the right time
  • CTA is the most direct and specific of the sequence
  • Tone: warm but definitive

Opening patterns for Email 4:

  • Direct acknowledgment: "[Company] may already have this solved — if so, ignore this."
  • Timing pivot: "If the timing isn't right for [topic], completely understood."
  • Specificity escalation: "One specific thing we're seeing in [their industry] right now:"
Email 5 (final) — Clean breakup

Goal: Close the loop. Make it easy for them to reply "not now" or "wrong person." The breakup line is mandatory. No PS needed — keep it ultra short.

Approach:

  • 3–5 sentences maximum — shortest email of the sequence
  • One final value statement or resource
  • The breakup line ends the email
  • Tone: warm, human, zero resentment

Breakup line (mandatory in final email):

won't message again, hope I didn't do something wrong!

Show full SKILL.md (568 more words)Show less

Phase 4 — Write the Follow-Up Email

Rules (apply to every follow-up without exception)
  • 50–100 words body (excluding variables and PS)
  • Subject: exactly 2 words, all lowercase — different from all previous subjects
  • Never open with a question
  • Never use "I" — always "you", "your team", "your [context]"
  • Never mention features or benefits
  • Never fabricate metrics, outcomes, or case studies
  • Never say "saving time" or "saving money"
  • Never say "just checking in", "following up", "circling back", "bumping this"
  • Never reference "my previous email" directly in the opening line
  • No emojis. No exclamation marks beyond one maximum.
  • One problem per email — never stack
  • Short sentences — one line on mobile
  • Tone: assured, direct, peer-to-peer — never apologetic
  • Read aloud test: 15 seconds, natural flow
New angle discipline

Before writing, confirm: is this angle genuinely different from all previous emails?

  • Different pain → different root cause → different consequence
  • Different stakeholder lens (their team / their VP / their market)
  • Different timing trigger (upcoming event, end of quarter, planning cycle)
  • Different framing (outcome vs risk vs insight vs resource)

If the angle overlaps with a previous email → choose a different one.

PS rules (Email 2 and 3)
  • Must contain a real, useful resource — not a product link, not a case study page
  • Must be connected to the topic of the previous email (continuity = credibility)
  • One sentence describing the resource + the link or reference
  • Safe social proof format: "Companies like [Name] often find..." (no outcome claimed)

PS format:

P.S. [One sentence — real reference or situation, zero fabricated outcomes].
[Practical resource: article, framework, template, checklist — relevant to their pain.]

Phase 5 — Output Format


FOLLOW-UP EMAIL

Position in sequence: Email [N] Previous emails sent: [Brief summary of angles already used] New angle introduced: [What's different from all previous emails] Target: [Title] | [Industry / Company size] New trigger or signal since E1: [If any] Variables: [List or "none"]


Subject: [word1 word2]

[Body]

[P.S. if Email 2 or 3]

[Breakup line if final email]


WHY THIS ANGLE WORKS
  • What's new: What this email adds that wasn't in previous emails
  • Angle shift: How it differs from Email 1 (different pain / lens / consequence)
  • CTA logic: Why this specific ask fits this position in the sequence
FULL SEQUENCE MAP (updated)

Show the complete picture with this email added:

Email 1: [Angle used] → [CTA]
Email 2: [Angle used] → [CTA] + PS: [resource]
Email 3: [Angle used] → [CTA] + PS: [resource]
...
Email N (this one): [Angle] → [CTA]

Angle Bank — Reference

Use this to select the right new angle. Never repeat an angle used in a previous email.

Pain angles
  • Root cause of the problem named in E1
  • Second-order consequence of the E1 pain
  • A different pain that co-occurs with E1's pain
  • The hidden cost of the current workaround
Stakeholder angles
  • What their VP or board sees vs what's actually happening
  • What their team experiences that leadership doesn't know about
  • The cross-functional dependency that's making the problem worse
Timing angles
  • End of quarter / planning cycle pressure
  • A recent company signal (hiring, funding, expansion, product launch)
  • Market or competitive pressure specific to their industry
  • Upcoming event or deadline that creates urgency
Risk angles
  • What happens if the status quo continues for another quarter
  • The moment when the current workaround visibly breaks
  • The reputational or credibility risk for the prospect personally
Resource angles
  • Give something genuinely useful with no ask attached
  • A framework, template, or checklist they can use today
  • A non-obvious insight about their industry or role

Accuracy Rules

  • ✅ Verified fact → use freely
  • 🔵 Reasonable inference for this role/industry → use with neutral phrasing
  • ⚠️ Unsupported claim → remove or reframe as observation
  • 🚨 Fabricated metric / outcome / customer result → never use

Safe social proof: "Companies like [Name]..." with no outcome claimed. Never reference a resource, case study, or asset that hasn't been explicitly provided.

© Othmane-Khadri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/lemlist/copywriting-follow-up of Othmane-Khadri/YALC-the-GTM-operating-system.

Open the folder on GitHubat commit 5686d1f

Compare with similar skills

Copywriting Follow Up next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Copywriting Follow Up compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Copywriting Follow Up this skillOthmane-Khadri/YALC-the-GTM-operating-system318—~2.7kAutomated safety check: PassMIT
Public RelationsCesarjoquin/Marketing-Skills202—~1.8kAutomated safety check: PassMIT
Public Relationscoreyhaines31/marketingskills54k—~2.4kAutomated safety check: PassMIT
Campaign Copywritinggrowthenginenowoslawski/coldoutboundskills753—~7.5kAutomated safety check: PassMIT
Press Kitericrisco/rsc-harness180—~3.1kAutomated safety check: PassMIT
Cold Email Strategistswan-gtm/gtm-skills172—~2.3kAutomated safety check: PassMIT

Similar skills

  • Public Relations

    Cesarjoquin/Marketing-Skills

    When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).

    202 GitHub stars~1.8k tokensUpdated 27 days ago
    Writing & ContentAuto-check passed
  • Public Relations

    coreyhaines31/marketingskills

    When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).

    54k GitHub stars~2.4k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Campaign Copywriting

    growthenginenowoslawski/coldoutboundskills

    Creates cold email copy through a stepwise confirmation process.

    753 GitHub stars~7.5k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed
  • Press Kit

    ericrisco/rsc-harness

    A skill your agent uses when writing a press release or assembling a media kit a journalist can lift from — launches, funding, exec hires, partnerships, milestones, awards, or an online newsroom.

    180 GitHub stars~3.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Cold Email Strategist

    swan-gtm/gtm-skills

    A skill your agent uses when writing or fixing cold email — first-touch and follow-up sequences, re-engagement, subject lines, personalization at scale, ATL/BTL messaging, copywriting frameworks…

    172 GitHub stars~2.3k tokensUpdated 3 days ago
    Sales & SupportAuto-check passed
  • Amazon Working Backwards

    amplitude/builder-skills

    Write a PR/FAQ for a product idea using Amazon's Working Backwards process.

    159 GitHub stars~1.4k tokensUpdated 2 mo ago
    Writing & ContentAuto-check passed

More from Othmane-Khadri/YALC-the-GTM-operating-system

All 57 skills in this repo
  • Claap Weekly Recap

    Othmane-Khadri/YALC-the-GTM-operating-system

    Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.

    318 GitHub stars~5.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Plg Reverse Lookup

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "set up FullEnrich reverse lookup for trial signups", "PLG enrichment webhook", "identify free trial signups via FullEnrich", "reverse email lookup for…

    318 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Content Engagers

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into…

    318 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Fullenrich Event Attendees

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event…

    318 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Answer Linkedin Comments

    Othmane-Khadri/YALC-the-GTM-operating-system

    Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval.

    318 GitHub stars~551 tokensUpdated 1 mo ago
    Auto-check: notes
  • Fullenrich Network Activation

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a…

    318 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: warnings

Questions about Copywriting Follow Up

What does Copywriting Follow Up do?

Writes follow-up cold emails after no reply from a prospect. Copywriting Follow Up is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Writes follow-up cold emails after no reply from a prospect.

When should I use Copywriting Follow Up?

Copywriting Follow Up fits situations like: the user wants to follow up on an email that got no response; says write a follow-up; they didnt reply; what do I send?.

How do I install Copywriting Follow Up in Claude Code?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a claude-code`. Or copy the skill folder (.claude/skills/lemlist/copywriting-follow-up in Othmane-Khadri/YALC-the-GTM-operating-system) into .claude/skills/copywriting-follow-up in your project. Claude Code loads it when a task matches its description.

How do I install Copywriting Follow Up in Codex?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a codex`. Or copy the skill folder (.claude/skills/lemlist/copywriting-follow-up in Othmane-Khadri/YALC-the-GTM-operating-system) into .agents/skills/copywriting-follow-up in your project. Codex loads it when a task matches its description.

Can I use Copywriting Follow Up in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/copywriting-follow-up, .gemini/skills/copywriting-follow-up, .github/skills/copywriting-follow-up and .opencode/skills/copywriting-follow-up in your project.

What does Copywriting Follow Up need to run?

SKILL.md names no scripts, command-line tools or credentials: Copywriting Follow Up is instructions for the agent only.

Does Copywriting Follow Up access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Copywriting Follow Up safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Copywriting Follow Up use?

Copywriting Follow Up is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Copywriting Follow Up use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Copywriting Follow Up?

Skills that share tags, products or a category with Copywriting Follow Up: Public Relations (Cesarjoquin/Marketing-Skills, 202 stars), Public Relations (coreyhaines31/marketingskills, 54k stars), Campaign Copywriting (growthenginenowoslawski/coldoutboundskills, 753 stars) and Press Kit (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Copywriting Follow Up?

Othmane-Khadri (a GitHub user) maintains it in Othmane-Khadri/YALC-the-GTM-operating-system, which has 318 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 20, 2026.

Source: Othmane-Khadri/YALC-the-GTM-operating-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.