Agent skill · software engineering · jeremylongshore
cohere-deploy-integration
Deploy a Cohere-powered service with server-side secrets, streaming-safe infrastructure, health checks, canarying, and rollback. Use when shipping Cohere workloads. Trigger with "deploy Cohere", "Cohere production deploy", or "Cohere streaming service".
Why this skill is useful
Adds deployment scripts and configurations for Cohere API applications on multiple platforms, which the AI wouldn't generate on its own.
What it needs
Requires fly, gcloud, vercel 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 Deployment Integration Overview Release the application around Cohere without embedding the key in clients, turning health checks into billable generation, or hiding provider failure. 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 Call Cohere from a trusted server runtime; never expose the provider key to browsers or mobile clients. Use a local process health check and a separate protected provider-readiness probe. Streaming paths require proxy buffering, idle timeout, cancellation, and client-disconnect tests. Model selection and fallback must be explicit deployment configuration reviewed against current availability. 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. Inspect the target platform's secret, egress, timeout, streaming, autoscaling, and rollback behavior. 2. Inject COAPIKEY from the platform secret manager and restrict access to the service identity. 3. Set explicit model IDs, request bounds, client timeouts, concurrency, and circuit-breaker thresholds. 4. Deploy to a non-production environment and test cancellation, throttling, timeout, and provider outage behavior. 5. Canary production traffic while watching quality, error, latency, queue, and spend signals. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-deploy-integration