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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels in completeness and distinctiveness. It clearly identifies the domain (Exa API), provides explicit 'Use when' guidance, and includes natural trigger phrases. The main area for improvement is listing more specific concrete actions beyond 'diagnose and fix'.
Suggestions
Add more specific concrete actions, e.g., 'Diagnose and fix Exa API errors including rate limiting (429), authentication failures (401), and malformed requests. Provides error-specific resolution steps and retry strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa API errors) and some actions (diagnose, fix by HTTP code and error tag), but doesn't list multiple specific concrete actions like listing specific error types handled or specific resolution steps. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix Exa API errors by HTTP code and error tag) and 'when' (encountering Exa errors, debugging failed requests, troubleshooting integration issues) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'exa error', 'fix exa', 'exa not working', 'debug exa', 'exa 429', 'exa 401' — these are phrases users would naturally say when encountering Exa API issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific API (Exa) with specific error handling scenarios. Very unlikely to conflict with other skills unless there's another Exa-specific skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality error reference skill that efficiently organizes Exa API errors into scannable tables with concrete solutions and executable diagnostic code. Its main weakness is the lack of a verification/feedback loop in the troubleshooting workflow — after applying a fix, there's no explicit step to confirm resolution. Overall, it's well-suited as a quick-reference troubleshooting guide.
Suggestions
Add a verification step to the Instructions workflow, e.g., '5. Re-run the failing request to confirm the fix resolved the issue' to close the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured using tables for quick lookup. It avoids explaining what APIs are or how HTTP status codes work, respecting Claude's existing knowledge. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides executable bash diagnostic scripts, a complete TypeScript exponential backoff implementation, and concrete curl commands for testing. Solutions in tables are specific and actionable (e.g., 'Set livecrawlTimeout: 15000' rather than 'adjust timeout settings'). | 3 / 3 |
Workflow Clarity | The Instructions section provides a clear 4-step diagnostic sequence, but lacks explicit validation checkpoints or feedback loops. For a troubleshooting skill, there's no 'verify the fix worked' step after applying solutions, which is important for debugging workflows. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections by HTTP status code, a quick diagnostic script, and well-signaled references to external resources (docs, status page) and related skills (exa-debug-bundle, exa-rate-limits). Navigation is straightforward and one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.