Agent skill · software engineering · jeremylongshore
cohere-rate-limits
Implement Cohere endpoint-aware throttling, bounded retry, and queue backpressure from current limits and observed responses. Use when handling 429s or planning throughput. Trigger with "Cohere rate limit", "Cohere throttling", or "Cohere 429".
Why this skill is useful
Provides specific implementation patterns for handling Cohere API rate limits, including backoff and queuing strategies that the AI wouldn't reliably generate on its own.
What it needs
Requires cohere-ai, p-queue 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 Rate-Limit Control Overview Treat limits as a live per-key, endpoint, and model contract rather than a single permanent requests-per-minute number. 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 The reviewed page lists Chat limits per model; several newer variants require contacting sales for production capacity. On the review date, Embed was expressed in inputs per minute, while Rerank was expressed in requests per minute. Trial usage includes a monthly cap, and production arrangements can vary. A successful load plan must measure actual account behavior and preserve headroom instead of copying a static table. 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. Identify key type, endpoint, resolved model, request batch size, and documented current limit. 2. Convert limits into request, input, and token budgets as applicable. 3. Apply a shared queue with bounded concurrency, jittered backoff, and a total retry deadline. 4. Honor provider retry guidance when present and stop retrying deterministic client errors. 5. Load test below the approved ceiling with non-sensitive fixtures and record saturation behavior. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-rate-limits