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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capabilities described are somewhat high-level — it says 'configure' but doesn't enumerate specific concrete actions like writing workflow files, setting up schema checks, or configuring rover CLI. The explicit trigger phrases are a notable strength for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Configure GitHub Actions workflows for schema checks, set up rover CLI in pipelines, automate schema publishing and contract tests.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io CI/CD integration) and mentions some actions (automated testing, continuous integration, deployment pipelines), but doesn't list specific concrete actions like 'configure GitHub Actions workflows', 'set up test runners', or 'create deployment scripts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Apollo.io CI/CD integration) and 'when' (setting up automated testing, CI, or deployment pipelines) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'apollo ci', 'apollo github actions', 'apollo pipeline', 'apollo ci/cd', 'apollo automated tests'. These cover common variations and natural language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Apollo.io' with 'CI/CD' creates a very specific niche. The trigger terms are all Apollo-prefixed, making it unlikely to conflict with generic CI/CD skills or other Apollo-unrelated skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with complete, executable code for every step of the CI/CD pipeline setup. The workflow clarity is excellent with proper gating, health checks, and error handling. The main weakness is that the inline code is quite lengthy — the full test files could be split into referenced bundle files — and there's some unnecessary explanation of concepts Claude already understands.
Suggestions
Move the full MSW test file and integration test file into bundle reference files (e.g., templates/apollo.test.ts) and reference them from SKILL.md to improve progressive disclosure.
Trim the overview to remove explanations of what MSW mocks and sandbox tokens are — Claude already knows these concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary verbosity — the overview explains what MSW mocks and sandbox tokens do (Claude knows this), and the output section largely restates what the workflow already shows. The error handling table and resources section add some value but could be tighter. | 2 / 3 |
Actionability | Fully executable code throughout: complete GitHub Actions YAML, MSW test setup with TypeScript, integration test files, and CLI commands for secret management. Every step is copy-paste ready with specific file paths and real API endpoints. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation checkpoints: health check before integration tests, secret scanning as a separate job, MSW mocks for safe PR testing, and integration tests gated to main branch only. The workflow includes proper error recovery guidance in the error handling table and conditional execution logic. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~150 lines of code) with full test file implementations inline that could be referenced as separate files. The structure is well-organized with clear sections, but the MSW test and integration test code blocks are substantial and could be split into referenced files. The 'Next Steps' reference to apollo-deploy-integration is good but there are no bundle files to support it. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.