Manage world migrations, handle breaking changes, and upgrade Dojo versions. Use when updating deployed worlds, migrating to new versions, or handling schema changes.
83
76%
Does it follow best practices?
Impact
98%
1.53xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dojo-migrate/SKILL.mdBreaking change strategy selection
Key change identified as breaking
100%
100%
Type change identified as breaking
100%
100%
Field addition identified as safe
100%
100%
Parallel model strategy used
30%
100%
Versioned model naming
0%
100%
New world seed strategy documented
0%
100%
Seed value in dojo_dev.toml
0%
100%
sozo inspect step included
0%
100%
Build before migrate
100%
100%
Model cannot be removed acknowledgment
25%
100%
Post-migration steps mentioned
100%
100%
Testnet-before-mainnet recommended
100%
100%
Dojo version upgrade workflow
dojo dependency version updated
100%
100%
dojo_cairo_test version updated
100%
100%
Both versions match
100%
100%
sozo build in workflow
0%
100%
sozo test in workflow
0%
100%
sozo migrate in workflow
100%
100%
Changelog review step present
100%
100%
sozo inspect in workflow
0%
100%
Sepolia profile used
100%
100%
Post-migration client bindings
0%
100%
Post-migration Torii update
0%
100%
On-chain data migration contract
#[dojo::contract] annotation
100%
100%
world.read_model() used
100%
100%
world.write_model() used
100%
100%
Old model retained
100%
100%
New model versioned name
0%
50%
world_default() called
100%
100%
Accepts array of keys
100%
100%
Field transformation present
100%
100%
sozo build step documented
100%
100%
sozo execute documented
100%
100%
sozo inspect step documented
0%
100%
Post-migration Torii update mentioned
83%
100%
52a1507
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.