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.
Install with Tessl CLI
npx tessl i github:steebchen/proof-of-war --skill dojo-migrate83
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/skillEvaluation — 98%
↑ 1.53xAgent success when using this skill
Validation 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 is a solid description with clear 'what' and 'when' components and good distinctiveness for the Dojo ecosystem. The main weakness is moderate specificity - it could benefit from listing more concrete actions like specific migration commands or procedures. Trigger terms are adequate but could include more natural user phrasings.
Suggestions
Add more concrete actions like 'run migration scripts', 'update contract ABIs', or 'resolve version conflicts' to improve specificity
Include additional natural trigger terms users might say, such as 'update my world', 'version bump', or 'compatibility issues'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (world migrations, Dojo versions) and some actions (manage, handle, upgrade), but lacks comprehensive concrete actions like specific migration steps or commands. | 2 / 3 |
Completeness | Clearly answers both what (manage migrations, handle breaking changes, upgrade versions) and when (updating deployed worlds, migrating to new versions, handling schema changes) with explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'migrations', 'breaking changes', 'upgrade', 'Dojo versions', 'schema changes', but these are somewhat technical and may miss common user phrasings like 'update my world' or 'version bump'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Dojo ecosystem with distinct triggers like 'world migrations', 'Dojo versions', and 'deployed worlds' - 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 skill with excellent workflow clarity and concrete code examples. The migration types, breaking change handling, and checklists provide comprehensive guidance. Main weaknesses are some redundant introductory content and the monolithic structure that could benefit from splitting advanced topics into separate files.
Suggestions
Remove or condense the 'When to Use This Skill' and 'What This Skill Does' sections - these repeat information Claude can infer from the content itself
Consider moving the detailed 'Handling Breaking Changes' section (Options 1-3) to a separate BREAKING_CHANGES.md file with a brief summary and link in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' and 'What This Skill Does' that repeat information Claude can infer. The migration checklist and troubleshooting sections add value but could be tighter. | 2 / 3 |
Actionability | Provides fully executable commands and concrete Cairo code examples throughout. The migration workflow has specific bash commands, the breaking changes section shows exact before/after code, and data migration includes complete implementation patterns. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit validation checkpoints. The migration workflow shows inspect → build/test → migrate sequence. The migration checklist provides pre/during/post phases with verification steps. Breaking change handling includes clear decision paths. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The 'Related Skills' section provides good cross-references, but the document is quite long (300+ lines) and could benefit from splitting detailed sections like 'Handling Breaking Changes' into separate files. | 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.