Agent skill · software engineering · jeremylongshore
exa-reliability-patterns
Design bounded Exa retries, deadlines, partial-result behavior, and tested fallbacks by endpoint and failure class. Use when operating or reviewing this Exa boundary. Trigger with "Exa reliability patterns", "review Exa reliability patterns", or "fix Exa reliability patterns".
Why this skill is useful
Adds executable scripts for implementing Exa-specific reliability patterns that enhance fault tolerance and resilience in integrations.
What it needs
Requires exa-js installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Reliability and Retry Design Overview Design bounded Exa retries, deadlines, partial-result behavior, and tested fallbacks by endpoint and failure class. 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 Retryability depends on status and operation. Invalid 400, auth, policy, and billing failures require repair; 429 honors Retry-After; documented transient server or overload failures can use capped jitter. Asynchronous creates and destructive calls require identity and state checks before replay. 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. Classify each operation as read, create, update, trigger, cancel, stop, or delete. 2. Assign an end-to-end deadline and bounded attempt budget per operation. 3. Retry only documented transient classes and preserve request or resource IDs. 4. Define partial Contents behavior and freshness fallback explicitly. 5. Choose a tested degrade path that preserves source attribution and policy. 6. Exercise timeout, duplicate delivery, stale cache, overload, and recovery in tests. 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-reliability-patterns