exa-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-common-errorsDiagnose and fix Exa common errors and exceptions. 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
57%This skill has good structure and appropriate references to related skills, but suffers from boilerplate padding and incomplete content. The title promises '10 most common errors' but only documents 3, and the generic Instructions section adds no value. The actual error solutions are useful but lack verification steps.
Suggestions
Remove the generic 'Instructions' section (Steps 1-3) and 'Output' section - they add no actionable value
Either document all 10 promised errors or change the title to match actual content
Add verification commands after each solution (e.g., 'Verify fix: curl -H "Authorization: Bearer $EXA_API_KEY" https://api.exa.com/test')
Replace the rate limit 'see other skill' with at least a minimal inline code example
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary scaffolding (Overview, Prerequisites, Instructions steps 1-3, Output section) that adds little value. The actual error solutions are reasonably concise, but the framing could be tightened significantly. | 2 / 3 |
Actionability | Provides some executable commands (curl, echo, TypeScript config), but several solutions are incomplete - rate limiting just references another skill, and only 3 of the promised '10 most common errors' are actually documented. | 2 / 3 |
Workflow Clarity | The escalation path is clear, but the main 'Instructions' workflow (identify -> find -> apply) is generic filler. The individual error solutions lack verification steps to confirm the fix worked. | 2 / 3 |
Progressive Disclosure | Appropriately references external skills (exa-rate-limits, exa-debug-bundle) and external resources without deep nesting. Content is well-organized with clear sections for each error type. | 3 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with explicit trigger guidance and clear 'when to use' clauses. The main weakness is the lack of specific concrete actions - it describes general troubleshooting activities rather than listing specific error types or fix procedures that would help Claude understand the full scope of capabilities.
Suggestions
Add 2-3 specific error types or scenarios this skill handles (e.g., 'authentication failures', 'rate limit errors', 'invalid query syntax') to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa errors) and general actions (diagnose, fix, debug, troubleshoot), but doesn't list specific concrete actions like 'resolve authentication failures', 'fix rate limiting issues', or 'handle malformed response errors'. | 2 / 3 |
Completeness | Clearly answers both what (diagnose and fix Exa errors/exceptions) and when (explicit 'Use when...' clause with triggers, plus 'Trigger with phrases like...' providing additional explicit guidance). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms users would say: 'exa error', 'fix exa', 'exa not working', 'debug exa', plus contextual phrases like 'failed requests' and 'integration issues'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Exa as a product/service with distinct trigger terms; unlikely to conflict with generic debugging skills or other API-specific troubleshooting skills. | 3 / 3 |
Total | 11 / 12 Passed |
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.