apollo-install-auth

Install and configure Apollo.io API authentication. Use when setting up a new Apollo integration, configuring API keys, or initializing Apollo client in your project. Trigger with phrases like "install apollo", "setup apollo api", "apollo authentication", "configure apollo api key".

Quality

83%

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.

A highly actionable, well-sequenced skill body with executable code and a real verification checkpoint. It loses points on conciseness and progressive disclosure because both full TypeScript and Python clients sit inline in one ~170-line file rather than one being referenced from a bundle file.

Suggestions

Keep one canonical client implementation (e.g., TypeScript) inline and move the other into a references/ file (e.g., references/apollo_client_python.md) linked from the relevant step, reducing duplication and token load.

Tighten the Instructions by collapsing Steps 3–5 so the verify checkpoint applies to both language clients in a single coherent flow, rather than placing the Python client after the verification step.

Consider moving the full error-handling table and cURL example into a references/ file, leaving the SKILL.md body as a lean overview that points to the detail.

Dimension	Reasoning	Score
Conciseness	The prose is lean and free of concept-explanation padding, but shipping two complete client implementations (a TypeScript createApolloClient and a full Python ApolloClient class) is duplicative across languages and could be tightened to one canonical example plus a note.	2 / 3
Actionability	It provides fully executable install commands, complete TypeScript and Python clients, a copy-paste cURL verification, and a concrete error-handling table with specific causes and solutions.	3 / 3
Workflow Clarity	Steps are clearly numbered (install → configure key → create client → verify → Python client) with an explicit Verify Connection checkpoint that catches 401s and points the user to regenerate the key, plus error-recovery guidance in the table.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the skill is a ~170-line monolithic single file with no bundle references, and the two full language implementations are inline content that could be split out for a leaner overview.	2 / 3
	Total	10 / 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 strong, well-structured description that clearly states what the skill does and when to use it, with explicit natural-language triggers and a distinct Apollo-auth niche. The only soft spot is specificity, where the action set is narrow rather than a comprehensive list of concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete actions — 'Install and configure Apollo.io API authentication' — but only two verbs applied to a single narrow task, not the multiple distinct concrete actions the level-3 anchor calls for.	2 / 3
Completeness	It explicitly answers both what ('Install and configure Apollo.io API authentication') and when ('Use when setting up a new Apollo integration, configuring API keys...'), with an explicit 'Use when' clause and trigger guidance.	3 / 3
Trigger Term Quality	It lists natural phrases a user would actually say — 'install apollo', 'setup apollo api', 'apollo authentication', 'configure apollo api key' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It is scoped to a clear niche (Apollo.io API authentication) with Apollo-specific, auth-focused triggers unlikely to fire for sibling skills like apollo-hello-world or apollo-rate-limits.	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-install-auth/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.