Agent skill · software engineering · jeremylongshore
exa-debug-bundle
Produce a minimal Exa diagnostic bundle that preserves reproducibility without exposing credentials, queries, retrieved content, or customer data. Use when operating or reviewing this Exa boundary. Trigger with "Exa debug bundle", "review Exa debug bundle", or "fix Exa debug bundle".
Why this skill is useful
Adds executable scripts for collecting Exa diagnostic information and troubleshooting that aren't in public documentation.
What it needs
Requires node, npm 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 Privacy-safe Debug Bundle Overview Produce a minimal Exa diagnostic bundle that preserves reproducibility without exposing credentials, queries, retrieved content, or customer data. 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 Useful Exa evidence includes endpoint family, SDK version, request ID, status, error tag, timing, result and status counts, cost, freshness mode, and retry history. Sensitive values and web content are unnecessary for most first-line diagnosis. 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. Set the incident window, environment, data classification, and evidence owner. 2. Collect configuration names and hashes rather than secret values. 3. Record request IDs, statuses, tags, timing, counts, and retry decisions. 4. Replace queries, URLs, prompts, schemas, and content with approved fingerprints or categories. 5. Scan the candidate bundle for keys, bearer headers, presigned URLs, and customer text. 6. Encrypt, time-bound, and delete the bundle according to the incident policy. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-debug-bundle--d5ed87