followup-sequence
Use when asked to write follow-ups, nurture warm non-responders, or build a re-engagement sequence for leads who went quiet
How do I install this agent skill?
npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill followup-sequenceIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is generally safe and focuses on drafting lead follow-up messages. However, it relies on ingesting data from external sources such as CRM notes, LinkedIn conversations, and company news, which introduces a potential surface for indirect prompt injection if those sources contain malicious instructions.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Follow-Up Sequence
Write follow-up messages for leads who engaged (opened, clicked, partial reply) but didn't convert — or for contacts who went cold after initial interest.
Required tools
Install these before running the skill. None of them is strictly required, the skill also runs on pasted input, but without them the result gets noticeably worse: the follow-up type is picked from memory, and the 'new value' in the message is a guess because nobody checked what changed at the company.
| Tool | Used for | Required? | Without it |
|---|---|---|---|
| Instantly (MCP) | pull the original sequence, opens, clicks, replies and the date of the last touch for the lead | Recommended | you state the lead status by hand; Type A versus B gets mixed up |
| HeyReach (MCP) | pull the LinkedIn conversation for leads who went quiet there | Recommended | Type B and C messages cannot quote the previous conversation exactly |
| CRM (Twenty or HubSpot) | read notes and the date agreed in a timing objection (Type D) | Recommended | Type D fires on a guessed date |
| Firecrawl (MCP) | check company news, hires and posts for the one new piece of value | Recommended | the follow-up repeats the original angle, and the skill tells you not to send it |
Alternatives: lemlist or Smartlead can stand in for Instantly; Aimfox or Expandi can stand in for HeyReach; Exa can stand in for Firecrawl.
Inputs to have ready:
- Original sequence that was sent
- Current status of the lead (opened but didn't reply / replied once then went cold / attended event but didn't book)
- ICP and offer context
- How much time has passed since last contact
Follow-up types
Type A — No reply to initial sequence (soft re-engage)
- Used after full sequence with no response but positive engagement signals (opens, clicks)
- New angle — do not repeat what was in the original sequence
- Maximum 1 follow-up of this type per contact, per quarter
Type B — Replied once then went cold
- Reference the previous conversation specifically
- One new piece of value: case study, stat, relevant news about their company
- Soft ask: "still worth a quick chat?"
Type C — Expressed interest but didn't book
- Direct and brief — they already said yes in principle
- Remove friction: offer a time directly, or a Calendly link
- Under 50 words
Type D — Timing objection follow-up
- Triggered on the date agreed in the objection reply
- Reference the previous conversation and the timing they mentioned
- Treat them like a warm lead, not a cold contact
Process
- Identify the follow-up type based on lead status
- Draft the message using guidance for that type
- Check: does this add new value or just repeat the ask?
- If it doesn't add new value — don't send it
- Return the message with context on when to send it
Terms and plain-language output
<!-- glossary:start terms=nurture,cta mode=copy -->Rules for every text a reader will see (post, email, message, page copy):
- No internal codes or letter scales (A/B/C, D L T E, scores without words, framework codes). Write the meaning.
- Use the plain form from the table below. English stays only for tool names and for copy that ships in English. A term the reader may not know gets explained in the same sentence or replaced.
- Any review, audit or report this skill produces for the team or the client follows the document rules: open it with «Словник цього документа» (terms used, at most 10), do not score what depends on unfinished work, and open each section with one concrete action.
| Internal term (this skill) | Write for the reader | What it means |
|---|---|---|
| nurture | догрів | регулярні корисні дотики до тих, хто ще не готовий купувати. |
| CTA | прохання в кінці листа | конкретний маленький наступний крок: відповісти, подивитися, погодитися на дзвінок |
Output format
Follow-up: [lead name / company]
Type, in words: [no reply to the sequence / replied once then went quiet / interested but did not book / asked to come back later]
Last contact: [date]
Send on: [date or trigger]
MESSAGE
---
[drafted follow-up]
---
Word count: [n]
New value added: [yes/no — what]
Next action if no reply: [close / one more try / mark nurture]
Notes
- The most common mistake is following up without adding new value — "just checking in" is a waste of both parties' time
- Type C (interested but didn't book) has the highest conversion of any follow-up type — always prioritize these
- Track how many follow-up types are needed per campaign — high Type A volume means the original sequence didn't land
- After Type A follow-up with no response: close the thread. Don't keep following up.
- Reactivation (someone who went cold 6+ months ago) is different from follow-up — treat it as a new cold sequence with a reference to prior contact
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/followup-sequence">View followup-sequence on skillZs</a>