CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

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.

The content is highly actionable with executable code and a clear error-categorized workflow, but it is longer than necessary and its progressive-disclosure structure is broken: real bundle files go unreferenced while the only pointer targets a non-existent bundle.

Suggestions

Link the existing references/ files (e.g., implementation-guide.md) from the body or remove them, and either create the referenced 'apollo-debug-bundle' or point 'Next Steps' at a real file to fix the dangling reference.

Tighten the body by moving the full error-reference table and middleware code into a reference file, keeping SKILL.md as a concise overview of the per-status diagnostic steps.

Reduce redundancy between the per-step code blocks and the duplicated 'Common 401 causes' / error-table content.

DimensionReasoningScore

Conciseness

The body is code-dense and avoids explaining concepts Claude already knows, but six full TypeScript blocks plus a per-status error table repeat information that could be tightened; it is mostly efficient rather than lean.

2 / 3

Actionability

Provides fully executable TypeScript handlers, copy-paste cURL diagnostics, and a concrete error-reference table — guidance is specific and copy-paste ready.

3 / 3

Workflow Clarity

A clear Step 1 (categorize) through Step 6 (middleware) decision sequence keyed by error code; being diagnostic rather than destructive, the missing-validation cap does not apply.

3 / 3

Progressive Disclosure

The ~230-line body is monolithic, the actual references (implementation-guide.md, implementation.md) are never linked from the body, and the sole forward reference ('apollo-debug-bundle') does not exist — references are present but not correctly signaled.

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.

The description is well-constructed: third-person voice, clear what/when structure, and strong natural trigger phrases. Its only weakness is that the action statement ('Diagnose and fix') is somewhat generic rather than listing concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and two actions ('Diagnose and fix common Apollo.io API errors') but does not enumerate multiple specific concrete actions, so it falls short of the comprehensive anchor 3.

2 / 3

Completeness

Explicitly states both what it does ('Diagnose and fix common Apollo.io API errors') and when to use it ('Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests') with explicit triggers.

3 / 3

Trigger Term Quality

Lists natural phrases users 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 niche (Apollo.io API errors) with distinct, domain-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.