apollo-common-errors

Diagnose and fix common Apollo.io API errors. Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests. Trigger with phrases like "apollo error", "apollo api error", "debug apollo", "apollo 401", "apollo 429", "apollo troubleshoot".

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.

A highly actionable, well-sequenced diagnostic guide with concrete code and accurate Apollo-specific facts. Its main weaknesses are mild verbosity in repeated code patterns and a progressive-disclosure mismatch where real bundle files go unreferenced while a dangling bundle name is named.

Suggestions

Link the existing references/implementation-guide.md and references/implementation.md from the body and move the elaborate Step 6 middleware there, keeping SKILL.md as a lean overview.

Remove or fix the dangling 'apollo-debug-bundle' reference, since no such file exists in the bundle.

Add explicit validation checkpoints (e.g., 'after applying a fix, re-run the cURL diagnostic and confirm the status code changed') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and the domain facts (rate-limit windows, master vs standard keys, endpoint requirements) earn their place, but six full TypeScript blocks include near-duplicate diagnose functions and an elaborate middleware step that could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript handlers, concrete cURL diagnostics, specific endpoint lists, and numeric rate-limit tables — copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The six steps are clearly sequenced around a categorization gate, but validation checkpoints are implicit and there is no explicit verify-fix-revalidate loop, so it sits at the 'sequence present, checkpoints missing' anchor rather than the top.	2 / 3
Progressive Disclosure	Bundle reference files exist (implementation-guide.md, implementation.md) but the body never signals or links them, and the only forward reference ('apollo-debug-bundle') points to a non-existent file; substantial inline content that could live in those references keeps it below the top anchor.	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.

A strong, third-person description that states concrete capabilities, an explicit use-when clause, and natural trigger phrases scoped to a distinct Apollo niche. Voice is correctly third person with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to the domain — 'Diagnose and fix common Apollo.io API errors', 'debugging integration issues', 'troubleshooting failed requests' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both what ('Diagnose and fix common Apollo.io API errors') and when ('Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural phrases a user would actually say — 'apollo error', 'apollo api error', 'debug apollo', 'apollo 401', 'apollo 429', 'apollo troubleshoot' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Apollo-specific niche with status-code-specific triggers (apollo 401, apollo 429), 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: 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.