Agent skill · research science · jeremylongshore
exa-advanced-troubleshooting
Localize complex Exa failures across query planning, retrieval, crawling, synthesis, SDK mapping, queues, and downstream consumption. Use when operating or reviewing this Exa boundary. Trigger with "Exa advanced troubleshooting", "review Exa advanced troubleshooting", or "fix Exa advanced troubleshooting".
Why this skill is useful
Provides advanced debugging techniques and specific API interaction patterns for diagnosing Exa issues that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. 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 Cross-layer Troubleshooting Overview Localize complex Exa failures across query planning, retrieval, crawling, synthesis, SDK mapping, queues, and downstream consumption. 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 Search relevance, Contents crawl status, deep output grounding, Agent terminal state, webhook delivery, and application rendering are independent layers. A single request can succeed at one layer and fail at another, so evidence must preserve layer-specific IDs and decisions. 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. Reproduce with a sanitized input and freeze endpoint, SDK, flags, and time window. 2. Trace the application request through adapter, Exa request ID, results, statuses, and downstream IDs. 3. Separate relevance, freshness, crawl, synthesis, schema, queue, and rendering symptoms. 4. Compare one controlled parameter at a time against a known-good fixture or request. 5. Escalate vendor defects with request IDs, tags, timestamps, and redacted shape evidence. 6. Verify the fix at the failed layer and then end to end before closing. 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-advanced-troubleshooting