sales-apollo-sequences

Name: sales-apollo-sequences
Author: sales-skills

86stars9forks

How to install sales-apollo-sequences?

sales-skills/sales/sales-apollo-sequences

$npx -y skills add sales-skills/sales --skill sales-apollo-sequences

Installs into the current project.

Summary

Manages outbound sequences in Apollo.io — create, configure, optimize deliverability, and analyze performance. Use when Apollo emails are going to spam, sequence open rates are low, A/B tests aren't producing clear winners, mailboxes keep getting throttled, sequence stats don't l

Files · 1

View on GitHub

SKILL.md

1	# Manage Apollo Sequences
2
3	Help the user create, configure, and optimize outbound sequences in Apollo.io — from sequence setup through deliverability management, A/B testing, and performance analysis. For cadence strategy and messaging content, use `/sales-cadence` — this skill covers the Apollo-specific execution layer.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. What do you need help with?
13	- A) Create a new sequence from scratch
14	- B) Fix deliverability issues (emails going to spam, low open rates)
15	- C) Set up A/B testing in a sequence
16	- D) Analyze sequence performance and optimize
17	- E) Configure mailboxes and sending settings
18	- F) Troubleshoot a sequence that's not sending
19	- G) Import a sequence from another tool
20	- H) Other — describe it
21
22	2. What's your current setup?
23	- How many mailboxes/email accounts are connected?
24	- What's your daily sending volume per mailbox?
25	- How long have the mailboxes been active?
26	- Are SPF, DKIM, and DMARC configured for your sending domain?
27
28	3. What Apollo plan are you on?
29	- Free (2 active sequences, limited features)
30	- Basic (unlimited sequences, no A/B testing)
31	- Professional (A/B testing, dialer, workflows)
32	- Organization (advanced analytics, custom reports)
33
34	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
35
36	## Step 2 — Sequence setup in Apollo
37
38	Read `references/platform-guide.md` for detailed module documentation, pricing, integrations, and data model.
39
40	Key settings — configure these for every sequence (non-negotiable):
41
42	- Stop on reply: Always enable. Auto-pause the sequence when a prospect replies. There is zero reason to keep emailing someone who responded — it damages trust and wastes sends.
43	- Stop on meeting booked: Always enable. Once the goal is achieved, stop the sequence.
44	- Business hours sending: Always enable. Send during the recipient's business hours (typically 8am-6pm in their timezone). Emails arriving at 2am look automated and get buried.
45	- Daily send limits: Start conservative — 50-100 emails/day per mailbox for warm, established mailboxes. For new mailboxes, start at 20-30/day and ramp up over 2-3 weeks. Exceeding safe limits tanks sender reputation fast.
46	- Delay between steps: Use 2-3 business days between email steps. Shorter gaps feel aggressive; longer gaps lose momentum. Increase to 4-5 days after 3+ unreplied emails to avoid fatigue.
47	- Sequence type: Use Automatic for email-only sequences (hands-off, sends on schedule). Use Manual for multi-channel sequences that include calls or LinkedIn steps — Auto mode skips non-email steps entirely.
48
49	For full cadence strategy — including messaging arc, multi-channel touch patterns, and email copy — use `/sales-cadence`.
50
51	You no longer need the platform guide details — focus on the user's specific situation.
52
53	## Gotchas
54
55	- Don't launch sequences without verifying domain authentication. Claude often generates sequence setup guides without checking SPF/DKIM/DMARC. Missing domain auth is the #1 cause of emails landing in spam. Check it before anything else.
56	- Don't set high daily sending limits on new mailboxes. New mailboxes must be ramped up gradually (20-30/day → 50-75/day over 2-3 weeks). Claude defaults to recommending 100+ sends/day, which will tank deliverability on a fresh mailbox.
57	- Don't use Apollo's "Auto" sequence type for multi-channel cadences. Auto sequences only work for email steps. If the cadence includes calls or LinkedIn touches, use "Manual" sequence type — otherwise those steps are skipped entirely.
58	- Don't evaluate A/B tests too early. Claude will analyze test results after 30-40 sends. You need at least 100 sends per variant for statistically meaningful results. Premature conclusions lead to wrong optimizations.
59	- Don't ignore the Deliverability Command Center. Apollo has

