apollo-ci-integration

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".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code and a well-sequenced, validated workflow, but it underuses progressive disclosure: the existing implementation-guide.md reference is not signaled from the body and substantial implementation detail is inlined inline.

Suggestions

Link to references/implementation-guide.md from the body (e.g., a 'Full implementation' pointer) so the bundled reference is discoverable and one level deep.

Move the full MSW and live integration test files into the reference, keeping only a representative excerpt in SKILL.md to reduce inline bulk.

Trim the inline workflow YAML to the job skeleton, offloading per-job step detail to the implementation guide.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but inlines two full test files and a complete workflow YAML that overlap with the bundled implementation-guide.md and could be tightened or offloaded.	2 / 3
Actionability	Provides copy-paste-ready, executable guidance: 'gh secret set' commands, a full GitHub Actions YAML workflow, and complete MSW/integration TypeScript test files.	3 / 3
Workflow Clarity	Steps 1-4 are clearly sequenced with explicit validation checkpoints (Apollo health check before integration tests, secret-scan job) and an error-handling table giving recovery feedback loops.	3 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists but is never linked or signaled from the body, and full implementation content is inlined rather than split out, matching the score-2 anchor of references present but not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-formed: third-person voice, explicit what/when structure, and concrete trigger phrases tied to a distinct Apollo CI/CD niche. Its only weakness is specificity, listing one action verb rather than several concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Apollo.io CI/CD integration') and a single action verb ('Configure'), plus scenarios in the 'Use when' clause, but does not enumerate multiple distinct concrete actions as the score-3 anchor requires.	2 / 3
Completeness	Clearly states what ('Configure Apollo.io CI/CD integration') and when ('Use when setting up automated testing, continuous integration, or deployment pipelines... Trigger with phrases like...'), satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Explicit trigger phrases ('apollo ci', 'apollo github actions', 'apollo pipeline', 'apollo ci/cd', 'apollo automated tests') give good coverage of natural terms a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The Apollo-specific niche and 'apollo'-prefixed triggers make it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/apollo-pack/skills/apollo-ci-integration/SKILL.md
Commit: 0540a62

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.