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

91%

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

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

A highly actionable, concise deployment skill with executable code, explicit pre-deploy validation, and rollback guidance. The main weakness is progressive disclosure: an implementation-guide reference bundle exists but is orphaned (never linked from the body), and platform-specific detail is inlined rather than offloaded to that reference.

Suggestions

Link the existing references/implementation-guide.md from the body (e.g., a '## Advanced' section pointing to it for AWS Lambda, blue-green, and multi-environment config) so the bundle is discoverable and signals one-level-deep navigation.

Move the per-platform deployment blocks (GCP, Vercel, Kubernetes) into the reference file, keeping SKILL.md as a lean overview plus the shared health-check pattern, to reduce the inline wall of code.

Reorder so pre-deploy validation (currently Step 5) is positioned before the deploy steps, making the validate-then-deploy sequence explicit in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code and commands with minimal explanatory prose, assumes Claude's competence (no definitions of Apollo, Kubernetes, or basic concepts), and every section earns its tokens; the short Output/Error-Handling tables add value without padding.	3 / 3
Actionability	Provides complete, copy-paste-ready artifacts across all targets — a working TypeScript health router, Dockerfile, gcloud/Vercel commands, k8s manifests, and a pre-deploy validation script — with no pseudocode placeholders.	3 / 3
Workflow Clarity	Steps 1-5 are explicitly sequenced and the production deployment includes real validation checkpoints (health endpoint verifying Apollo connectivity, a pre-deploy gate that exits non-zero on failure) plus rollback guidance in the error-handling table, satisfying the feedback-loop requirement for risky operations.	3 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists but is never linked or signaled from the body, and all three platform deployment configs are inlined in SKILL.md rather than split out, matching the anchor where references are present but not clearly signaled and content that could be separate is inline.	2 / 3
	Total	11 / 12 Passed

Description

90%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 tight, well-structured description that answers both what and when with explicit, natural trigger phrases and a clear niche. The only soft spot is specificity, where the named actions are somewhat overlapping and one is abstract rather than a distinct concrete capability.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io domain and several actions ('Deploy Apollo.io integrations to production', 'configuring production environments', 'setting up deployment pipelines'), but the actions overlap and 'configuring production environments' is abstract rather than a distinct concrete capability, so it falls short of the multi-specific-action anchor.	2 / 3
Completeness	Clearly states what it does ('Deploy Apollo.io integrations to production') and an explicit 'Use when' clause covering when to invoke it, satisfying both the what and when with explicit triggers.	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 likely natural-language triggers.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Apollo.io production deployment) with distinctive, product-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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-deploy-integration/SKILL.md
Commit: 0540a62

Reviewed: about 18 hours 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.