agentleFS
admdanielpaulinoadmdanielpaulino/claude-codes/outbound-engine/SKILL.md

cold-outbound-optimizer

Skill1 starsChanged 7 months agoMITView on GitHub

Design, analyze, and optimize cold outbound email campaigns for Instantly. Handles end-to-end ICP definition, expert panel scoring (recursive to 90+), sequence copywriting, infrastructure audit, capacity planning, and implementation docs. Use when asked to build cold outbound sequences, optimize cold email, analyze outbound campaigns, build sales sequences, build Instantly sequences, create cold outbound strategies, or design email campaigns. Supports both "start from scratch" and "optimize existing" modes.

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do you have an existing Instantly account with campaigns to audit, or are you starting from scratch?

    line 28
  2. Distinctive:

    Do you have an Instantly API key?

    line 29
  3. Very specific:

    If API key provided → run scripts/instantly-audit.py to pull campaigns, account inventory, and warmup scores before proceeding.

    line 31
  4. Very specific:

    Run python3 scripts/instantly-audit.py --api-key <KEY> and report:

    line 38
  5. Distinctive:

    Ask: "Do you have a spreadsheet with historical outbound data?" If yes, request link.

    line 46
  6. Distinctive:

    If no ICP defined, collect:

    line 49
  7. Very specific:

    Use references/icp-template.md as the collection template.

    line 56
  8. Very specific:

    Default: 10 experts (see references/expert-panel.md).

    line 66
  9. Distinctive:

    Ask: "Any industry-specific experts to add, or panelists to swap?" Confirm roster before scoring.

    line 67
  10. Distinctive:

    If round score < 90: identify top 3 weaknesses, revise copy, run next round.

    line 94
  11. Distinctive:

    If round score ≥ 90: finalize copy and proceed to deliverables.

    line 95
  12. Distinctive:

    Create a document (Google Doc, Notion, or markdown) with:

    line 103
  13. Very specific:

    Follow all rules in references/instantly-rules.md and references/copy-rules.md.

    line 117
  14. Distinctive:

    After review, collect feedback and re-run scoring on revised copy if needed.

    line 123
  15. Very specific:

    Lead pipeline: Use scripts/lead-pipeline.py for Apollo → LeadMagic → Instantly automation.

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Preamble (runs on skill start)

# Version check (silent if up to date)
python3 telemetry/version_check.py 2>/dev/null || true

# Telemetry opt-in (first run only, then remembers your choice)
python3 telemetry/telemetry_init.py 2>/dev/null || true

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md.


Cold Outbound Optimizer


Startup: Determine Mode

Ask the user:

  1. Do you have an existing Instantly account with campaigns to audit, or are you starting from scratch?
  2. Do you have an Instantly API key? (Required for audit mode.)

If API key provided → run scripts/instantly-audit.py to pull campaigns, account inventory, and warmup scores before proceeding.


Phase 1: Discovery & Audit

1A — Infrastructure Check (if API key available)

Run python3 scripts/instantly-audit.py --api-key <KEY> and report:

  • Active campaigns (name, status, reply rate, open rate)
  • Sending accounts (count, warmup score, daily limit)
  • Domain inventory
  • Warmup gaps: any account with score <80 or <14 days warmup → flag as NOT ready

1B — Performance Data

  • Pull campaign analytics from Instantly
  • Ask: "Do you have a spreadsheet with historical outbound data?" If yes, request link.

1C — ICP Definition

If no ICP defined, collect:

  • Titles: Who are you targeting? (e.g., VP Marketing, Head of Growth)
  • Industries: Which verticals?
  • Company size: Employee count or revenue range?
  • Revenue floor: Minimum ARR/revenue to qualify?
  • Anti-ICP: Who to explicitly exclude?

Use references/icp-template.md as the collection template.

1D — Business Context

Collect:

  • What do you sell? (One sentence, no jargon)
  • What's the primary offer? (Free trial, audit, demo, consultation)
  • Real URLs to reference (pricing page, case studies, relevant content)
  • Any proof points? (Client results, stats, social proof)

