Agent skill · software engineering · jeremylongshore
exa-prod-checklist
Gate an Exa-backed service on contract, security, cost, reliability, observability, and rollback evidence. Use when operating or reviewing this Exa boundary. Trigger with "Exa prod checklist", "review Exa prod checklist", or "fix Exa prod checklist".
Why this skill is useful
Adds executable scripts for pre-flight checks, deployment procedures, and rollback that enhance deployment capabilities for Exa integrations.
What it needs
Requires curl, kubectl, npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Production Readiness Gate Overview Gate an Exa-backed service on contract, security, cost, reliability, observability, and rollback evidence. 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 Production readiness spans the chosen Exa product, not just connectivity. Search and Contents require content and freshness controls; Agent, Monitors, Websets, and Batch add asynchronous state; webhooks add signature and replay handling; every paid surface needs a budget owner. 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. Freeze the release SHA, adapter version, endpoint inventory, and rollback owner. 2. Verify auth, secret rotation, data classification, domain policy, and moderation. 3. Exercise documented success, partial, throttle, billing, policy, and overload paths. 4. Confirm endpoint budgets, cost alerts, queue bounds, timeouts, and retry ceilings. 5. Verify request IDs, safe metrics, signed-webhook evidence, and deletion procedures. 6. Canary under explicit limits and promote only after the rollback window passes. 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-prod-checklist--eef19a