Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost.

MITAuto-check passedDevelopment

Install Exa Core Workflow A

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-core-workflow-a -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace exa-core-workflow-a --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/exa-core-workflow-a .claude/skills/exa-core-workflow-a && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
exa-core-workflow-a
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
566 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost.

  • Works in 6 steps: Classify the query, allowed domains,… → Choose type auto unless a measured… → Search with a bounded result count and… → …
  • Reviewing this Exa boundary
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Needs EXA_API_KEY

What it does

Exa Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Exa work requires network access

It sits in Development, covering Domain-driven design. It works with Exa. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Reviewing this Exa boundary
  • With Exa core workflow a
  • Review Exa core workflow a
  • Fix Exa core workflow a

Example prompts

  • “Exa core workflow a”
  • “review Exa core workflow a”
  • “fix Exa core workflow a”
  • “/exa-core-workflow-a”

Requirements

  • A credential in EXA_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code; live Exa work requires network access
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • EXA_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live Exa work requires network access

    From compatibility in the SKILL.md frontmatter.

Context cost

Exa Core Workflow A loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 566 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 566 words, ~1,215 tokens.

Download SKILL.mdSave it as .claude/skills/exa-core-workflow-a/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
exa-core-workflow-a
description
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".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Exa work requires network access
argument-hint
<query> <content-mode> <freshness-policy>
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, exa
model
inherit
effort
high

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 EXA_API_KEY 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. Use Write and Edit only for approved implementation or documentation changes. Do not call Exa, run paid research, create or alter a Monitor, Webset, Agent run, Batch, team, member, API key, budget, webhook, or deployment merely because this skill was invoked.

Show full SKILL.md (249 more words)Show less

Approval Boundaries

Require an accountable owner before live queries involving sensitive intent, production credentials, spend or rate-limit changes, forced live crawling, generated summaries, external delivery, deployment, member or key changes, schedule creation, or destructive cancellation, stopping, deletion, or revocation. Read-only repository inspection and synthetic offline validation do not authorize live vendor actions.

Failure Modes

  • Legacy neural is not the recommended type for new code.
  • Forcing livecrawl increases latency and can still fail per URL.
  • A successful batch-level Contents response can contain failed URL statuses.

Output

Return the operation scope, environment, team and product surface, authorization class, contract and policy decisions, deterministic validation results, content-free identifiers, status and cost counts, risks, cleanup or rollback state, and a concise pass or fail receipt. Exclude credentials, raw queries, prompts, presigned URLs, retrieved content, generated output, and customer-derived data unless separately approved.

Example

  • Use auto Search with highlights for five results, then request capped text only for the two approved source URLs.
  • Finish with request or resource IDs, assertion counts, cost and terminal state, rollback or deletion status, and the decision owner; never reproduce secrets or retrieved content.

Validation

Rerun the smallest relevant deterministic test, compare actual behavior with the requested outcome and current first-party contract, verify sensitive fields are absent from evidence, and confirm deadlines, terminal state, downstream retention, and rollback before reporting success.

References

Review the dated first-party evidence map before relying on any endpoint, parameter, search type, price, limit, beta, compliance, identity, retry, or lifecycle claim.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/exa-core-workflow-a of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Exa Core Workflow A next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Exa Core Workflow A compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Exa Core Workflow A this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Domain Modelingfossasia/eventyay-interpretation1.6k30 repos~821Automated safety check: PassApache-2.0
Domain Modelingbrim-borium/spotify_sdk1667 repos~806Automated safety check: PassApache-2.0
Evolutionary Modular Architecturetech-leads-club/agent-skills7k—~3.7kAutomated safety check: PassCC-BY-4.0
Domain Modeling and Glossarywindmill-labs/windmill18k—~622Automated safety check: PassCustom licence
Dddswamp-club/swamp646—~1.4kAutomated safety check: PassCustom licence

Similar skills

  • Domain Modeling

    fossasia/eventyay-interpretation

    Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 30 repos~821 tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 7 repos~806 tokens
    DevelopmentAuto-check passed
  • Evolutionary Modular Architecture

    tech-leads-club/agent-skills

    Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.

    7k GitHub stars~3.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Domain Modeling and Glossary

    windmill-labs/windmill

    Actively challenges vague or conflicting terminology as you design, and keeps a living domain glossary file up to date in real time.

    18k GitHub stars~622 tokensUpdated today
    DevelopmentAuto-check passed
  • Ddd

    swamp-club/swamp

    Domain Driven Design guidance for TypeScript/Deno codebases.

    646 GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Migration Path

    AxonIQ/AxonFramework

    Create a new Axon Framework 4→5 migration path documentation page.

    3.6k GitHub stars~594 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Exa Core Workflow A

What does Exa Core Workflow A do?

Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost. Exa Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Operate Search and Contents as an explicit two-stage retrieval workflow with bounded context, freshness, and cost.

When should I use Exa Core Workflow A?

Exa Core Workflow A fits situations like: reviewing this Exa boundary; with Exa core workflow a; review Exa core workflow a; fix Exa core workflow a.

How do I install Exa Core Workflow A in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-core-workflow-a -a claude-code`. Or copy the skill folder (skills/.curated/exa-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/exa-core-workflow-a in your project. Claude Code loads it when a task matches its description.

How do I install Exa Core Workflow A in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-core-workflow-a -a codex`. Or copy the skill folder (skills/.curated/exa-core-workflow-a in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/exa-core-workflow-a in your project. Codex loads it when a task matches its description.

Can I use Exa Core Workflow A in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-core-workflow-a -a cursor` (or -a -a, -a or -a for the others). To copy it by hand, put the folder in .cursor/skills/exa-core-workflow-a, .gemini/skills/exa-core-workflow-a, .github/skills/exa-core-workflow-a and .opencode/skills/exa-core-workflow-a in your project.

What does Exa Core Workflow A need to run?

Going by SKILL.md and its folder, Exa Core Workflow A needs credentials named EXA_API_KEY. Our summary lists: A credential in EXA_API_KEY. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Exa work requires network access.

Does Exa Core Workflow A access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Exa Core Workflow A safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Exa Core Workflow A use?

Exa Core Workflow A is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Exa Core Workflow A use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 459 tokens, read only when the agent opens those files.

What are the alternatives to Exa Core Workflow A?

Skills that share tags, products or a category with Exa Core Workflow A: Domain Modeling (fossasia/eventyay-interpretation, 1.6k stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars) and Domain Modeling and Glossary (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Exa Core Workflow A?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.