1E — Expert Panel Config

Default: 10 experts (see references/expert-panel.md). Ask: "Any industry-specific experts to add, or panelists to swap?" Confirm roster before scoring.


Phase 2: Expert Panel Recursive Scoring

Target: 90/100. Non-negotiable. Iterate until reached.

Round Structure

Each round produces:

  1. Score table — all 10 panelists, individual score (0-100), one-line rationale
  2. Aggregate score — average of all 10
  3. Top weaknesses — ranked list of what's holding the copy back
  4. Changes made — specific edits addressing each weakness
  5. Updated copy — full revised sequence after changes

Scoring Criteria (per panelist's lens — see references/expert-panel.md)

  • Subject line curiosity / open rate potential
  • First sentence pattern interrupt
  • Body clarity and brevity
  • CTA softness and specificity
  • Sequence flow and follow-up logic
  • Deliverability risk signals (spam words, link density)
  • Personalization believability

Rules

  • Scores must be brutally honest. No padding to 90 without earning it.
  • If round score < 90: identify top 3 weaknesses, revise copy, run next round.
  • If round score ≥ 90: finalize copy and proceed to deliverables.
  • Show every round in the final doc — the iteration trail is part of the value.

Phase 3: Deliverables

Strategy Doc

Create a document (Google Doc, Notion, or markdown) with:

  1. Pre-Analysis / Brutal Truth — what the existing campaigns are doing wrong (or baseline if starting from scratch)
  2. ICP Summary — confirmed targeting parameters
  3. Infrastructure Status — account inventory, warmup readiness, capacity math
  4. Scoring Rounds — full panel vote tables for every round
  5. Final Email Copy — all steps for all campaigns, Instantly-ready format
  6. Implementation Plan — step-by-step setup instructions
  7. Capacity Math — accounts × daily send rate = pipeline projections
  8. Weekly Metrics Targets — open rate, reply rate, positive reply rate, meetings booked
  9. STOP List — what to kill immediately
  10. START List — what to launch first

Format Rules for Final Copy

Follow all rules in references/instantly-rules.md and references/copy-rules.md.

Human Review Gate

Do NOT push anything to Instantly automatically. The doc is for human review. Get explicit approval before any API writes.

Iteration

After review, collect feedback and re-run scoring on revised copy if needed.


Capacity Math Formula

Accounts ready (score ≥80, ≥14 days warmup) × 30 emails/day = conservative daily volume
Accounts ready × 50 emails/day = aggressive daily volume
Daily volume × 22 working days = monthly send capacity
Monthly sends × expected reply rate = expected replies
Expected replies × qualification rate = pipeline opportunities

Weekly Metrics Targets (Baselines)

MetricGoodGreat
Open rate40%+60%+
Reply rate3%+7%+
Positive reply rate1%+3%+
Meeting rate0.5%+1.5%+

Adjust targets based on niche and offer. Cold traffic to a free audit converts differently than a paid trial.


Add-On Recommendations (mention but don't build)

  • LinkedIn automation: HeyReach or similar for multi-channel sequences. Separate workflow.
  • Lead enrichment: Clay or Apollo for personalization data before upload.
  • Lead pipeline: Use scripts/lead-pipeline.py for Apollo → LeadMagic → Instantly automation.

Reference Files

FilePurpose
references/instantly-rules.mdVariable syntax, sequence structure, deliverability rules
references/expert-panel.mdDefault 10-expert roster with scoring lenses
references/copy-rules.mdEmail copy rules (first sentence, CTA, stats framing)
references/icp-template.mdICP data collection template
scripts/instantly-audit.pyPulls campaigns, accounts, warmup scores via Instantly v2 API
scripts/lead-pipeline.pyEnd-to-end lead sourcing pipeline
scripts/competitive-monitor.pyCompetitor tracking and intelligence
scripts/cross-signal-detector.pyMulti-source signal detection
scripts/cold-outbound-sender.pySend approved outbound emails

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.