Agent skill · software engineering · jeremylongshore
cohere-multi-env-setup
Configure Cohere development, staging, and production with separate keys, model resolution, budgets, and promotion evidence. Use when operating Cohere across environments. Trigger with "Cohere environments", "Cohere staging", or "Cohere dev prod setup".
Why this skill is useful
Provides specific configuration patterns and environment management strategies for the Cohere API that the AI wouldn't reliably generate on its own.
What it needs
Requires aws, gcloud, vault installed locally. Requires cohere account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere Multi-Environment Configuration Overview Keep credentials and capacity isolated while promoting one versioned provider contract through increasingly production-like environments. Prerequisites The target repository, runtime, environment, and accountable owner An approved Cohere team and key for any live verification Current quality, security, privacy, capacity, and change-control requirements Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content. Current Contract Use separate keys or provider deployments per environment and never fall back from production to an evaluation key. Resolve model availability per environment because Cohere platform and cloud-provider IDs differ. Promote configuration references, not secret values. Keep evaluation fixtures synthetic or approved and align staging limits closely enough to expose production failure modes. Authentication Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place COAPIKEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions. Instructions 1. Inventory environments, accounts, teams, cloud platforms, keys, owners, and data classes. 2. Define a validated configuration schema for provider, base URL, model IDs, timeouts, retries, and budgets. 3. Store secrets in environment-specific managers and bind access to runtime identities. 4. Run the same offline contracts everywhere and a bounded provider probe only in trusted environments. 5. Promote resolved configuration through review with quality, capacity, and rollback evidence. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-multi-env-setup