Agent skill · software engineering · jeremylongshore
exa-sdk-patterns
Isolate exa-js or exa-py behind an application-owned adapter that preserves current request semantics and safe evidence. Use when operating or reviewing this Exa boundary. Trigger with "Exa sdk patterns", "review Exa sdk patterns", or "fix Exa sdk patterns".
Why this skill is useful
Adds production-ready TypeScript SDK patterns for Exa, including client singletons and error handling wrappers that enhance integration capabilities.
What it needs
Requires exa-js 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 SDK Adapter Patterns Overview Isolate exa-js or exa-py behind an application-owned adapter that preserves current request semantics and safe 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 The JavaScript and Python SDKs expose Search, Contents, Answer, Agent, and Monitor surfaces with language-specific naming. The adapter should normalize application inputs and errors without inventing defaults, and it should preserve requestId, statuses, grounding, and costDollars needed for operations. 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. Pin the selected SDK and inspect its current first-party specification. 2. Define the smallest application-owned interface for the required product surface. 3. Map names and optional fields explicitly at the adapter boundary. 4. Return content-free operational metadata separately from retrieved content. 5. Normalize documented errors without erasing status, tag, or request ID. 6. Add fixture-backed contract tests before changing the pinned SDK. 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-sdk-patterns