Agent skill · data analytics · jeremylongshore
exa-performance-tuning
Tune Exa search type, content mode, freshness, result count, and concurrency against measured latency and retrieval quality. Use when operating or reviewing this Exa boundary. Trigger with "Exa performance tuning", "review Exa performance tuning", or "fix Exa performance tuning".
Why this skill is useful
Adds multiple executable scripts for optimizing Exa API performance, including caching and parallelization techniques that aren't commonly known.
What it needs
Requires lru-cache 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 Latency and Retrieval Performance Tuning Overview Tune Exa search type, content mode, freshness, result count, and concurrency against measured latency and retrieval quality. 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 Search types trade latency and synthesis depth; content extraction, outputSchema, forced livecrawl, summaries, and subpages add work. Highlights are usually more token-efficient than full text. Published latency values are guidance, not a service-specific SLO. 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. Build a consented benchmark set with explicit relevance and freshness judgments. 2. Measure the current adapter end to end, including queue and downstream processing. 3. Vary one dimension at a time: type, result count, content mode, freshness, or subpages. 4. Track p50, p95, errors, content size, relevance, freshness, and cost together. 5. Choose separate profiles for interactive, background, and deep-research paths. 6. Canary the winning profile and retain rollback thresholds. 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-performance-tuning