Agent skill · Databases

mistral-upgrade-migration

Analyze, plan, and execute Mistral AI SDK upgrades with breaking change detection. Use when upgrading Mistral SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade mistral", "mistral migration", "mistral breaking changes", "update mistral SDK", "analyze mistral version".

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill mistral-upgrade-migration --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(npm:*)Bash(git:*)
Path: skills/ai-llm/mistral-upgrade-migration/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mistral AI Upgrade & Migration ## Overview Guide for upgrading Mistral AI SDK versions and handling breaking changes. ## Prerequisites - Current Mistral AI SDK installed - Git for version control - Test suite available - Staging environment ## Instructions ### Step 1: Check Current Version ```bash # Node.js SDK npm list @mistralai/mistralai npm view @mistralai/mistralai versions --json | jq '.[-5:]' # Python SDK pip show mistralai pip index versions mistralai 2>/dev/null || pip install mistralai== # Check for outdated npm outdated @mistralai/mistralai ``` ### Step 2: Review Changelog ```bash # Check GitHub releases open https://github.com/mistralai/client-js/releases open https://github.com/mistralai/client-python/releases # Check npm changelog npm info @mistralai/mistralai ``` ### Step 3: Create Upgrade Branch ```bash # Create feature branch git checkout -b upgrade/mistral-sdk-vX.Y.Z # Backup current lock file cp package-lock.json package-lock.json.bak # Upgrade SDK npm install @mistralai/mistralai@latest # Or specific version npm install @mistralai/mistralai@1.2.0 # Check what changed npm diff @mistralai/mistralai ``` ### Step 4: Handle Breaking Changes **Common Migration Patte

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Check Current Version
  5. Step 2: Review Changelog
  6. Step 3: Create Upgrade Branch
  7. Step 4: Handle Breaking Changes
  8. Step 5: Run Tests
  9. Step 6: Create Migration Script
  10. Step 7: Document Changes
  11. Output
  12. Version Compatibility
  13. Error Handling
  14. Examples
Ships with 1 file
  • metadata.json
Commands it runs
Node.js SDK
npm list @mistralai/mistralai
npm view @mistralai/mistralai versions --json | jq '.[-5:]'
Python SDK
pip show mistralai
pip index versions mistralai 2>/dev/null || pip install mistralai==
Check for outdated
npm outdated @mistralai/mistralai
Check GitHub releases
open https://github.com/mistralai/client-js/releases
More from claude-skill-registry
All skills →
About this skill
What does the mistral-upgrade-migration skill do?

Analyze, plan, and execute Mistral AI SDK upgrades with breaking change detection. Use when upgrading Mistral SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade mistral", "mistral migration", "mistral breaking changes", "update mistral SDK", "analyze mistral version".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill mistral-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going