Agent skill · software engineering · jeremylongshore
clade-multi-env-setup
Configure Claude across dev, staging, and production with different
Why this skill is useful
Provides specific configuration patterns for managing Anthropic API keys and models across multiple environments that the AI wouldn't reliably generate on its own.
What it needs
Requires anthropic account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Multi-Environment Setup Overview Use different API keys, models, and limits across dev/staging/prod. Environment Configuration Separate API Keys Per Environment Use different Anthropic API keys for each environment: Dev key: Low tier, spending alerts at $10 Staging key: Medium tier, spending alerts at $50 Prod key: Highest tier, spending alerts at usage baseline + 50% Model Selection Strategy Environment Model Why ------------- ------- ----- Development Haiku Fast iteration, cheap Staging Sonnet Match prod quality Production Sonnet (default) Balanced cost/quality Production (complex) Opus Complex reasoning tasks Output Environment-specific Anthropic configuration (model, maxTokens, maxRetries) Separate API keys per environment with appropriate tier limits Spending alerts configured per environment Dev using Haiku (cheap), staging matching prod (Sonnet), prod using Sonnet/Opus Error Handling Error Cause Solution ------- ------- ---------- API Error Check error type and status code See clade-common-errors Examples See Environment Configuration TypeScript pattern, API key separation strategy, and Model Selection Strategy table above. Resources API Key Management Next Steps See clade-observability for monitoring across environments. Prerequisites Completed clade-install-auth Multiple environments (dev/staging/prod) configured Separate Anthropic API keys created per environment Instructions Step 1: Review the patterns below Each section contains production-ready code examples. Copy and adapt them to your use case. Step 2: Apply to your codebase Integrate the patterns that match your requirements. Test each change individually. Step 3: Verify Run your test suite to confirm the integration works correctly.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clade-multi-env-setup--be6df0