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 ./.agents/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 'Use when' clause and targets a specific niche (Dojo world migrations). Its main weakness is that the capability descriptions could be more concrete with specific actions, and the trigger terms could cover more natural user phrasings. Overall it's a solid mid-to-high quality description.
Suggestions
Add more concrete actions such as 'run migration scripts, resolve version conflicts, update entity schemas, handle state transitions' to improve specificity.
Expand trigger terms to include variations like 'Dojo upgrade', 'version bump', 'compatibility issues', 'migration script', or 'world update' to better match natural user language.
| 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 rather than listing multiple concrete specific operations like 'run migration scripts, update schema definitions, resolve version conflicts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage world migrations, handle breaking changes, upgrade Dojo versions) and 'when' with an explicit 'Use when' clause specifying triggers (updating deployed worlds, migrating to new versions, handling schema changes). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'migrations', 'breaking changes', 'Dojo versions', 'schema changes', and 'deployed worlds', but misses common variations users might say such as 'upgrade guide', 'version bump', 'compatibility issues', 'Dojo upgrade', or 'migration script'. | 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 tools or other framework-specific 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 migration guide with clear workflows, concrete code examples, and good validation checkpoints. Its main weaknesses are moderate verbosity (unnecessary prompt examples, redundant introductory sections) and a monolithic structure that could benefit from splitting detailed examples into separate reference files. The migration checklist and troubleshooting sections are particularly strong additions.
Suggestions
Remove the 'When to Use This Skill' and 'What This Skill Does' sections, and the 'Quick Start' prompt examples - they consume tokens without adding actionable guidance.
Extract the detailed breaking change examples and data migration system code into a separate MIGRATIONS_REFERENCE.md file, keeping only a 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 don't add actionable value. The 'Quick Start' section with quoted prompts rather than actual commands is wasted space. Some sections like the migration checklist are useful but could be tighter. | 2 / 3 |
Actionability | The skill 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 practical troubleshooting steps. The data migration system example is fully fleshed out with real code patterns. | 3 / 3 |
Workflow Clarity | The migration workflow is clearly sequenced (inspect → build/test → migrate) with explicit validation checkpoints. The migration checklist provides pre/during/post verification steps. The handling of breaking changes presents clear decision paths (new world, parallel models, data migration). The troubleshooting section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, and references related skills at the end. However, the document is quite long (~250 lines) and some sections like the detailed breaking change examples and the data migration system code could be split into separate reference files. Everything is inline in a single monolithic document. | 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
- steebchen/proof-of-war
- Commit
44466c6
- 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.