cohere-multi-env-setup
Configure Cohere across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment API keys, model selection, and rate limit strategies. Trigger with phrases like "cohere environments", "cohere staging", "cohere dev prod", "cohere environment setup", "cohere config by env".
Best use case
cohere-multi-env-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure Cohere across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment API keys, model selection, and rate limit strategies. Trigger with phrases like "cohere environments", "cohere staging", "cohere dev prod", "cohere environment setup", "cohere config by env".
Teams using cohere-multi-env-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cohere-multi-env-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cohere-multi-env-setup Compares
| Feature / Agent | cohere-multi-env-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure Cohere across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment API keys, model selection, and rate limit strategies. Trigger with phrases like "cohere environments", "cohere staging", "cohere dev prod", "cohere environment setup", "cohere config by env".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cohere Multi-Environment Setup
## Overview
Configure Cohere API v2 across dev/staging/prod with environment-specific API keys, model selection, and budget controls.
## Prerequisites
- Separate Cohere API keys per environment (trial for dev, production for staging/prod)
- Secret management solution (Vault, AWS Secrets Manager, GCP Secret Manager)
- Environment detection in application
## Environment Strategy
| Environment | API Key Type | Model | maxTokens | Caching |
|-------------|-------------|-------|-----------|---------|
| Development | Trial (free) | `command-r7b-12-2024` | 200 | Disabled |
| Staging | Production | `command-r-08-2024` | 1000 | Enabled |
| Production | Production | `command-a-03-2025` | 4096 | Enabled |
## Instructions
### Step 1: Configuration Structure
```typescript
// src/config/cohere.ts
type Environment = 'development' | 'staging' | 'production';
interface CohereEnvConfig {
chatModel: string;
embedModel: string;
rerankModel: string;
maxTokens: number;
cacheEnabled: boolean;
cacheTtlMs: number;
retries: number;
timeoutSeconds: number;
}
const configs: Record<Environment, CohereEnvConfig> = {
development: {
chatModel: 'command-r7b-12-2024', // Fastest, cheapest
embedModel: 'embed-v4.0',
rerankModel: 'rerank-v3.5',
maxTokens: 200, // Limit for dev
cacheEnabled: false, // See real responses
cacheTtlMs: 0,
retries: 1, // Fail fast in dev
timeoutSeconds: 30,
},
staging: {
chatModel: 'command-r-08-2024', // Mid-tier for testing
embedModel: 'embed-v4.0',
rerankModel: 'rerank-v3.5',
maxTokens: 1000,
cacheEnabled: true,
cacheTtlMs: 5 * 60 * 1000, // 5 minutes
retries: 3,
timeoutSeconds: 60,
},
production: {
chatModel: 'command-a-03-2025', // Best quality
embedModel: 'embed-v4.0',
rerankModel: 'rerank-v3.5',
maxTokens: 4096,
cacheEnabled: true,
cacheTtlMs: 15 * 60 * 1000, // 15 minutes
retries: 5,
timeoutSeconds: 120,
},
};
function detectEnvironment(): Environment {
const env = process.env.NODE_ENV ?? 'development';
if (['development', 'staging', 'production'].includes(env)) {
return env as Environment;
}
return 'development';
}
export function getCohereConfig(): CohereEnvConfig & { environment: Environment } {
const env = detectEnvironment();
return { ...configs[env], environment: env };
}
```
### Step 2: Environment-Aware Client
```typescript
// src/cohere/client.ts
import { CohereClientV2 } from 'cohere-ai';
import { getCohereConfig } from '../config/cohere';
let instance: CohereClientV2 | null = null;
export function getCohere(): CohereClientV2 {
if (!instance) {
const config = getCohereConfig();
if (!process.env.CO_API_KEY) {
throw new Error(`CO_API_KEY not set for ${config.environment} environment`);
}
instance = new CohereClientV2({
token: process.env.CO_API_KEY,
timeoutInSeconds: config.timeoutSeconds,
});
console.log(`[cohere] Initialized for ${config.environment} (model: ${config.chatModel})`);
}
return instance;
}
```
### Step 3: Secret Management
```bash
# --- Local Development ---
# .env.local (git-ignored)
CO_API_KEY=trial-key-for-dev
# --- GitHub Actions (CI) ---
gh secret set CO_API_KEY --body "production-key-for-ci"
# --- AWS Secrets Manager ---
aws secretsmanager create-secret \
--name cohere/staging/api-key \
--secret-string "staging-production-key"
aws secretsmanager create-secret \
--name cohere/production/api-key \
--secret-string "prod-production-key"
# --- GCP Secret Manager ---
echo -n "staging-key" | gcloud secrets create cohere-api-key-staging --data-file=-
echo -n "prod-key" | gcloud secrets create cohere-api-key-prod --data-file=-
# --- HashiCorp Vault ---
vault kv put secret/cohere/staging api_key="staging-key"
vault kv put secret/cohere/production api_key="prod-key"
```
### Step 4: Environment Guards
```typescript
// Prevent expensive operations in development
function guardExpensiveOperation(operation: string): void {
const config = getCohereConfig();
if (config.environment === 'development') {
// In dev, warn but don't block
console.warn(`[cohere] ${operation} using trial key — limited to 20 calls/min`);
}
}
// Prevent development keys in production
function validateKeyForEnv(): void {
const config = getCohereConfig();
const key = process.env.CO_API_KEY ?? '';
if (config.environment === 'production' && key.length < 30) {
throw new Error('Production requires a production API key (not trial)');
}
}
```
### Step 5: Per-Environment API Calls
```typescript
import { getCohereConfig } from '../config/cohere';
export async function chat(message: string): Promise<string> {
const config = getCohereConfig();
const cohere = getCohere();
const response = await cohere.chat({
model: config.chatModel, // Environment-specific model
messages: [{ role: 'user', content: message }],
maxTokens: config.maxTokens, // Environment-specific limit
});
return response.message?.content?.[0]?.text ?? '';
}
export async function embed(texts: string[]): Promise<number[][]> {
const config = getCohereConfig();
const cohere = getCohere();
const response = await cohere.embed({
model: config.embedModel,
texts,
inputType: 'search_document',
embeddingTypes: config.environment === 'development' ? ['float'] : ['int8'], // Cheaper in prod
});
return response.embeddings.float ?? response.embeddings.int8;
}
```
### Step 6: Docker Compose for Local Multi-Env Testing
```yaml
# docker-compose.yml
services:
app-dev:
build: .
environment:
- NODE_ENV=development
- CO_API_KEY=${CO_API_KEY_DEV}
ports:
- "3000:3000"
app-staging:
build: .
environment:
- NODE_ENV=staging
- CO_API_KEY=${CO_API_KEY_STAGING}
ports:
- "3001:3000"
```
## Output
- Per-environment Cohere configuration (model, tokens, timeout)
- Secret management across dev/staging/prod
- Environment guards preventing misuse
- Docker compose for local multi-env testing
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Trial key in production | Wrong secret | Validate key length at startup |
| Rate limited in dev | Trial key limits | Use 20 calls/min budget |
| Model not found | Typo in config | Validate model IDs at startup |
| Config merge fails | Missing environment | Default to development |
## Resources
- [Cohere API Keys](https://dashboard.cohere.com/api-keys)
- [Cohere Rate Limits](https://docs.cohere.com/docs/rate-limits)
- [12-Factor App Config](https://12factor.net/config)
## Next Steps
For observability setup, see `cohere-observability`.Related Skills
websocket-handler-setup
Websocket Handler Setup - Auto-activating skill for Backend Development. Triggers on: websocket handler setup, websocket handler setup Part of the Backend Development skill category.
vpc-network-setup
Vpc Network Setup - Auto-activating skill for GCP Skills. Triggers on: vpc network setup, vpc network setup Part of the GCP Skills skill category.
tensorflow-serving-setup
Tensorflow Serving Setup - Auto-activating skill for ML Deployment. Triggers on: tensorflow serving setup, tensorflow serving setup Part of the ML Deployment skill category.
sqs-queue-setup
Sqs Queue Setup - Auto-activating skill for AWS Skills. Triggers on: sqs queue setup, sqs queue setup Part of the AWS Skills skill category.
spy-setup-helper
Spy Setup Helper - Auto-activating skill for Test Automation. Triggers on: spy setup helper, spy setup helper Part of the Test Automation skill category.
spike-test-setup
Spike Test Setup - Auto-activating skill for Performance Testing. Triggers on: spike test setup, spike test setup Part of the Performance Testing skill category.
sla-monitor-setup
Sla Monitor Setup - Auto-activating skill for Enterprise Workflows. Triggers on: sla monitor setup, sla monitor setup Part of the Enterprise Workflows skill category.
server-sent-events-setup
Server Sent Events Setup - Auto-activating skill for API Integration. Triggers on: server sent events setup, server sent events setup Part of the API Integration skill category.
react-context-setup
React Context Setup - Auto-activating skill for Frontend Development. Triggers on: react context setup, react context setup Part of the Frontend Development skill category.
rds-instance-setup
Rds Instance Setup - Auto-activating skill for AWS Skills. Triggers on: rds instance setup, rds instance setup Part of the AWS Skills skill category.
rabbitmq-queue-setup
Rabbitmq Queue Setup - Auto-activating skill for Backend Development. Triggers on: rabbitmq queue setup, rabbitmq queue setup Part of the Backend Development skill category.
pre-commit-hook-setup
Pre Commit Hook Setup - Auto-activating skill for DevOps Basics. Triggers on: pre commit hook setup, pre commit hook setup Part of the DevOps Basics skill category.