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).
Writes follow-up cold emails after no reply from a prospect.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .claude/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-upType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .agents/skills/copywriting-follow-up && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .agents/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .cursor/skills/copywriting-follow-up && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .cursor/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git --path .claude/skills/lemlist/copywriting-follow-up--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .gemini/skills/copywriting-follow-up && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .gemini/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-upInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .github/skills/copywriting-follow-up && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .github/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-follow-up -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-follow-up --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-follow-up .opencode/skills/copywriting-follow-up && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "copywriting-follow-up" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/copywriting-follow-up into .opencode/skills/copywriting-follow-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-follow-up", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
copywriting-follow-upWrites 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. 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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.claude/skills/copywriting-follow-up/SKILL.md (or your agent's skills folder).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.
Ask only what is missing — in a single message, never multiple rounds.
1. The previous email(s)
2. The sender's company & offer
3. The target prospect
4. Position in sequence
5. Personalization variables available
| Mistake | Why it fails |
|---|---|
| "Just checking in" | Zero new value — signals desperation |
| Repeating email 1 | They ignored it once — repetition confirms the delete |
| "Did you get my last email?" | Passive-aggressive — kills trust |
| Longer than email 1 | If the short version didn't work, longer won't either |
| More features or benefits | Wrong 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 |
Add new value — always. Every follow-up must give the prospect something they didn't have after email 1:
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.
The angle and tone change depending on where this follow-up sits in the sequence.
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:
Opening patterns for Email 2:
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:
Opening patterns for Email 3:
Goal: One last genuine attempt. High value, low pressure. Signal that this is near the end without full breakup yet.
Approach:
Opening patterns for Email 4:
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:
Breakup line (mandatory in final email):
won't message again, hope I didn't do something wrong!Before writing, confirm: is this angle genuinely different from all previous emails?
If the angle overlaps with a previous email → choose a different one.
PS format:
P.S. [One sentence — real reference or situation, zero fabricated outcomes].
[Practical resource: article, framework, template, checklist — relevant to their pain.]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]
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]Use this to select the right new angle. Never repeat an angle used in a previous email.
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
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
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Copywriting Follow Up this skillOthmane-Khadri/YALC-the-GTM-operating-system | 318 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Public RelationsCesarjoquin/Marketing-Skills | 202 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Public Relationscoreyhaines31/marketingskills | 54k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Campaign Copywritinggrowthenginenowoslawski/coldoutboundskills | 753 | — | ~7.5k | Automated safety check: Pass | MIT | |
| Press Kitericrisco/rsc-harness | 180 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Cold Email Strategistswan-gtm/gtm-skills | 172 | — | ~2.3k | Automated safety check: Pass | MIT |
Cesarjoquin/Marketing-Skills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
growthenginenowoslawski/coldoutboundskills
Creates cold email copy through a stepwise confirmation process.
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.
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…
amplitude/builder-skills
Write a PR/FAQ for a product idea using Amazon's Working Backwards process.
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.
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…
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…
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…
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.
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…
Categories
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.
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?.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Copywriting Follow Up is instructions for the agent only.
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.
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.
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.
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.
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.
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.