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". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill cohere-multi-env-setup --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.
# 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 ## Environm
What does the cohere-multi-env-setup 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". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill cohere-multi-env-setup --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 jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 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.