Systems Lab

Agent skill

re-engagement

Writes re-engagement emails to revive cold or lost leads.

slowingReaches the webInstructions only395 words

Filed under Outbound email.

From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14

What it does when it runs

Writes re-engagement emails to revive cold or lost leads. Use when the user asks to "re-engage", "reactivate", "closed-lost email", "win back", "reconnect with old leads", "ramp re-engagement", "no-show follow-up", or needs to email prospects who went dark weeks/months ago. Also triggers on "revive dead leads", "lost deal email", "they ghosted me". Do NOT use for follow-ups within an active sequence (use follow-up skill), first-touch emails, or deliverability questions.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
  • frontal.so
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about re-engagement

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills
git -C /tmp/outbound-skills sparse-checkout set "master-skills/cold-email/.claude/skills/re-engagement"
mkdir -p ~/.claude/skills/re-engagement
cp -R "/tmp/outbound-skills/master-skills/cold-email/.claude/skills/re-engagement/." ~/.claude/skills/re-engagement/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/cold-email/.claude/skills/re-engagement/SKILL.md, which is licensed MIT (repository). 395 words, 9 headings.

Re-Engagement Email Writing

You write emails that revive cold leads, closed-lost deals, and prospects who went dark. These are NOT follow-ups within an active sequence -- these target leads from weeks or months ago.

Process

  1. Understand the history -- When was last contact? What was discussed? Why did they go cold?
  2. Identify the new angle -- What has changed since then? (new feature, new data, new trigger)
  3. Draft re-engagement -- No-oriented question, very soft CTA, acknowledge the gap

Reference

Read {SKILL_BASE}/resources/templates/email-templates-library.md for re-engagement templates (#31-34): no-oriented questions, closed-lost reactivation, and ramp re-engagement.

Re-Engagement Types

1. No-Oriented Question (Rebook Demos)

For prospects who booked but did not convert. Use "no-oriented" questions that are easy to say no to (which paradoxically gets more replies).

2. Closed-Lost Reactivation

For deals that were lost. Reference the original objection and what has changed since.

3. Ramp Re-Engagement

For leads from old sequences. New angle, new trigger, very soft ask for the right person.

Key Principles

  • Acknowledge the gap -- Do not pretend the previous interaction did not happen
  • Lead with what changed -- New feature, new data, new case study, market shift
  • No-oriented questions work -- "Would it be crazy to reconnect?" gets more replies than "Want to chat?"
  • Reference their words -- If they gave an objection, name it: "You mentioned X was the blocker"
  • Very soft CTAs -- "Still relevant?" or "Worth another look?" not "Book a call"

Examples

Example 1: No-Oriented Question (Rebook)

Subject: quick question

{{firstName}},

Would it be crazy to reconnect?

I know we talked {{timeframe}} ago about {{topic}}.

We've since launched {{new_feature}} which directly addresses the {{objection}} concern.

Still relevant?

Example 2: Closed-Lost Reactivation

Subject: since we last talked

{{firstName}},

When we talked in {{month}}, you mentioned {{objection}} was the blocker.

Since then, we've {{specific_improvement}} -- {{similar_company}} saw {{result}} after making the switch.

Worth another look?

Example 3: Ramp Re-Engagement (New Angle)

Subject: different angle

{{firstName}},

Reached out a while back about {{original_topic}} -- different reason this time.

Just published a report on {{new_topic}} showing {{industry}} companies are {{insight}}.

Thought of {{company}} given {{trigger}}.

If this isn't you, who handles {{topic}} on your team?

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what re-engagement does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.