exa-common-errors

Diagnose and fix Exa API errors by HTTP code and error tag. Use when encountering Exa errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "exa error", "fix exa", "exa not working", "debug exa", "exa 429", "exa 401".

Quality

82%

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

65%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 body is highly actionable with executable code and a well-organized error reference, but it loses points on conciseness and workflow_clarity, and its two bundle references are broken (the files do not exist).

Suggestions

Create the referenced exa-debug-bundle and exa-rate-limits files under references/ (or remove the Next Steps pointers), so progressive-disclosure references resolve to real bundles.

Tighten conciseness by collapsing the redundant "Instructions" section and trimming the inline backoff/curl blocks to the essential lines, offloading full patterns to the rate-limits bundle.

Add a validation/feedback step to the workflow (e.g., after applying a fix, re-run the diagnostic script to confirm the HTTP code is 200) so workflow_clarity clears the validation checkpoint bar.

Dimension	Reasoning	Score
Conciseness	Dense and mostly earns its tokens (tables, executable snippets), but the embedded full backoff function, a second curl test block, and an "Instructions" section that restates what the tables already imply keep it just short of "every token earns its place."	2 / 3
Actionability	Executable curl with the x-api-key header, a complete TypeScript searchWithBackoff function, a set -euo pipefail diagnostic script, and per-row Solution columns give copy-paste-ready guidance.	3 / 3
Workflow Clarity	A 4-step sequence exists, but the live diagnostic and fix operations have no validation checkpoint or verify-after-fix feedback loop; per the rubric, missing validation for live-request operations caps this at 2.	2 / 3
Progressive Disclosure	"Next Steps" signals one-level-deep follow-ups, but neither referenced bundle (exa-debug-bundle, exa-rate-limits) exists in references/scripts/assets, and ~80 lines of inline error reference could live in a separate file.	2 / 3
	Total	9 / 12 Passed

Description

100%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 specific, complete, and distinct: it names concrete actions, gives explicit use-when triggers with natural phrases, and occupies a clear Exa-specific niche. No significant weaknesses in the frontmatter description.

Dimension	Reasoning	Score
Specificity	"Diagnose and fix Exa API errors by HTTP code and error tag" plus "debugging failed requests" and "troubleshooting integration issues" lists multiple concrete, specific actions rather than vague language.	3 / 3
Completeness	Answers both what ("Diagnose and fix Exa API errors by HTTP code and error tag") and when ("Use when encountering Exa errors, debugging failed requests, or troubleshooting integration issues") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Explicit "Trigger with phrases like 'exa error', 'fix exa', 'exa not working', 'debug exa', 'exa 429', 'exa 401'" gives good coverage of natural phrases a user would say.	3 / 3
Distinctiveness Conflict Risk	Scoped to Exa API errors with Exa-specific triggers ("exa 429", "exa 401"), making it a clear niche unlikely to fire for other 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
Path: plugins/saas-packs/exa-pack/skills/exa-common-errors/SKILL.md
Commit: 0540a62

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.