Agent skill · software engineering · jeremylongshore
cohere-upgrade-migration
Migrate Cohere API v1 or older SDK usage to v2 with contract tests, model lifecycle checks, canarying, and rollback. Use when upgrading Cohere dependencies or endpoints. Trigger with "Cohere v1 to v2", "upgrade Cohere SDK", or "Cohere deprecation".
Why this skill is useful
Provides detailed migration steps and breaking changes for upgrading from Cohere API v1 to v2, which the AI wouldn't reliably generate on its own.
What it needs
Requires git, npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere API and SDK Upgrade Overview Inventory legacy behavior, move through the documented v2 contract, and prove semantic parity before removing rollback paths. 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 V2 uses messages instead of separate message, preamble, and managed conversation history fields. V2 requires explicit models; Embed also requires embedding types. V2 tools use JSON Schema and correlate results with tool-call IDs. Legacy Generate, Summarize, Classify, managed connectors, selected models, and fine-tuning paths appear on Cohere's deprecation schedule. 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. Inventory SDK versions, endpoints, parameters, models, stream events, connectors, fine-tunes, and response parsing. 2. Read the current migration and deprecation pages and classify each dependency as live, legacy, deprecated, or shut down. 3. Add golden contract tests around current user-visible behavior and failure paths. 4. Introduce the v2 client and provider adapter while retaining a feature-flagged rollback path. 5. Migrate request and response shapes, then reindex embeddings if their model contract changes. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-upgrade-migration