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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a well-sequenced, validation-backed CI workflow, but it is heavier than necessary because detailed implementation and full test files are inlined while an existing reference guide goes unused and unlinked.

Suggestions

Link references/implementation-guide.md from the body (e.g., a 'Full implementation details' pointer) and move the complete MSW and integration test files there, keeping only representative snippets inline to improve progressive disclosure and conciseness.

Trim the inline workflow YAML to the job skeleton and key gates, delegating the full file contents to the implementation guide to reduce token load.

Add a brief navigation line under Overview listing what each reference/bundle file contains so the bundle structure is clearly signaled.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes Claude's competence, but the body inlines two full TypeScript test files plus a complete workflow YAML, and the existing references/implementation-guide.md is never linked — content that could be tightened or delegated.	2 / 3
Actionability	Provides fully executable GitHub Actions YAML, concrete 'gh secret set' commands, a curl health check, complete MSW and integration test files, and a secret-scan grep — copy-paste ready with specific examples.	3 / 3
Workflow Clarity	Steps 1–4 are clearly sequenced with explicit validation checkpoints (health check exit-on-failure, secret-scan job, integration-tests gated to main via 'needs') and an error-handling table providing feedback loops.	3 / 3
Progressive Disclosure	Section organization is clear, but the bundled references/implementation-guide.md is never signaled or linked from the body, and content that could be split out remains inline — matching the score-2 anchor of structure present but references not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 specific, uses third-person imperative voice, and explicitly covers both capability and trigger conditions with natural user phrases. It is concise without padding and clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io CI/CD domain and lists multiple concrete action areas — 'automated testing, continuous integration, or deployment pipelines' — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly states what it does ('Configure Apollo.io CI/CD integration') and when to use it via an explicit 'Use when setting up...' clause plus trigger phrases, answering both what and when.	3 / 3
Trigger Term Quality	Explicitly enumerates natural phrases a user would say — 'apollo ci', 'apollo github actions', 'apollo pipeline', 'apollo ci/cd', 'apollo automated tests' — giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to Apollo.io CI/CD with 'apollo'-prefixed triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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
Commit: 02d6341

Reviewed: 3 days 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.