Agent skill · marketing growth · jeremylongshore
exa-incident-runbook
Contain Exa credential, data, cost, capacity, or correctness incidents while preserving safe evidence and vendor request IDs. Use when operating or reviewing this Exa boundary. Trigger with "Exa incident runbook", "review Exa incident runbook", or "fix Exa incident runbook".
Why this skill is useful
Adds executable scripts and decision trees for incident response specific to Exa API issues that aren't publicly documented.
What it needs
Requires bash, curl 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 Incident Containment Runbook Overview Contain Exa credential, data, cost, capacity, or correctness incidents while preserving safe evidence and vendor request IDs. 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 Containment choices differ by incident: revoke or rotate a key, disable a caller, pause or delete Monitors, stop or cancel Agent runs, cancel Batches, quarantine webhook processing, or switch to a tested fallback. Deletion and cancellation are destructive and require exact targets. 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. Declare severity, affected product, environment, owner, and evidence boundary. 2. Stop new work at the narrowest reversible application or queue control. 3. Snapshot content-free IDs, states, costs, error tags, timestamps, and request IDs. 4. Rotate credentials or pause vendor resources only with exact authorization. 5. Reconcile in-flight runs, batches, monitors, webhooks, and downstream outputs. 6. Verify recovery, document residual risk, and time-bound evidence retention. 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-incident-runbook