Agent skill · software engineering · jeremylongshore
mistral-migration-deep-dive
Migrate an existing model workload to Mistral through semantic mapping, dual-run evaluation, bounded canary, and provider rollback. Use when re-platforming from another provider. Trigger with "migrate to Mistral", "move from OpenAI to Mistral", or "compare a workload with Mistral".
Why this skill is useful
Adds executable scripts for assessing AI integration points and provides a comprehensive migration guide with model mapping and adapter patterns.
What it needs
Requires npm installed locally. Requires mistral account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cross-Provider Migration to Mistral Overview Treat migration as behavior and operations redesign, not field renaming. Preserve the application contract while re-evaluating models, prompts, streams, tools, safety, state, data, spend, and incidents. Prerequisites A source workload inventory and application-owned adapter. Golden/adversarial evaluation sets with governed data. Current Mistral access, dual-run budget, canary, rollback, and exit owners. Current Contract Chat, embeddings, classifiers, files/OCR, audio, batch, Workflows, and Public Preview stateful APIs are provider-specific. No source feature, model, tool, safety result, or state object is automatically equivalent. Authentication Keep source and Mistral credentials in separate secret references with independent owners. Dual-run data must be approved for both providers. Instructions 1. Inventory source messages, streams, tools, structure, embeddings, files, state, retry, usage, and safety. 2. Define the stable app contract and identify source-specific behavior to adapt or retire. 3. Map workloads to current Mistral surfaces; reject unsupported or unacceptable preview substitutions. 4. Build target adapter and run offline characterization against shared normalized fixtures. 5. Run approved dual evaluation for correctness, safety, latency, usage, failure, and governance. 6. Canary bounded traffic with kill switch; reconcile state, cut over, and retain rollback. 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 Dual submission, customer data, new spend, preview APIs, production routing, state copying, source shutdown, or credential deletion require approval. Error Handling Equivalent parameter names can differ in defaults/semantics. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-migration-deep-dive