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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 code and a clear step sequence, but it leans verbose by embedding two full client implementations inline and lacks explicit feedback-loop validation. No bundle files exist, so progressive disclosure rests on sectioning alone.

Suggestions

Collapse the duplicate TypeScript and Python client implementations — present one inline and move the other (or a shared reference) into a bundle file under references/ to reduce token cost.

Convert the verify step into an explicit validate-and-branch loop (verify auth → if invalid, diagnose via the error table → re-verify) rather than logging a single pass/fail message.

Move the explanatory prose about REST-only integration and basic SDK concepts out of the Overview, keeping only the auth header and base URL facts Claude cannot infer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-forward, but it duplicates full client implementations in both TypeScript and Python and includes explanatory prose ('There is no official SDK — all integrations use the REST API directly') and inline concepts Claude already knows, so it could be tightened.	2 / 3
Actionability	Executable, copy-paste-ready install commands and complete TypeScript/Python client code plus a cURL example provide fully concrete guidance with specific endpoints and headers.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and include a verify-auth checkpoint, but the connect/verify step prints rather than branching on success, and destructive/batch operations lack an explicit validate-fix-retry feedback loop, leaving checkpoints somewhat implicit.	2 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline in a single file with no bundle files or one-level-deep references separating the duplicated client code; the duplicated TS/Python implementations are content that could 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 well-triggered with natural user phrases, giving a clear what-and-when picture scoped to Apollo.io authentication. It avoids vague language and over-claims while remaining concise.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Install and configure Apollo.io API authentication', 'setting up a new Apollo integration, configuring API keys, or initializing Apollo client' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It explicitly answers what ('Install and configure Apollo.io API authentication') and when ('Use when setting up a new Apollo integration...Trigger with phrases like...'), satisfying both halves with explicit trigger guidance.	3 / 3
Trigger Term Quality	Trigger phrases 'install apollo', 'setup apollo api', 'apollo authentication', 'configure apollo api key' are natural terms a user would say, providing good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The narrow Apollo.io-auth niche with distinct Apollo-specific trigger phrases makes it unlikely to fire for unrelated skills, matching the clear-niche anchor.	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: 1 day 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.