sales-apollo

Name: sales-apollo
Author: sales-skills

86stars9forks

How to install sales-apollo?

sales-skills/sales/sales-apollo

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

Installs into the current project.

Summary

Apollo.io platform help — config, integrations, CRM sync, API, analytics, dialer, Chrome extension, credit management, admin. Use when Apollo settings aren't configured right, CRM sync is breaking or duplicating records, running out of credits too fast, API calls returning errors

Files · 1

View on GitHub

SKILL.md

1	# Apollo.io Platform Help
2
3	Help the user with Apollo.io platform questions — from configuration and CRM sync through analytics, dialer, API, and credit management.
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 area of Apollo do you need help with?
13	- A) Prospecting & Search — finding and filtering leads (hand off: `/sales-prospect-list {your question}`)
14	- B) Enrichment — getting emails, phones, firmographic data (hand off: `/sales-enrich {your question}`)
15	- C) Sequences — outbound email/call sequences (for Apollo mechanics, `/sales-cadence` for strategy, hand off: `/sales-apollo-sequences {your question}`)
16	- D) Intent & Signals — buying intent, job changes, lead scoring (hand off: `/sales-intent {your question}`)
17	- E) Dialer — click-to-call, parallel dialing, call recording
18	- F) Analytics — reports, dashboards, sequence performance
19	- G) CRM Sync — Salesforce/HubSpot integration, field mapping, sync issues
20	- H) Chrome Extension — LinkedIn prospecting, website visitor identification
21	- I) Credits & Billing — credit management, usage, plan limits
22	- J) API & Integrations — REST API, Zapier, webhooks
23	- K) Admin — user management, teams, permissions, SSO
24	- L) Something else — describe it
25
26	2. What's your role?
27	- A) Sales rep / AE / BDR
28	- B) Sales manager / team lead
29	- C) RevOps / Sales Ops
30	- D) Admin / IT
31	- E) Founder / solo seller
32	- F) Other
33
34	3. What are you trying to accomplish? (describe your specific goal or question)
35
36	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.
37
38	Note: If the user needs one of the specialized skills, route them there with a brief explanation of why that skill is a better fit.
39
40	## Step 2 — Route or answer directly
41
42	If the request maps to a specialized skill, route:
43	- List building / prospecting → `/sales-prospect-list`
44	- Contact enrichment / data hygiene → `/sales-enrich`
45	- Intent signals / lead scoring → `/sales-intent`
46	- Sequence strategy / cadence design → `/sales-cadence`
47	- Apollo sequence mechanics → `/sales-apollo-sequences`
48
49	Otherwise, answer directly from platform knowledge using the reference below.
50
51	## Step 3 — Apollo platform reference
52
53	Read `references/platform-guide.md` for the full module-by-module reference — Dialer, Analytics &
54	Reporting, CRM Sync, Chrome Extension, Credits & Billing, the Apollo data model, API & Integrations, the
55	MCP tools for direct Apollo access (Composio, Membrane), and Admin & Settings. For the full API endpoint
56	catalog, auth, and rate limits, see `references/apollo-api-reference.md`.
57
58	Answer using only the relevant section — don't dump the full reference.
59
60	## Step 4 — Actionable guidance
61
62	Based on the user's specific question:
63
64	1. Step-by-step instructions — numbered steps to accomplish their goal in Apollo
65	2. Configuration recommendations — specific settings to change, with where to find them (Settings > [section] > [page])
66	3. Common pitfalls — what can go wrong and how to avoid it
67	4. Verification — how to confirm the change worked
68	5. For API questions — always end your response with this exact line: "For the full endpoint catalog, request/response schemas, and rate limits, see `references/apollo-api-reference.md`." This citation is mandatory even when you provide inline code examples.
69
70	## Gotchas
71
72	- Don't confuse Apollo's database search with enrichment. Searching for people is free and doesn't consume credits. Enrichment (revealing emails/phones) consumes credits. Claude often generates workflows that search + enrich in one step without warning about credit costs.
73	- Don't assume all Apollo features are available on all plans. Dialer requires Professional+, parallel dialing requires Organization, SSO requires Organization, custom reporting requires Organization. Always ask about the user's plan before recommending gated features.
74	- **Don't recommend the Chrome e

