dojo-migrate
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.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is well-structured with a clear 'what' and 'when' clause, and targets a distinct niche (Dojo world migrations). However, the actions described are somewhat high-level and could benefit from more concrete specifics, and the trigger terms could cover more natural user phrasings.
Suggestions
Add more concrete actions such as 'run migration scripts', 'update world contracts', or 'resolve schema conflicts' to improve specificity.
Include additional trigger term variations like 'upgrade guide', 'Dojo upgrade', 'migrate contracts', or 'version bump' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo world migrations) and some actions (manage migrations, handle breaking changes, upgrade versions), but the actions are somewhat general and could be more concrete—e.g., specifying exact migration steps, CLI commands, or file operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage world migrations, handle breaking changes, upgrade Dojo versions) and 'when' (Use when updating deployed worlds, migrating to new versions, or handling schema changes) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'migrations', 'breaking changes', 'Dojo versions', 'schema changes', and 'deployed worlds', but misses common variations a user might say such as 'upgrade guide', 'version bump', 'migrate contracts', or 'Dojo upgrade'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Dojo-specific world migrations and version upgrades, which is a distinct niche unlikely to conflict with general migration or versioning skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflows and good validation checkpoints. Its main strength is the comprehensive coverage of migration scenarios with executable code examples and explicit checklists. The primary weakness is that it's somewhat long for a SKILL.md overview, with detailed code examples that could be offloaded to reference files, and some boilerplate sections (trigger phrases, summary) that don't add value.
Suggestions
Remove the 'When to Use This Skill' and 'What This Skill Does' sections - these are boilerplate that don't help Claude execute the skill.
Move the detailed breaking change examples and handling strategies (Options 1-3) into a separate MIGRATION-STRATEGIES.md reference file, keeping only a brief summary with links in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' trigger phrases and 'What This Skill Does' summaries that add little value. The migration types section with safe vs breaking examples is well-structured but slightly verbose with comments restating what's obvious from the code. | 2 / 3 |
Actionability | Provides concrete, executable commands (sozo build, sozo migrate, sozo inspect), real Cairo code examples for both safe and breaking migrations, specific TOML configuration snippets, and a complete data migration system example. The guidance is copy-paste ready and covers multiple concrete scenarios. | 3 / 3 |
Workflow Clarity | The migration workflow is clearly sequenced (inspect → build/test → migrate) with explicit validation checkpoints. The pre/during/post migration checklists provide comprehensive verification steps, and the troubleshooting section addresses common failure modes with specific remediation steps. | 3 / 3 |
Progressive Disclosure | The document references related skills at the end which is good, but the content itself is quite long (~200+ lines) with detailed code examples for breaking changes, handling strategies, and version upgrades all inline. The breaking changes examples and migration strategies could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- dojoengine/book
- Commit
093849a
- Reviewed
Table of Contents
Is this your skill?
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.