Instantly sequences skill
Sets up and optimizes Instantly: sending accounts, warmup pool, campaign settings, and the unified inbox.
by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗
npx degit LeadMagic/gtm-skills/skills/tools/instantly-sequences#main ~/.claude/skills/instantly-sequencesChecked ·commit main
Inside this skill
SKILL.md · the author's own words# Instantly Sequences ## Overview Instantly competes with Smartlead in the high-volume cold email space. Key features: unlimited email accounts, built-in warmup pool, campaign optimization, and a unified inbox. This skill covers setup from infrastructure through optimization. ## Authoritative Foundations - **Instantly Help Center** — Connect sending accounts, enable warmup, and set per-account daily limits and campaign schedules before launc… - **Eric Nowoslawski — Cold email infrastructure** — Cold email infra at scale — 2 inboxes/domain, backup inboxes, Creative Ideas testing. - **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and hon… ## When to Use - "Set up Instantly" - "Instantly campaign setup" - "Instantly warmup"
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Instantly sequences
Show the full text149 lines
Instantly Sequences
Overview
Instantly competes with Smartlead in the high-volume cold email space. Key features: unlimited email accounts, built-in warmup pool, campaign optimization, and a unified inbox. This skill covers setup from infrastructure through optimization.
Authoritative Foundations
- Instantly Help Center — Connect sending accounts, enable warmup, and set per-account daily limits and campaign schedules before launch.
- Eric Nowoslawski — Cold email infrastructure — Cold email infra at scale — 2 inboxes/domain, backup inboxes, Creative Ideas testing.
- Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and honor unsubscribes quickly.
When to Use
- "Set up Instantly"
- "Instantly campaign setup"
- "Instantly warmup"
- "Optimize Instantly campaigns"
Step-by-Step Process
Phase 1: Account Infrastructure
- Buy secondary domains (never use primary domain)
- Set up 2-3 Google Workspace or M365 mailboxes per domain
- Configure DNS: SPF, DKIM, DMARC, custom tracking domain
- Connect all mailboxes to Instantly
- Begin warmup: Instantly auto-sends from your mailboxes to its warmup pool and auto-replies to build reputation. Run 2-3 weeks before launching.
Phase 2: Campaign Setup
- Import leads: CSV upload with mapped fields, verify emails before sending
- Sequence builder: Unlimited email steps, delays between 1-7 days
- A/B testing: Up to 26 variants per campaign, auto-rotate, declare winner
- Sending schedule: Mon-Fri with timezone optimization, max 50 emails/day/account
- Account rotation: Auto-rotate across connected accounts, no account sends >50/day
Phase 3: Campaign Rules
- Auto-pause on X consecutive bounces
- Auto-remove from sequence on unsubscribe request
- Auto-label replies by sentiment (AI categorization)
- Duplicate detection: don't send to the same email across campaigns
- Blocklist management: automatically suppress unsubscribes across all campaigns
Phase 4: Unified Inbox
- All replies across all accounts in one view
- Reply from any connected account in one interface
- Auto-label: interested, not interested, OOO, wrong person
- Lead status sync: update CRM based on reply categorization
Phase 5: Optimization
- Campaign analytics: open rate, reply rate, bounce rate, spam rate
- Account analytics: per-account health score, warmup status, reputation
- A/B winner: auto-declare after statistical significance, apply winner
- Sequence optimization: prune low-performing steps, extend high-performing ones
Output Format
Instantly playbook with: infrastructure checklist, campaign configuration, account management plan, inbox workflow, and optimization cadence.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Execution Artifacts
references/framework-notes.md— Eric infra, Pat verify gate, tool boundariestemplates/output-template.md— infrastructure + campaign + Clay gate deliverablescripts/check-output.py— local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand:references/clay-enrollment-handoff.md— Clay/loops → Instantly field map + verify gatereferences/eric-nowoslawski-outbound.md— infra at scale (Eric Nowoslawski)references/pat-spielmann-outbound-copy.md— verify-before-send (Pat Spielmann)- the
clay-toolkitskill — clay-toolkit upstream enrichment references/loop-catalog.md— signal loop routingreferences/gtm-experts-outbound-index.md— expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- Instantly Best Practices: apply only the part that directly improves the requested deliverable.
- Cold Email Infrastructure Standards: apply only the part that directly improves the requested deliverable.
- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Related Skills
- email-deliverability, domain-infrastructure, inbox-setup, cold-email-strategy, reply-handling
| 1 | |
| 2 | name instantly-sequences |
| 3 | description >- |
| 4 | Sets up and optimizes Instantly: sending accounts, warmup pool, campaign |
| 5 | settings, and the unified inbox. Use when the user is configuring Instantly |
| 6 | for cold email or diagnosing Instantly campaign performance. Triggers on: |
| 7 | "Instantly", "Instantly setup", "Instantly campaigns", "Instantly warmup". |
| 8 | license MIT |
| 9 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 10 | metadata |
| 11 | version "1.0.0" |
| 12 | author LeadMagic |
| 13 | category tools |
| 14 | tags [instantly, cold-email, warmup, outbound, campaigns] |
| 15 | frameworks |
| 16 | - "Instantly Help Center" |
| 17 | - "Eric Nowoslawski — Cold email infrastructure" |
| 18 | - "Google and Yahoo — Bulk sender requirements (2024)" |
| 19 | |
| 20 | |
| 21 | # Instantly Sequences |
| 22 | |
| 23 | ## Overview |
| 24 | Instantly competes with Smartlead in the high-volume cold email space. Key features: |
| 25 | unlimited email accounts, built-in warmup pool, campaign optimization, and a unified |
| 26 | inbox. This skill covers setup from infrastructure through optimization. |
| 27 | |
| 28 | ## Authoritative Foundations |
| 29 | **Instantly Help Center** — Connect sending accounts, enable warmup, and set per-account daily limits and campaign schedules before launch. |
| 30 | **Eric Nowoslawski — Cold email infrastructure** — Cold email infra at scale — 2 inboxes/domain, backup inboxes, Creative Ideas testing. |
| 31 | **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and honor unsubscribes quickly. |
| 32 | |
| 33 | ## When to Use |
| 34 | "Set up Instantly" |
| 35 | "Instantly campaign setup" |
| 36 | "Instantly warmup" |
| 37 | "Optimize Instantly campaigns" |
| 38 | |
| 39 | ## Step-by-Step Process |
| 40 | |
| 41 | ### Phase 1: Account Infrastructure |
| 42 | Buy secondary domains (never use primary domain) |
| 43 | Set up 2-3 Google Workspace or M365 mailboxes per domain |
| 44 | Configure DNS: SPF, DKIM, DMARC, custom tracking domain |
| 45 | Connect all mailboxes to Instantly |
| 46 | Begin warmup: Instantly auto-sends from your mailboxes to its warmup pool |
| 47 | and auto-replies to build reputation. Run 2-3 weeks before launching. |
| 48 | |
| 49 | ### Phase 2: Campaign Setup |
| 50 | **Import leads:** CSV upload with mapped fields, verify emails before sending |
| 51 | **Sequence builder:** Unlimited email steps, delays between 1-7 days |
| 52 | **A/B testing:** Up to 26 variants per campaign, auto-rotate, declare winner |
| 53 | **Sending schedule:** Mon-Fri with timezone optimization, max 50 emails/day/account |
| 54 | **Account rotation:** Auto-rotate across connected accounts, no account sends >50/day |
| 55 | |
| 56 | ### Phase 3: Campaign Rules |
| 57 | Auto-pause on X consecutive bounces |
| 58 | Auto-remove from sequence on unsubscribe request |
| 59 | Auto-label replies by sentiment (AI categorization) |
| 60 | Duplicate detection: don't send to the same email across campaigns |
| 61 | Blocklist management: automatically suppress unsubscribes across all campaigns |
| 62 | |
| 63 | ### Phase 4: Unified Inbox |
| 64 | All replies across all accounts in one view |
| 65 | Reply from any connected account in one interface |
| 66 | Auto-label: interested, not interested, OOO, wrong person |
| 67 | Lead status sync: update CRM based on reply categorization |
| 68 | |
| 69 | ### Phase 5: Optimization |
| 70 | Campaign analytics: open rate, reply rate, bounce rate, spam rate |
| 71 | Account analytics: per-account health score, warmup status, reputation |
| 72 | A/B winner: auto-declare after statistical significance, apply winner |
| 73 | Sequence optimization: prune low-performing steps, extend high-performing ones |
| 74 | |
| 75 | ## Output Format |
| 76 | Instantly playbook with: infrastructure checklist, campaign configuration, account |
| 77 | management plan, inbox workflow, and optimization cadence. |
| 78 | |
| 79 | |
| 80 | |
| 81 | ## Quality Check |
| 82 | |
| 83 | Before delivering, verify: |
| 84 | [ ] All required sections are complete |
| 85 | [ ] Output matches the user's stated need |
| 86 | [ ] Named frameworks are cited for key recommendations |
| 87 | [ ] No vague claims — every recommendation has a specific action |
| 88 | [ ] Deliverable is ready for operational use, not just conceptual |
| 89 | |
| 90 | ## Common Pitfalls |
| 91 | |
| 92 | **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables. |
| 93 | **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner. |
| 94 | **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority. |
| 95 | |
| 96 | ## Execution Artifacts |
| 97 | |
| 98 | `references/framework-notes.md` — Eric infra, Pat verify gate, tool boundaries |
| 99 | `templates/output-template.md` — infrastructure + campaign + Clay gate deliverable |
| 100 | `scripts/check-output.py` — local checklist validator for required sections |
| 101 | This skill includes lightweight artifacts the agent can load on demand: |
| 102 | `references/clay-enrollment-handoff.md` — Clay/loops → Instantly field map + verify gate |
| 103 | `references/eric-nowoslawski-outbound.md` — infra at scale (Eric Nowoslawski) |
| 104 | `references/pat-spielmann-outbound-copy.md` — verify-before-send (Pat Spielmann) |
| 105 | the `clay-toolkit` skill — clay-toolkit upstream enrichment |
| 106 | `references/loop-catalog.md` — signal loop routing |
| 107 | `references/gtm-experts-outbound-index.md` — expert router |
| 108 | Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice. |
| 109 | |
| 110 | ## Implementation Depth |
| 111 | |
| 112 | Use this section when the user asks for a finished asset, not a high-level explanation. |
| 113 | |
| 114 | ### Diagnostic Questions |
| 115 | |
| 116 | What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led? |
| 117 | Which ICP tier is the output for: small business, mid-market, enterprise, or mixed? |
| 118 | What proof is available today: customer stories, usage data, third-party validation, screenshots, or none? |
| 119 | What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow? |
| 120 | What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure? |
| 121 | |
| 122 | ### Framework Application |
| 123 | |
| 124 | Map the recommendation explicitly to the named frameworks in this skill: |
| 125 | |
| 126 | Instantly Best Practices: apply only the part that directly improves the requested deliverable. |
| 127 | Cold Email Infrastructure Standards: apply only the part that directly improves the requested deliverable. |
| 128 | Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable. |
| 129 | |
| 130 | ### Deliverable Standard |
| 131 | |
| 132 | A strong output from this skill includes: |
| 133 | |
| 134 | A crisp diagnosis of the current situation |
| 135 | A recommended path with tradeoffs, not a generic list |
| 136 | A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan |
| 137 | A measurement plan with leading and lagging indicators |
| 138 | Risks and edge cases called out before execution |
| 139 | |
| 140 | ### Adaptation Rules |
| 141 | |
| 142 | For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity. |
| 143 | For mid-market: include workflow ownership, handoffs, integrations, and enablement assets. |
| 144 | For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements. |
| 145 | |
| 146 | |
| 147 | ## Related Skills |
| 148 | email-deliverability, domain-infrastructure, inbox-setup, cold-email-strategy, reply-handling |
| 149 |
Discussion
Browse more free Claude skills.