Agent skill · research science · jeremylongshore
exa-core-workflow-a
Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost. Use when operating or reviewing this Exa boundary. Trigger with "Exa core workflow a", "review Exa core workflow a", or "fix Exa core workflow a".
Why this skill is useful
Adds executable scripts for advanced neural search capabilities with Exa, including content extraction and filtering that aren't in public docs.
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 and Contents Retrieval Workflow Overview Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost. 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 can return ranked results and nested contents. POST /contents retrieves known URLs or document IDs and always requires inspection of per-URL statuses. Highlights are token-efficient; text supports deeper analysis; summary is generated. Omitting maxAgeHours uses cache with livecrawl fallback, zero forces livecrawl, and minus one is cache-only. 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 the query, allowed domains, moderation need, and freshness requirement. 2. Choose type auto unless a measured latency or deep-synthesis need justifies another type. 3. Search with a bounded result count and minimal content mode. 4. Promote only approved URLs or IDs into a Contents request when more context is needed. 5. Inspect every Contents status and quarantine partial crawl failures. 6. Record request IDs, counts, freshness policy, and cost without copied content. 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-core-workflow-a--def880