Agent skill · writing content · jeremylongshore
exa-core-workflow-b
Run asynchronous Exa Agent research with a bounded schema, effort, terminal-state policy, citations, and cleanup decision. Use when operating or reviewing this Exa boundary. Trigger with "Exa core workflow b", "review Exa core workflow b", or "fix Exa core workflow b".
Why this skill is useful
Adds executable scripts for Exa API workflows that enable similarity search, content retrieval, and AI-generated answers with citations.
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 Agent Run Lifecycle Overview Run asynchronous Exa Agent research with a bounded schema, effort, terminal-state policy, citations, and cleanup decision. 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 Agent runs are asynchronous unless streamed. A created run returns an ID that must be polled, streamed, stopped, cancelled, or deleted through the Agent lifecycle. Fixed effort provides a predictable price; auto and beta max are usage-metered. Structured output and grounding require separate validation. 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. Translate the approved research question into a narrow query and optional system prompt. 2. Choose fixed effort or an explicit metered cap and define the output schema. 3. Create one run and persist its content-free run ID. 4. Poll or consume server-sent events with a deadline and terminal-state handling. 5. Validate structured fields, grounding, citations, and cost independently. 6. Stop, cancel, retain, or delete the run according to the approved evidence policy. 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-core-workflow-b