agentleFS
guerrilla2799guerrilla2799/sdr-copilot/skills/reactivate/SKILL.md

reactivate

Skill1 starsChanged 4 months agoMITView on GitHub

Mine dormant HubSpot lists — closed-lost, unbooked demo requests, ghosted threads, stale trials — and build re-entry outreach that acknowledges the history. Use when the rep says "reactivate", "work the closed-lost list", "old leads", "who went dark", or wants outbound without burning fresh accounts.

3 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. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/references/icp.md, references/messaging.md, and references/guardrails.md if not already in context.

    line 12
  2. Distinctive:

    If the connector can't run a pool query, ask the rep to paste an export.

    line 23
  3. Distinctive:

    No delta + weak history = leave it dormant.

    line 32
  4. Distinctive:

    Every re-entry email: acknowledges the history in the first line, brings the ONE new thing, ≤80 words, one CTA.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Reactivate

Dormant lists are the sanctioned experimentation playground — these accounts already knew us once, nobody else is working them, and a swing-and-miss costs nothing. That freedom has one price: never pretend it's a first touch. A re-entry that ignores the history reads as either automation or amnesia, and both kill whatever warmth is left.

Before you mine

Read ${CLAUDE_PLUGIN_ROOT}/references/icp.md, references/messaging.md, and references/guardrails.md if not already in context. Confirm with the rep which pool and how many (default 15, hard cap 25 per run — same as build-list).

Step 1 — Pull the pool (HubSpot)

The four pools, in rough order of value:

  1. Unbooked demo requests — asked for a demo, never scheduled. Warmest dormant contacts that exist.
  2. Closed-lost > 6 months — pull the closed-lost REASON with each one; it determines the angle.
  3. Ghosted threads > 90 days — replied once, then went dark mid-conversation.
  4. Stale trials — signed up for the free tier, never meaningfully activated (or activated and drifted).

If the connector can't run a pool query, ask the rep to paste an export. Guardrail #1 still applies: anything that has since become a customer or grown an open deal → out, immediately.

Step 2 — Why would NOW be different?

For each account, two checks:

  • History read (HubSpot): what actually happened last time — the closed-lost reason, the last thing they said, who they talked to. Quote it.
  • Delta check (Exa, ~1 search per account): what changed since — a relevant new hire, a launch, funding, the competitor they chose getting acquired, renewal window opening. A dormant account plus a fresh trigger is the best lead in this plugin — score it like signal-watch would and rank those first.

No delta + weak history = leave it dormant. Re-entering with nothing new to say spends the last of the goodwill.

Step 3 — Match the angle to the exit reason

Last timeRe-entry angle
Lost to a competitorRenewal timing + your organizing competitive frame from messaging.md (Hook 5). Ask when the contract renews — that's the whole email.
"No budget"Honest pricing + real free tier: "the thing that changed since (e.g. new pricing) is the answer to what stopped us last time"
"Not a priority" / no urgencyONLY re-enter on a fresh trigger, and lead with it
Ghosted mid-threadReply in the old thread, 2 sentences, name the gap without guilt ("we got to X and life happened — still the right problem?")
Unbooked demoShortest path back: "you asked for a demo in [month]; easier now — 15 minutes or just start the free tier"
Stale trialProduct-led re-entry for Champion types: one specific thing they'd see if they reconnected the account (a new capability shipped since they tried it)
Lost to "do nothing" / built internal"How's the in-house build holding up?" — gently; DIY builds decay and they know it

Every re-entry email: acknowledges the history in the first line, brings the ONE new thing, ≤80 words, one CTA. All write-email rules and the voice profile apply.

Output format

# Reactivation run: [pool] · [date] · [N] accounts

## Hot — dormant + fresh trigger (work these first)
| Company | Last time (reason + date) | What changed | Angle | Contact |
|---|---|---|---|---|

## Standard re-entry
[same table]

## Leave dormant (no delta, no angle)
[company → why — so the next run doesn't re-litigate them]

## Excluded — became customer / active pipeline
[company → status]

## Sample re-entry drafts
[2-3 full emails from the Hot tier, per the angle table]

End with: this pool is where experiments belong — if you want to test a new angle or subject-line style, run it here first and tell what-works how it went. Track reactivation replies separately in the weekly review; they should beat cold rates (5-8%+) or the pool/angle needs rethinking.

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.