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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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, copy-paste-ready validation code and a clear five-step sequence, but it is over-embedded for an overview and fails to surface the bundled implementation guide that already exists. Tightening the inline script and linking the reference would lift conciseness and progressive disclosure.

Suggestions

Replace much of the inline TypeScript in the body with a concise overview and link to references/implementation-guide.md (e.g., 'Full validation script: see implementation-guide.md'), so the overview stays lean.

Add an explicit remediation/feedback loop in the workflow (e.g., 'If checks fail, review the failing detail, apply the Error Handling table fix, then re-run prod:checklist') rather than relying on a single pass/fail exit code.

Add a one-line pointer in the body to the existing references/implementation-guide.md so the bundled runbook, rollback plan, and post-deploy verification are discoverable.

Dimension	Reasoning	Score
Conciseness	The body embeds a ~120-line TypeScript validation script inline rather than pointing to the bundled implementation-guide.md, so it assumes competence and avoids concept padding but is longer than a SKILL.md overview needs to be.	2 / 3
Actionability	Fully executable TypeScript (real axios calls, env checks, grep patterns, report generation with exit code) plus a concrete CI-gate npm example — copy-paste ready.	3 / 3
Workflow Clarity	Five steps are clearly sequenced and the report acts as a go/no-go gate via process.exit, but checks are grep-based pass/fail detection with implicit rather than explicit validate->fix->retry checkpoints.	2 / 3
Progressive Disclosure	A references/implementation-guide.md bundle exists with substantial content, but the body never signals or links to it, leaving that material undiscoverable and keeping inline content that should be split out.	2 / 3
	Total	9 / 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, complete, and distinctive, naming concrete deployment-readiness actions and providing natural trigger phrases that answer both what the skill does and when to use it. It uses clean third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Execute Apollo.io production deployment checklist', 'pre-launch verification', 'auditing production readiness' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Execute Apollo.io production deployment checklist') and when ('Use when preparing to deploy Apollo integrations to production...') with an explicit 'Use when' trigger clause.	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 coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Apollo.io-specific niche with distinct, well-scoped triggers; 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: 2 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.