New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Exa Multi Env Setup

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability.

MITAuto-check passedDevOps & Cloud

Install Exa Multi Env Setup

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-multi-env-setup -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace exa-multi-env-setup --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-multi-env-setup .claude/skills/exa-multi-env-setup && 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-multi-env-setup
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
541 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability.

  • Works in 6 steps: Inventory teams, organizations, members,… → Assign each environment an explicit team… → Create narrowly named keys with budgets… → …
  • 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 Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability. Use when operating or reviewing this Exa boundary. Trigger with "Exa multi env setup", "review Exa multi env setup", or "fix Exa multi env setup".

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 DevOps & Cloud, covering Observability. 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 multi env setup
  • Review Exa multi env setup
  • Fix Exa multi env setup

Example prompts

  • “Exa multi env setup”
  • “review Exa multi env setup”
  • “fix Exa multi env setup”
  • “/exa-multi-env-setup”

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. Inventory teams, organizations, members, service keys, API keys, and owners.
  2. Assign each environment an explicit team or documented isolation boundary.
  3. Create narrowly named keys with budgets and rate limits where supported.
  4. Prevent production keys from preview, developer, and forked-CI contexts.
  5. Namespace Monitor, Webset, Agent, Batch, and evidence identifiers by environment.
  6. Test revocation, promotion, teardown, and cross-environment denial.

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 Multi Env Setup loads about 1.2k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
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.6k

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). 541 words, ~1,191 tokens.

Download SKILL.mdSave it as .claude/skills/exa-multi-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
exa-multi-env-setup
description
Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability. Use when operating or reviewing this Exa boundary. Trigger with "Exa multi env setup", "review Exa multi env setup", or "fix Exa multi env setup".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Exa work requires network access
argument-hint
<dev-team> <stage-team> <prod-team>
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, exa
model
inherit
effort
high

Exa Multi-environment Isolation

Overview

Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability. 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

Exa usage and paid access are organized through teams, and team members share plan features and limits. API keys can have names, rate limits, and budgets when Team Management is enabled. Environment isolation must be designed rather than inferred from a key name.

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. Inventory teams, organizations, members, service keys, API keys, and owners.
  2. Assign each environment an explicit team or documented isolation boundary.
  3. Create narrowly named keys with budgets and rate limits where supported.
  4. Prevent production keys from preview, developer, and forked-CI contexts.
  5. Namespace Monitor, Webset, Agent, Batch, and evidence identifiers by environment.
  6. Test revocation, promotion, teardown, and cross-environment denial.

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.

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.

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

Failure Modes

  • Multiple keys in one team can still share plan and capacity boundaries.
  • Copying production data into staging changes the data-governance scope.
  • Deleting a deployment does not remove vendor-side scheduled resources.

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

  • Development uses synthetic queries and a small key budget; production has separate ownership, limits, alerts, and scheduled-resource inventory.
  • 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-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Exa Multi Env Setup 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 Multi Env Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Exa Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Distributed Tracingwshobson/agents40k12 repos~527Automated safety check: PassMIT
Workers Best Practiceshodgef/apiker1276 repos~1.8kAutomated safety check: PassMIT
Backend DesignxenitV1/claude-code-maestro229—~2.1kAutomated safety check: NotesMIT
Add Metricmicrobus-io/fabric172—~1.5kAutomated safety check: PassApache-2.0
OmniRoute Health Monitoringdiegosouzapw/OmniRoute75k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 12 repos~527 tokens
    DevOps & CloudAuto-check passed

  • Workers Best Practices

    hodgef/apiker

    Reviews and authors Cloudflare Workers code against production best practices.

    127 GitHub starsUsed in 6 repos~1.8k tokens
    DevOps & CloudAuto-check passed

  • Backend Design

    xenitV1/claude-code-maestro

    Elite Tier Backend standards, including Vertical Slice Architecture, Zero Trust Security, and High-Performance API protocols.

    229 GitHub stars~2.1k tokensUpdated 8 mo ago
    DevOps & CloudAuto-check: notes

  • Add Metric

    microbus-io/fabric

    TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.

    172 GitHub stars~1.5k tokensUpdated 12 days ago
    DevOps & CloudAuto-check passed

  • OmniRoute Health Monitoring

    diegosouzapw/OmniRoute

    Checks the health of an OmniRoute gateway: provider circuit breakers, latency percentiles, budget guard alerts, connection cooldowns and model lockouts.

    75k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Output Dev Cost Hooks

    growthxai/output

    Subscribe to cost events (cost:http:request, llm:generation:metering) to forward LLM and API spend to your own observability system.

    442 GitHub stars~2.7k tokensUpdated today
    DevOps & CloudAuto-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

Categories

Questions about Exa Multi Env Setup

What does Exa Multi Env Setup do?

Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability. Exa Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability.

When should I use Exa Multi Env Setup?

Exa Multi Env Setup fits situations like: reviewing this Exa boundary; with Exa multi env setup; review Exa multi env setup; fix Exa multi env setup.

How do I install Exa Multi Env Setup in Claude Code?

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

How do I install Exa Multi Env Setup in Codex?

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

Can I use Exa Multi Env Setup 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-multi-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exa-multi-env-setup, .gemini/skills/exa-multi-env-setup, .github/skills/exa-multi-env-setup and .opencode/skills/exa-multi-env-setup in your project.

What does Exa Multi Env Setup need to run?

Going by SKILL.md and its folder, Exa Multi Env Setup 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 Multi Env Setup 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 Multi Env Setup 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 Multi Env Setup use?

Exa Multi Env Setup 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 Multi Env Setup use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Multi Env Setup?

Skills that share tags, products or a category with Exa Multi Env Setup: Distributed Tracing (wshobson/agents, 40k stars), Workers Best Practices (hodgef/apiker, 127 stars), Backend Design (xenitV1/claude-code-maestro, 229 stars) and Add Metric (microbus-io/fabric, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Exa Multi Env Setup?

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.