From apollo-pack
Implement Apollo.io email sequences and outreach workflow. Use when building automated email campaigns, creating sequences, or managing outreach through Apollo. Trigger with phrases like "apollo email sequence", "apollo outreach", "apollo campaign", "apollo sequences", "apollo automated emails".
How this skill is triggered — by the user, by Claude, or both
Slash command
/apollo-pack:apollo-core-workflow-bThis 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 Apollo.io's email sequencing and outreach automation capabilities for B2B sales campaigns.
Implement Apollo.io's email sequencing and outreach automation capabilities for B2B sales campaigns.
apollo-core-workflow-a (lead search)Follow these high-level steps to implement apollo-core-workflow-b:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-core-workflow-b/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| Email Not Connected | No sending account | Connect email in Apollo UI |
| Contact Already in Sequence | Duplicate enrollment | Check before adding |
| Invalid Email Template | Missing variables | Validate template syntax |
| Sequence Limit Reached | Plan limits | Upgrade plan or archive sequences |
Proceed to apollo-common-errors for error handling patterns.
Basic usage: Apply apollo core workflow b to a standard project setup with default configuration options.
Advanced scenario: Customize apollo core workflow b 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