From apollo-pack
Implement Apollo.io lead search and enrichment workflow. Use when building lead generation features, searching for contacts, or enriching prospect data from Apollo. Trigger with phrases like "apollo lead search", "search apollo contacts", "find leads in apollo", "apollo people search", "enrich contacts apollo".
How this skill is triggered — by the user, by Claude, or both
Slash command
/apollo-pack:apollo-core-workflow-aThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement the primary Apollo.io workflow for searching leads and enriching contact/company data. This is the core use case for B2B sales intelligence.
Implement the primary Apollo.io workflow for searching leads and enriching contact/company data. This is the core use case for B2B sales intelligence.
apollo-sdk-patterns setupFollow these high-level steps to implement apollo-core-workflow-a:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-core-workflow-a/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| Empty Results | Too narrow criteria | Broaden search parameters |
| Missing Emails | Contact not in database | Try LinkedIn enrichment |
| Rate Limited | Too many enrichment calls | Implement batching |
| Invalid Domain | Domain doesn't exist | Validate domains first |
Proceed to apollo-core-workflow-b for email sequences and outreach.
Basic usage: Apply apollo core workflow a to a standard project setup with default configuration options.
Advanced scenario: Customize apollo core workflow a for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin apollo-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026