Agent skill · software engineering · jeremylongshore
exa-hello-world
Prove a new Exa Search integration with a bounded synthetic query and content-free assertions. Use when operating or reviewing this Exa boundary. Trigger with "Exa hello world", "review Exa hello world", or "fix Exa hello world".
Why this skill is useful
Provides specific TypeScript examples for using the Exa API that are not commonly found in public documentation.
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 Search Smoke Test Overview Prove a new Exa Search integration with a bounded synthetic query and content-free assertions. 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 POST /search requires a query and defaults to type auto. New code should not select legacy neural terminology. A successful smoke test checks requestId, bounded results, valid HTTP(S) URLs, and costDollars rather than snapshotting volatile rankings or page text. 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. Define a non-sensitive query with a stable topical expectation. 2. Set an explicit result cap and omit content extraction for the first probe. 3. Submit one authorized request through the application adapter. 4. Validate requestId, result count, URL schemes, and the cost field. 5. Repeat only once when the failure is explicitly retryable. 6. Delete transient output and retain only content-free evidence. 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-hello-world