Agent skill · software engineering · jeremylongshore
anth-multi-env-setup
Configure Claude API across dev, staging, and production environments
Why this skill is useful
Adds executable scripts for configuring Claude API across multiple environments with isolated keys and spend controls that are not in public documentation.
What it needs
Requires anthropic installed locally. Requires anthropic account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Multi-Environment Setup Overview Configure isolated Claude API environments with per-env API keys, model selection, and spend controls using Anthropic Workspaces. Environment Configuration Anthropic Workspaces (Key Isolation) Create separate Workspaces in console.anthropic.com: Workspace Purpose Rate Limit Tier ----------- --------- ----------------- dev Development & testing Tier 1 staging Pre-production validation Tier 2 production Live traffic Tier 3+ Each workspace has independent API keys, usage tracking, and rate limits. Environment Files Client Factory Per-Environment Model Override Error Handling Issue Cause Fix ------- ------- ----- Dev key used in prod Wrong env loaded Validate key prefix matches environment Staging rate limited Low tier workspace Upgrade staging workspace tier Cost overrun in dev No budget guard Add per-env spend limits Prerequisites Define the environment inventory, workspace/key ownership, model policy, rate and spend budgets, data classification, and promotion approver. Provision separate least-privileged credentials through a secret manager; production secrets must not exist in repository files, shell history, examples, or CI logs. Prepare synthetic fixtures, environment isolation tests, a canary route, and a rollback configuration before changing any workspace or client factory. Instructions 1. Map each environment to exactly one approved Anthropic workspace and secret-manager reference. Validate environment identity at startup and fail closed on a missing or mismatched key. 2. Load configuration through the environment-specific client factory, pin model and API settings, and enforce per-environment token, rate, timeout, retry, data, and destination limits. 3. Run authentication, cross-environment isolation, budget, and request-shape tests with synthetic fixtures. Capture only aggregate pass/fail and usage metadata. 4. Promote a reviewed artifact from staging to a small internal canary before production. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anth-multi-env-setup--b123a0