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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-prod-checklist87
Quality
83%
Does it follow best practices?
Impact
99%
2.53xAverage score across 3 eval scenarios
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 excellent trigger term coverage and clear 'what/when' guidance. The main weakness is the lack of specific concrete actions - it tells us it's a 'checklist' but doesn't enumerate what the checklist actually covers (e.g., API validation, webhook testing, data sync verification).
Suggestions
Add 2-3 specific checklist items to improve specificity, e.g., 'Verifies API credentials, tests webhook configurations, validates data sync settings, checks rate limits.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io production deployment) and mentions actions like 'pre-launch verification' and 'auditing production readiness', but doesn't list specific concrete actions like 'verify API keys', 'test webhooks', or 'validate data sync'. | 2 / 3 |
Completeness | Clearly answers both what ('Execute Apollo.io production deployment checklist') and when ('Use when preparing to deploy Apollo integrations to production, doing pre-launch verification, or auditing production readiness') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases including 'apollo production checklist', 'deploy apollo', 'apollo go-live', 'apollo production ready', and 'apollo launch checklist' - these are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io production deployments specifically. The combination of 'Apollo' + 'production' + 'deployment/checklist' creates a distinct trigger profile unlikely to conflict with general deployment or other integration 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 production checklist skill with excellent actionability and workflow clarity. The executable validation scripts, clear checklists, and runbook table provide concrete guidance. However, the skill is somewhat lengthy and could benefit from extracting the larger code blocks into referenced files to improve progressive disclosure and reduce token usage.
Suggestions
Extract the validation script (validate-production.ts) to a separate referenced file to reduce inline content length
Consider condensing the TypeScript examples by removing some of the verbose comments and console output formatting
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the validation script is quite lengthy and could be more condensed. The checklists and runbook tables are appropriately concise, but the TypeScript examples could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash scripts, TypeScript code, and specific curl commands. The validation script is copy-paste ready with concrete checks, and the runbook table gives specific commands for each scenario. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit validation checkpoints: pre-deployment checklist → validation script → post-deployment verification → rollback plan. Each phase has concrete verification steps and the validation script includes pass/fail/warn feedback loops. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long and monolithic. The validation script and feature flags code could be referenced as separate files rather than inline. Only one external reference (apollo-upgrade-migration) is mentioned. | 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 | |
- 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.