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

Quality

88%

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 body is highly actionable with executable code and a clear validated workflow, and avoids explaining concepts Claude already knows. Its weakness is progressive disclosure: an unused reference file and a large inline script mean the overview-to-reference split is underused.

Suggestions

Link references/implementation-guide.md from the body (e.g., a '## Deep dive' or '## Implementation guide' section pointing to it) so the bundled reference is actually surfaced.

Extract the repeated results.push check definitions into a small data table or a referenced script, keeping only the runner and report logic inline to tighten conciseness and the overview.

Consider moving the full prod-checklist.ts script into scripts/ and showing only the key check categories plus the run command in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly functional code with no concept-fluff, but it embeds a ~120-line script with twelve near-identical results.push blocks that repeat the category/name/pass/detail pattern; a data-driven table of checks would tighten it. It is efficient but could be materially trimmed, matching the score-2 anchor rather than the lean score-3.	2 / 3
Actionability	Provides fully executable TypeScript across every step and a copy-paste CI-gate example ('npm run prod:checklist && npm run deploy'); concrete commands and code rather than abstract description, meeting the score-3 anchor. Not score-2 because there is no pseudocode and no missing key details.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced and the generateReport pass/fail summary with process.exit code acts as an explicit validation checkpoint; the Error Handling table and CI-gate usage give a feedback loop. This satisfies the score-3 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	Sections are well organized, but a bundle file references/implementation-guide.md exists and is never referenced from the body, and the full checklist script is inline (~170 lines) rather than split out. This matches the score-2 anchor 'content that should be separate is inline' and references 'not clearly signaled'; not score-3 because the overview does not point cleanly into the provided reference.	2 / 3
	Total	10 / 12 Passed

Description

100%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.

A strong, concise description: third-person imperative voice, explicit what-and-when, and natural Apollo-specific trigger phrases. It follows the canonical good-example pattern with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Execute Apollo.io production deployment checklist', 'pre-launch verification', 'auditing production readiness' — rather than vague language; not the score-2 level that only names a domain and some actions.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via the 'Use when preparing to deploy... doing pre-launch verification, or auditing production readiness' clause plus explicit trigger phrases; clearly above the score-2 anchor where 'when' is only implied.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say ('apollo production checklist', 'deploy apollo', 'apollo go-live', 'apollo production ready', 'apollo launch checklist') with good variation; exceeds the score-2 'some relevant keywords' anchor.	3 / 3
Distinctiveness Conflict Risk	Apollo-scoped niche with distinct 'apollo' trigger terms makes it unlikely to fire for unrelated skills; well past the score-2 anchor that could still overlap with similar 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
Path: plugins/saas-packs/apollo-pack/skills/apollo-prod-checklist/SKILL.md
Commit: 4c47e33

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.