apollo-deploy-integration

Deploy Apollo.io integrations to production. Use when deploying Apollo integrations, configuring production environments, or setting up deployment pipelines. Trigger with phrases like "deploy apollo", "apollo production deploy", "apollo deployment pipeline", "apollo to production".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

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 complete, executable deployment code and reasonable sectioning, but it duplicates much of an unreferenced bundle file and places its validation step after the deploy steps. Tightening the inline volume and wiring in the reference file would meaningfully improve it.

Suggestions

Reference references/implementation-guide.md from the body (e.g., a 'Full implementation guide' pointer under each platform section) so the bundle file is discoverable instead of orphaned.

Reorder so the pre-deploy validation runs as a checkpoint before the platform deploy steps (Step 2-4), not as a trailing Step 5, and state explicitly 'run pre-deploy check; only deploy when it passes'.

Offload the full per-platform manifests into the reference file and keep the body to a concise overview per platform to reduce inline duplication and token cost.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and avoids explaining basics Claude already knows, but it inlines substantial platform-specific code that overlaps the existing (yet unreferenced) bundle file and could be tightened by offloading detail. This fits 'mostly efficient but could be tightened' rather than 'every token earns its place'.	2 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts — a TypeScript health router, a multi-stage Dockerfile, gcloud/vercel commands, vercel.json, Kubernetes manifests, and a pre-deploy validation script — with specific commands and obvious placeholders only where expected.	3 / 3
Workflow Clarity	Steps are sequenced and a pre-deploy validation script plus an error-handling/rollback table exist, but the validation is detached as 'Step 5' after the deploy steps rather than wired in as a pre-deploy checkpoint, leaving validation implicit in the actual flow.	2 / 3
Progressive Disclosure	A bundle file (references/implementation-guide.md) exists but is never referenced from the body, and content that overlaps it (health, GCP, Vercel, K8s, pre-deploy) is inlined rather than split out — 'references present but not clearly signaled; content that should be separate is inline'.	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 third-person, concise, and clearly states both what the skill does and when to use it, with natural Apollo-specific trigger phrases. It is distinguishable from other skills and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions on a specific domain — 'Deploy Apollo.io integrations to production', 'configuring production environments', 'setting up deployment pipelines' — matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' ('Deploy Apollo.io integrations to production') and 'when' with an explicit 'Use when...' clause plus trigger phrases, matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say ('deploy apollo', 'apollo production deploy', 'apollo deployment pipeline', 'apollo to production'), giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Apollo.io deployment niche with Apollo-specific triggers, making it 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: 4 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.