Agent skill · data analytics · jeremylongshore
exa-common-errors
Classify Exa failures by HTTP status, error tag, endpoint, and per-item crawl status before deciding whether to repair, retry, or escalate. Use when operating or reviewing this Exa boundary. Trigger with "Exa common errors", "review Exa common errors", or "fix Exa common errors".
Why this skill is useful
Provides specific troubleshooting steps and code snippets for handling Exa API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires exa account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Error and Status Decision Tree Overview Classify Exa failures by HTTP status, error tag, endpoint, and per-item crawl status before deciding whether to repair, retry, or escalate. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Documented errors distinguish invalid requests, authentication, exhausted credits or budgets, access policy, per-URL crawl failure, rate limiting, service overload, and Answer generation failure. Most errors include requestId, error, and tag; 429 can use a simpler body. Contents also reports granular statuses inside a successful response. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Capture endpoint, status, tag, request ID, attempt, and content-free input shape. 2. Separate request defects from auth, billing, policy, crawl, and capacity classes. 3. Repair 400-class contract errors instead of retrying them unchanged. 4. Honor Retry-After for 429 and use bounded jitter for documented transient failures. 5. Inspect Contents statuses even when the outer request succeeded. 6. Escalate persistent vendor failures with request IDs and redacted timing evidence. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-common-errors--48f37c