Agent skill · software engineering · jeremylongshore
exa-multi-env-setup
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".
Why this skill is useful
Adds executable scripts for multi-environment configuration and caching strategies that are not commonly found in public documentation.
What it needs
Requires exa-js, redis 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 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 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. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-multi-env-setup