Mistral Upgrade MigrationSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: mistral-upgrade-migration description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<from-version-or-surface> <to-version-or-surface> <scope>" version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: [saas, mistral, migration] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Mistral actions require network access and explicit approval" --- # 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. ## Output Return source/target pins, contract diff, destination per workflow, changed call sites, tests/canary, preview risks, rollback, and removal date. ## Examples - Upgrade the TypeScript client behind an unchanged app adapter. - Keep stable chat while separately evaluating Workflows. ## Validation Test both adapters with identical fixtures, malformed responses, cancellation, retry classes, usage, and rollback drill. ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources before relying on mutable endpoints, models, limits, prices, preview status, or retention. - Record live account observations as environment-specific evidence, not universal Mistral guarantees.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__mistral-upgrade-migration.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Mistral Upgrade Migration skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Mistral Upgrade Migration safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Mistral Upgrade Migration access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Mistral Upgrade Migration work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.