Agent skill · software engineering · jeremylongshore
exa-data-handling
Govern queries, public-web retrieval, generated summaries, citations, and downstream copies across their full retention lifecycle. Use when operating or reviewing this Exa boundary. Trigger with "Exa data handling", "review Exa data handling", or "fix Exa data handling".
Why this skill is useful
Adds executable scripts for managing Exa search results, caching, and RAG context management that are not available in public documentation.
What it needs
Requires exa-js, ioredis, 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 Retrieved-content Governance Overview Govern queries, public-web retrieval, generated summaries, citations, and downstream copies across their full retention lifecycle. 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 and Contents can return page text, highlights, summaries, links, images, and subpages; Agent and Answer can generate cited output. Public availability does not remove privacy, copyright, contractual, prompt-injection, or retention obligations. Enterprise Zero Data Retention and request-scoped HIPAA behavior require explicit enablement. 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 query intent, target domains, returned content, generated output, and citations. 2. Request the smallest content mode and character budget that supports the task. 3. Apply domain, moderation, malware, prompt-injection, and personal-data controls. 4. Keep source attribution and generated claims distinguishable downstream. 5. Define cache, vector-store, log, backup, and deletion propagation before persistence. 6. Verify downstream deletion and preserve only content-free operational receipts. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-data-handling