Agent skill · data analytics · jeremylongshore
cohere-common-errors
Diagnose Cohere v2 authentication, validation, model, quota, transport, and provider failures from redacted evidence. Use when a Cohere request fails. Trigger with "Cohere error", "Cohere 429", or "debug Cohere API".
Why this skill is useful
Provides specific error handling patterns and fixes for the Cohere API that the AI wouldn't reliably generate on its own.
What it needs
Requires cohere-ai 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 Error Diagnosis Overview Classify the failing layer before changing code, and return a minimal reproduction plus the safest next action. 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 400 and 422 usually indicate an invalid request contract or incompatible feature combination. 401 means the key is absent, invalid, expired, or injected into the wrong runtime. 402 indicates a billing limit; 429 indicates a current endpoint or model limit. Eligible 5xx and transport failures may be retried boundedly; deterministic client errors must not be retried. 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. Capture timestamp, endpoint, status, SDK version, resolved model, redacted request shape, and provider request identifier when available. 2. Check Cohere status and determine whether failures are global, model-specific, environment-specific, or request-specific. 3. Compare required v2 fields and feature combinations with the current reference. 4. Run one minimal non-sensitive reproduction with retries disabled. 5. Apply the smallest correction or mitigation and verify with one bounded probe. 6. Record the classification, evidence, correction, and rollback or escalation owner. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-common-errors