People who liked this also viewed

6 picks

Type

sales-apollo

86stars9forks

View on GitHub

How to install sales-apollo?

sales-skills/sales/sales-apollo

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Apollo.io Platform Help
2
3	Help the user with Apollo.io platform questions — from configuration and CRM sync through analytics, dialer, API, and credit management.
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 area of Apollo do you need help with?
13	- A) Prospecting & Search — finding and filtering leads (hand off: `/sales-prospect-list {your question}`)
14	- B) Enrichment — getting emails, phones, firmographic data (hand off: `/sales-enrich {your question}`)
15	- C) Sequences — outbound email/call sequences (for Apollo mechanics, `/sales-cadence` for strategy, hand off: `/sales-apollo-sequences {your question}`)
16	- D) Intent & Signals — buying intent, job changes, lead scoring (hand off: `/sales-intent {your question}`)
17	- E) Dialer — click-to-call, parallel dialing, call recording
18	- F) Analytics — reports, dashboards, sequence performance
19	- G) CRM Sync — Salesforce/HubSpot integration, field mapping, sync issues
20	- H) Chrome Extension — LinkedIn prospecting, website visitor identification
21	- I) Credits & Billing — credit management, usage, plan limits
22	- J) API & Integrations — REST API, Zapier, webhooks
23	- K) Admin — user management, teams, permissions, SSO
24	- L) Something else — describe it
25
26	2. What's your role?
27	- A) Sales rep / AE / BDR
28	- B) Sales manager / team lead
29	- C) RevOps / Sales Ops
30	- D) Admin / IT
31	- E) Founder / solo seller
32	- F) Other
33
34	3. What are you trying to accomplish? (describe your specific goal or question)
35
36	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.
37
38	Note: If the user needs one of the specialized skills, route them there with a brief explanation of why that skill is a better fit.
39
40	## Step 2 — Route or answer directly
41
42	If the request maps to a specialized skill, route:
43	- List building / prospecting → `/sales-prospect-list`
44	- Contact enrichment / data hygiene → `/sales-enrich`
45	- Intent signals / lead scoring → `/sales-intent`
46	- Sequence strategy / cadence design → `/sales-cadence`
47	- Apollo sequence mechanics → `/sales-apollo-sequences`
48
49	Otherwise, answer directly from platform knowledge using the reference below.
50
51	## Step 3 — Apollo platform reference
52
53	Read `references/platform-guide.md` for the full module-by-module reference — Dialer, Analytics &
54	Reporting, CRM Sync, Chrome Extension, Credits & Billing, the Apollo data model, API & Integrations, the
55	MCP tools for direct Apollo access (Composio, Membrane), and Admin & Settings. For the full API endpoint
56	catalog, auth, and rate limits, see `references/apollo-api-reference.md`.
57
58	Answer using only the relevant section — don't dump the full reference.
59
60	## Step 4 — Actionable guidance
61
62	Based on the user's specific question:
63
64	1. Step-by-step instructions — numbered steps to accomplish their goal in Apollo
65	2. Configuration recommendations — specific settings to change, with where to find them (Settings > [section] > [page])
66	3. Common pitfalls — what can go wrong and how to avoid it
67	4. Verification — how to confirm the change worked
68	5. For API questions — always end your response with this exact line: "For the full endpoint catalog, request/response schemas, and rate limits, see `references/apollo-api-reference.md`." This citation is mandatory even when you provide inline code examples.
69
70	## Gotchas
71
72	- Don't confuse Apollo's database search with enrichment. Searching for people is free and doesn't consume credits. Enrichment (revealing emails/phones) consumes credits. Claude often generates workflows that search + enrich in one step without warning about credit costs.
73	- Don't assume all Apollo features are available on all plans. Dialer requires Professional+, parallel dialing requires Organization, SSO requires Organization, custom reporting requires Organization. Always ask about the user's plan before recommending gated features.
74	- **Don't recommend the Chrome e

People who liked this also viewed

6 picks

Type