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.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has good structure with explicit 'Use when' guidance and clear domain focus on Dojo framework migrations. However, it could benefit from more specific concrete actions and additional trigger terms that users might naturally use when seeking help with version upgrades or migration tasks.
Suggestions
Add more specific concrete actions like 'run migration scripts', 'backup world state', 'validate schema compatibility', or 'resolve version conflicts'
Include additional natural trigger terms users might say such as 'upgrade world', 'version bump', 'breaking API', 'migrate contracts', or 'update dependencies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (world migrations, Dojo versions) and some actions (manage, handle, upgrade), but lacks specific concrete actions like 'run migration scripts', 'backup state', or 'validate schema compatibility'. | 2 / 3 |
Completeness | Clearly answers both what (manage migrations, handle breaking changes, upgrade Dojo versions) and when (updating deployed worlds, migrating to new versions, handling schema changes) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'migrations', 'Dojo versions', 'schema changes', but misses common variations users might say like 'upgrade world', 'version bump', 'breaking API changes', or 'migrate contracts'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Dojo', 'world migrations', and 'deployed worlds' creates a clear niche specific to the Dojo framework ecosystem, making it unlikely to conflict with generic migration or upgrade 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 skill with excellent workflow clarity and concrete executable examples. The main weakness is length - the skill tries to cover many scenarios inline rather than using progressive disclosure to reference detailed guides. Some minor verbosity in introductory sections could be trimmed.
Suggestions
Move detailed breaking change examples and data migration patterns to a separate MIGRATION_PATTERNS.md file, keeping only summaries in the main skill
Remove or condense the 'What This Skill Does' section as it largely repeats information from 'When to Use This Skill'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., 'What This Skill Does' section repeats information, and some explanations like 'Shows:' lists could be tighter). The content is mostly lean but could be condensed further. | 2 / 3 |
Actionability | Provides fully executable commands and concrete Cairo code examples throughout. Migration commands, code snippets for breaking vs safe changes, and troubleshooting steps are all copy-paste ready with specific syntax. | 3 / 3 |
Workflow Clarity | Clear numbered sequences with explicit validation checkpoints (build -> test -> migrate -> verify). The migration checklist provides comprehensive pre/during/post validation steps, and troubleshooting section addresses common failure modes. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines) and could benefit from splitting detailed content (like breaking change examples or data migration patterns) into separate reference files. Related skills are listed but inline content is heavy. | 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 | |
- 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.