People who liked this also viewed

6 picks

Type

sales-apollo-sequences

86stars9forks

View on GitHub

How to install sales-apollo-sequences?

sales-skills/sales/sales-apollo-sequences

$npx -y skills add sales-skills/sales --skill sales-apollo-sequences

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Manage Apollo Sequences
2
3	Help the user create, configure, and optimize outbound sequences in Apollo.io — from sequence setup through deliverability management, A/B testing, and performance analysis. For cadence strategy and messaging content, use `/sales-cadence` — this skill covers the Apollo-specific execution layer.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. What do you need help with?
13	- A) Create a new sequence from scratch
14	- B) Fix deliverability issues (emails going to spam, low open rates)
15	- C) Set up A/B testing in a sequence
16	- D) Analyze sequence performance and optimize
17	- E) Configure mailboxes and sending settings
18	- F) Troubleshoot a sequence that's not sending
19	- G) Import a sequence from another tool
20	- H) Other — describe it
21
22	2. What's your current setup?
23	- How many mailboxes/email accounts are connected?
24	- What's your daily sending volume per mailbox?
25	- How long have the mailboxes been active?
26	- Are SPF, DKIM, and DMARC configured for your sending domain?
27
28	3. What Apollo plan are you on?
29	- Free (2 active sequences, limited features)
30	- Basic (unlimited sequences, no A/B testing)
31	- Professional (A/B testing, dialer, workflows)
32	- Organization (advanced analytics, custom reports)
33
34	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
35
36	## Step 2 — Sequence setup in Apollo
37
38	Read `references/platform-guide.md` for detailed module documentation, pricing, integrations, and data model.
39
40	Key settings — configure these for every sequence (non-negotiable):
41
42	- Stop on reply: Always enable. Auto-pause the sequence when a prospect replies. There is zero reason to keep emailing someone who responded — it damages trust and wastes sends.
43	- Stop on meeting booked: Always enable. Once the goal is achieved, stop the sequence.
44	- Business hours sending: Always enable. Send during the recipient's business hours (typically 8am-6pm in their timezone). Emails arriving at 2am look automated and get buried.
45	- Daily send limits: Start conservative — 50-100 emails/day per mailbox for warm, established mailboxes. For new mailboxes, start at 20-30/day and ramp up over 2-3 weeks. Exceeding safe limits tanks sender reputation fast.
46	- Delay between steps: Use 2-3 business days between email steps. Shorter gaps feel aggressive; longer gaps lose momentum. Increase to 4-5 days after 3+ unreplied emails to avoid fatigue.
47	- Sequence type: Use Automatic for email-only sequences (hands-off, sends on schedule). Use Manual for multi-channel sequences that include calls or LinkedIn steps — Auto mode skips non-email steps entirely.
48
49	For full cadence strategy — including messaging arc, multi-channel touch patterns, and email copy — use `/sales-cadence`.
50
51	You no longer need the platform guide details — focus on the user's specific situation.
52
53	## Gotchas
54
55	- Don't launch sequences without verifying domain authentication. Claude often generates sequence setup guides without checking SPF/DKIM/DMARC. Missing domain auth is the #1 cause of emails landing in spam. Check it before anything else.
56	- Don't set high daily sending limits on new mailboxes. New mailboxes must be ramped up gradually (20-30/day → 50-75/day over 2-3 weeks). Claude defaults to recommending 100+ sends/day, which will tank deliverability on a fresh mailbox.
57	- Don't use Apollo's "Auto" sequence type for multi-channel cadences. Auto sequences only work for email steps. If the cadence includes calls or LinkedIn touches, use "Manual" sequence type — otherwise those steps are skipped entirely.
58	- Don't evaluate A/B tests too early. Claude will analyze test results after 30-40 sends. You need at least 100 sends per variant for statistically meaningful results. Premature conclusions lead to wrong optimizations.
59	- Don't ignore the Deliverability Command Center. Apollo has

People who liked this also viewed

6 picks

Type