From apollo-pack
Configure Apollo.io CI/CD integration. Use when setting up automated testing, continuous integration, or deployment pipelines for Apollo integrations. Trigger with phrases like "apollo ci", "apollo github actions", "apollo pipeline", "apollo ci/cd", "apollo automated tests".
How this skill is triggered — by the user, by Claude, or both
Slash command
/apollo-pack:apollo-ci-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set up CI/CD pipelines for Apollo.io integrations with automated testing, secret management, and deployment workflows.
Set up CI/CD pipelines for Apollo.io integrations with automated testing, secret management, and deployment workflows.
apollo-install-auth setupFollow these high-level steps to implement apollo-ci-integration:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-ci-integration/references/implementation-guide.md)
| Issue | Resolution |
|---|---|
| Secret not found | Verify secret name in GitHub |
| Tests timeout | Increase timeout or mock API |
| Rate limited in CI | Use mocks for unit tests |
| Health check fails | Check Apollo status page |
Proceed to apollo-deploy-integration for deployment configuration.
Basic usage: Apply apollo ci integration to a standard project setup with default configuration options.
Advanced scenario: Customize apollo ci integration 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