follow-ups
Skill1 starsChanged 58 days agoMITView on GitHub
Use when stage 16 of the prospecting system needs the follow-up steps, timing, and channel mix drafted around the first-touch email and LinkedIn note. Also use standalone to design a multi-step outbound sequence.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- theam/claude-dev-kittheir own version, first seen Nov 1, 2026
- SuperMailOS/plugintheir own version, first seen Oct 25, 2026
- mukewl/jobkittheir own version, first seen Oct 20, 2026
- WireCatLabs/cli-coretheir own version, first seen Oct 20, 2026
- GuiBayma/skillstheir own version, first seen Oct 17, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- theam/claude-dev-kit★ 17same name
- WireCatLabs/cli-core★ 2same name
- youdcode/open-company★ 2same name
- GuiBayma/skills★ 1same name
- mukewl/jobkit★ 1same name
- SuperMailOS/plugin★ 1same name
- samsam007b/carriere-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- account-notesSkill
- audience-discoverySkill
- audience-filterSkill
- buying-signalsSkill
- cold-emailSkill
- contact-enrichmentSkill
- customer-patternsSkill
- follower-scrapeSkill
- icp-definitionSkill
- lead-prioritizationSkill
- lead-qualificationSkill
- lead-scoringSkill
- linkedin-outreachSkill
- lookalike-researchSkill
- personalizationSkill
- pipeline-reviewSkill
- prospecting-systemSkill
- reply-classificationSkill
- segmentationSkill
- targeted-searchSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
6
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
- Very specific: line 18
Follow-up copy rules live in /cold-email section 7.
- Distinctive: line 79
Every email step should have 2-3 variants to enable testing:
- Distinctive: line 89
Only test ONE variable per variant pair (subject OR body, not both)
- Distinctive: line 151
Use a consistent naming structure so performance data is analyzable:
- Distinctive: line 216
Don't over-engineer your first sequence.
- Distinctive: line 217
Keep a "swipe file" of every reply you get — positive and negative.
- Distinctive: line 218
If your open rate drops below 40% mid-campaign, stop sending.
“Common” is measured: kept by at least 6 in 10 of the 7 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.
Files
Sequence Architecture
Pipeline contract
Stage 16 of 20. Reads 14-emails.csv, 15-linkedin.csv. Writes 16-sequence.md (steps, day offsets, channel per step) and 16-followups.csv (segment, step, day_offset, channel, subject, body).
- Each follow-up adds something new (proof, angle, resource). A bump that only says "following up" does not ship.
- Follow-up copy rules live in
/cold-emailsection 7; this skill owns order, timing, and escalation. - Drafts only. Sequence settings are a recommendation for the human's sender.
Files live in runs/<run>/. Column definitions: /prospecting-system. Standalone use: ignore this block.
When to Use
- Building a new outbound campaign from scratch
- Restructuring sequences with poor step-2+ engagement
- Designing multi-channel cadences (email + LinkedIn + phone)
- Setting up A/B testing frameworks for sequence optimization
Framework
Sequence Design Principles
- Every step earns the next — Step 1's job is to get Step 2 opened. Step 2's job is to get a reply. Never front-load everything into Step 1.
- New value every touch — Each step must introduce a new angle, insight, or proof point. "Following up" is not a strategy.
- Decay is natural — Open and reply rates drop with each step. Design for this: your best material goes in Steps 1-2, your boldest ask goes in the final step.
- Variants multiply learning — Run 2-3 subject/body variants per step. At 200+ sends per variant, you have statistical significance.
The 4-Step Core Sequence
This is the baseline architecture. Adapt timing and angles to your ICP.
| Step | Day | Channel | Objective | Angle Strategy |
| 1 | 0 | Open + Reply | Lead with strongest signal or observation | |
| 2 | 3-4 | Reply | New value: resource, benchmark, or case study | |
| 3 | 7-8 | Reply or Referral | Social proof or creative ideas angle | |
| 4 | 14 | Close or Redirect | Breakup ("should I close this out?") or referral ask |
Total campaign duration: 14 days Total touches: 4 emails
Extended Sequence (Multi-Channel)
For high-value accounts or enterprise targets, layer in LinkedIn and phone:
| Step | Day | Channel | Objective |
| 1 | 0 | Signal-based opening | |
| 2 | 1 | Connection request with personalized note | |
| 3 | 3 | New value angle | |
| 4 | 5 | Engage with their content (like/comment) | |
| 5 | 7 | Case study or social proof | |
| 6 | 8 | Phone | "Following up on the email I sent" |
| 7 | 10 | Direct message with resource | |
| 8 | 14 | Breakup or referral |
Total campaign duration: 14 days Total touches: 8 (4 email + 3 LinkedIn + 1 phone)
Variant Strategy
Every email step should have 2-3 variants to enable testing:
| Variant Type | What You're Testing | Example |
| Subject variants | Which framing gets opens | A: {{company}} outbound vs B: quick question |
| Opening variants | Which personalization resonates | A: Signal-based vs B: Problem-based |
| CTA variants | Which ask gets replies | A: "Worth a look?" vs B: "Want me to send the playbook?" |
| Angle variants | Which value prop converts | A: ROI-focused vs B: Time-savings-focused |
Testing rules:
- Only test ONE variable per variant pair (subject OR body, not both)
- Minimum 200 sends per variant before drawing conclusions
- Winner = highest positive reply rate (not total reply rate — ignore "not interested" replies)
- Rotate winning variants into the "control" and test new challengers
Timing Optimization
| Factor | Recommendation | Why |
| Send days | Tuesday-Thursday | Monday = inbox overload. Friday = checked out. |
| Send window | 8:00 AM - 11:00 AM prospect's timezone | Caught during morning email triage |
| Step gaps | 3-4 days between emails | Enough to not feel pushy, close enough to maintain context |
| Reply window | Check within 30 min of sends | Fast replies to "interested" responses 3x close rate |
| Match lead ESP | Enabled | Send from Gmail to Gmail, Outlook to Outlook — improves deliverability |
Sequence Settings Checklist
Configure these before launching any campaign:
| Setting | Value | Reason |
| Stop on reply | ON | Never email someone who already responded |
| Stop on auto-reply | OFF | Auto-replies (OOO) shouldn't kill the sequence |
| Text only | ON | HTML emails trigger spam filters more often |
| Link tracking | OFF | Tracking pixels and links hurt deliverability |
| Open tracking | OFF | Same — open tracking = invisible pixel = spam risk |
| Daily send limit | Per account limits | Respect your email provider's sending limits |
| Email gap | 10-20 minutes | Time between individual sends — avoids burst patterns |
| Random delay | 5-10 minutes | Adds randomness to look human |
Escalation Logic
What happens when the standard sequence doesn't convert:
Standard Sequence (14 days)
↓ No reply
Wait 30 days
↓
Re-engagement Sequence (different angle, 3 steps)
↓ No reply
Wait 60 days
↓
Trigger-based Re-entry
(Only re-enter if new signal detected: funding, hiring, tech change)Never:
- Re-enroll someone in the same sequence
- Contact someone who explicitly said "not interested"
- Send more than 2 sequences to the same person in 6 months without a new signal
Campaign Naming Convention
Use a consistent naming structure so performance data is analyzable:
{Client} - {Segment} - {Angle} - {Version}Examples:
Acme - Enterprise VP Sales - Hiring Signal - v1Acme - SMB Founders - Referral Ceiling - v2Acme - Mid-Market Growth - Tech Stack Change - v1
This makes it trivial to filter analytics by client, segment, or angle.
Architecture Decision Tree
Is the target account high-value (>$50K ACV)?
├── YES → Extended Multi-Channel Sequence (8 touches, 14 days)
│ Layer email + LinkedIn + phone
│ Personalize every touch individually
│
└── NO → Standard 4-Step Email Sequence (4 touches, 14 days)
Use signal-based personalization at scale
Rely on variants for optimization
Is this a new persona/segment you haven't tested?
├── YES → Run 3 variants of Step 1 with 200+ sends each
│ Wait for data before building Steps 2-4
│
└── NO → Clone your best-performing sequence
Swap personalization for new segment
Keep winning structure intactTemplates
Campaign Launch Checklist
Pre-Launch:
- [ ] ICP and persona defined
- [ ] Lead list built and verified (bounce rate < 3%)
- [ ] Email accounts warmed (2+ weeks, 30+ emails/day)
- [ ] Sequence written (2-3 variants per step)
- [ ] Settings configured (tracking off, text-only, stop on reply)
- [ ] Naming convention applied
- [ ] Test send to yourself and team for QA
Post-Launch (Day 3):
- [ ] Check open rates (target: 60%+)
- [ ] Check bounce rate (must be < 3%)
- [ ] Check spam complaints (must be 0)
- [ ] Review any replies for pattern recognition
Post-Launch (Day 14):
- [ ] Calculate positive reply rate per variant
- [ ] Identify winning variants
- [ ] Document learnings
- [ ] Plan next iterationTips
- Build your sequence backwards — write the breakup email first, then work back to Step 1. This forces you to think about the full arc.
- The best Step 2 is a reply to Step 1 (literally in the same thread), not a new email. This uses the "thread effect" for higher opens.
- Don't over-engineer your first sequence. Launch with 4 steps, 2 variants each, and iterate from data. Perfection before launch = wasted time.
- Keep a "swipe file" of every reply you get — positive and negative. The language prospects use to say "yes" and "no" is gold for future copy.
- If your open rate drops below 40% mid-campaign, stop sending. You have a deliverability problem, not a copy problem.
Progressive disclosure: load channel-specific templates and industry playbooks only when building sequences for a specific campaign.
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
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.

