mistral-multi-env-setup
Configure Mistral AI across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Mistral AI configurations. Trigger with phrases like "mistral environments", "mistral staging", "mistral dev prod", "mistral environment setup", "mistral config by env".
npx skills add majiayu000/claude-skill-registry --skill mistral-multi-env-setup-jeremylongshore-claude-code-plugins --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Mistral AI Multi-Environment Setup ## Overview Configure Mistral AI across development, staging, and production environments. ## Prerequisites - Separate Mistral AI API keys per environment - Secret management solution (Vault, AWS Secrets Manager, GCP Secret Manager) - CI/CD pipeline with environment variables - Environment detection in application ## Environment Strategy | Environment | Purpose | API Keys | Model Selection | |-------------|---------|----------|-----------------| | Development | Local dev | Test keys | mistral-small-latest | | Staging | Pre-prod testing | Staging keys | Same as prod | | Production | Live traffic | Production keys | Optimized selection | ## Instructions ### Step 1: Configuration Structure ``` config/ ├── mistral/ │ ├── base.ts # Shared configuration │ ├── development.ts # Dev overrides │ ├── staging.ts # Staging overrides │ └── production.ts # Prod overrides ``` ### Step 2: Base Configuration ```typescript // config/mistral/base.ts export const baseConfig = { defaultModel: 'mistral-small-latest', timeout: 30000, maxRetries: 3, cache: { enabled: true, ttlSeconds: 300, }, rateLimits: { requestsPerMinute: 60, tokensPerMinute: 500000, }, }; ``` ### St
- Overview
- Prerequisites
- Environment Strategy
- Instructions
- Step 1: Configuration Structure
- Step 2: Base Configuration
- Step 3: Environment-Specific Configs
- Step 4: Environment Detection
- Step 5: Secret Management
- Step 6: Environment Isolation
- Step 7: Feature Flags by Environment
- Output
- Error Handling
- Examples
Store secrets aws secretsmanager create-secret \ Retrieve in code aws secretsmanager get-secret-value \ Store secret echo -n "your-api-key" | gcloud secrets create mistral-api-key-prod --data-file=- Grant access gcloud secrets add-iam-policy-binding mistral-api-key-prod \
What does the mistral-multi-env-setup skill do?
Configure Mistral AI across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Mistral AI configurations. Trigger with phrases like "mistral environments", "mistral staging", "mistral dev prod", "mistral environment setup", "mistral config by env".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill mistral-multi-env-setup-jeremylongshore-claude-code-plugins --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.