apollo-prod-checklist
Execute Apollo.io production deployment checklist. Use when preparing to deploy Apollo integrations to production, doing pre-launch verification, or auditing production readiness. Trigger with phrases like "apollo production checklist", "deploy apollo", "apollo go-live", "apollo production ready", "apollo launch checklist".
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 well-structured skill description with strong trigger terms and clear 'when' guidance, making it easy for Claude to select appropriately. Its main weakness is that the 'what' portion lacks specificity about the concrete actions the checklist involves — it tells you there's a checklist but not what's on it. Adding 2-3 specific checklist items would strengthen the description.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Verifies API authentication, validates webhook configurations, checks rate limit settings, confirms data mapping accuracy'
Consider mentioning what 'Apollo integrations' refers to more specifically (e.g., CRM sync, enrichment API, sequences) to further improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Apollo.io production deployment) and mentions some actions like 'pre-launch verification' and 'auditing production readiness', but doesn't list specific concrete actions (e.g., check API keys, verify webhooks, validate rate limits). 'Execute checklist' is somewhat vague about what the checklist actually contains. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute Apollo.io production deployment checklist, pre-launch verification, auditing production readiness) and 'when' (explicit 'Use when' clause with specific trigger scenarios and phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'apollo production checklist', 'deploy apollo', 'apollo go-live', 'apollo production ready', 'apollo launch checklist'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Apollo.io' and 'production deployment checklist' creates a very specific niche that is unlikely to conflict with other skills. The trigger terms are all Apollo-specific. | 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 solid, actionable production checklist skill with executable TypeScript code and clear workflow sequencing. Its main weakness is that the entire script is inlined in the SKILL.md body rather than being placed in a bundle file and referenced, making the document longer than necessary. The error handling table and CI gate example add practical value.
Suggestions
Move the full checklist script to a bundle file (e.g., src/scripts/prod-checklist.ts) and reference it from SKILL.md with a brief summary of what each step checks, rather than inlining all the code.
Remove the 'Output' section since it merely restates what the code already produces—the report format is self-evident from the generateReport function.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably focused but includes some unnecessary structural overhead (e.g., the 'Overview' paragraph restating what the skill does, the 'Output' section that just re-describes what the code already shows). The code itself is fairly lean but could be tightened—the fileContains helper and grep patterns are repeated verbosely across steps. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code that can be directly used as a production checklist script. Each check is concrete with specific grep patterns, API calls, and clear pass/fail criteria. The CI gate example at the end is copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 steps building toward a final report with explicit pass/fail validation. The report generation includes a feedback mechanism (exit code 1 for failures, 'BLOCKED — fix failing checks' message), and the error handling table provides clear resolution paths. The CI gate example shows how to use it as a deployment blocker. | 3 / 3 |
Progressive Disclosure | The skill references other skills ('apollo-install-auth', 'apollo-rate-limits', 'apollo-cost-tuning', 'apollo-upgrade-migration') and external resources, which is good. However, the entire checklist script is inlined in the SKILL.md rather than being referenced as a separate script file, making the body quite long. With no bundle files provided, the referenced skills and paths cannot be verified. | 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.