Agent skill · software engineering · jeremylongshore
mistral-upgrade-migration
Migrate a pinned Mistral client or deprecated API surface through characterization, contract diffing, and staged rollback. Use when upgrading SDKs or moving API generations. Trigger with "upgrade Mistral SDK", "migrate Mistral Agents", or "fix Mistral deprecations".
Why this skill is useful
Adds an automated migration script for Mistral SDK upgrades that the AI cannot generate on its own.
What it needs
Requires jq, npm, pip installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Mistral SDK and API Surface Upgrade Overview Upgrade from evidence, not search-and-replace. Characterize the current adapter, compare exact target contracts, and isolate Public Preview migrations from dependency maintenance. Prerequisites A clean branch, pinned source/target versions, and adapter inventory. Characterization tests for requests, streams, errors, usage, and state. A canary, compatibility window, and rollback owner. Current Contract Current docs expose Public Preview beta Agents and Conversations plus Workflows, while deprecated Agents remains documented. Choose the target per workload; this is not a one-to-one rename. Authentication Use offline characterization where possible. Live comparison uses the server-side key, synthetic content, fixed budget, and content-free evidence. Instructions 1. Inventory imports, types, endpoints, models, options, parsing, retries, and state IDs. 2. Lock characterization tests before changing dependencies. 3. Diff releases, schemas, preview labels, and unsupported features. 4. Choose per workload: stable chat, Workflows, or explicitly accepted beta Agents/Conversations. 5. Migrate one adapter path at a time without leaking target SDK objects. 6. Run offline regression and approved canary; remove compatibility only after rollback expiry. Tool Discipline Use Read, Glob, and Grep to inspect code, locks, configuration, tests, and evidence. Use Write and Edit only for approved repository changes. Invocation alone does not authorize network calls, paid usage, uploads, stateful resources, admin mutations, deployments, or deletion. Approval Boundaries Require approval for dependencies, preview adoption, endpoint changes, live comparison, state migration, or compatibility removal. Error Handling Compiling can still hide stream, error, usage, or pagination changes. Deprecated-to-beta Agents may require redesigned state lifecycle. Automatic model substitution invalidates quality, price, and safety baselines. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-upgrade-migration