dojo-deploy
Deploy Dojo worlds to local Katana, testnet, or mainnet. Configure Katana sequencer and manage deployments with sozo. Use when deploying your game or starting local development environment.
90
88%
Does it follow best practices?
Impact
93%
1.36xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly identifies the specific toolchain (Dojo, Katana, sozo), lists concrete actions (deploy, configure, manage), specifies target environments, and includes an explicit 'Use when' clause. The only minor note is the use of second person ('your game') which slightly deviates from the preferred third-person voice, but it doesn't significantly impact clarity or selection accuracy.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deploying Dojo worlds, configuring Katana sequencer, managing deployments with sozo, and specifies target environments (local Katana, testnet, mainnet). | 3 / 3 |
Completeness | Clearly answers both what ('Deploy Dojo worlds to local Katana, testnet, or mainnet. Configure Katana sequencer and manage deployments with sozo') and when ('Use when deploying your game or starting local development environment'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'deploy', 'Dojo', 'Katana', 'testnet', 'mainnet', 'sozo', 'local development environment', 'game'. These cover the terms a Dojo developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terms like 'Dojo worlds', 'Katana sequencer', and 'sozo' that are unique to the Dojo/Starknet ecosystem, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 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, highly actionable deployment skill with clear workflows and good validation checkpoints. Its main weakness is length — it tries to be both an overview and a comprehensive reference, resulting in redundancy and a document that could benefit from splitting detailed Katana configuration and Slot deployment into separate files. The executable examples and troubleshooting section are strong assets.
Suggestions
Remove redundant sections: the 'When to Use', 'What This Skill Does', and 'Quick Start' sections largely duplicate information found in the actual workflow sections below.
Extract Katana configuration details (mining modes, persistent storage, network forking, Cartridge Controller) into a separate KATANA_CONFIG.md reference file to keep SKILL.md as a concise overview.
Consolidate the repeated `katana --dev --dev.no-fee` command — it appears 4 times and could be shown once with a reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., `katana --dev --dev.no-fee` appears 4 times, the 'When to Use' and 'What This Skill Does' sections add little value, and the Quick Start section with quoted strings is unnecessary). The content could be tightened significantly while preserving all useful information. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete TOML configuration examples, concrete sozo commands with arguments, and a detailed manifest JSON example. Commands are copy-paste ready with specific flags and URLs. | 3 / 3 |
Workflow Clarity | The deployment workflow is clearly sequenced (build → inspect → migrate → verify) with explicit validation checkpoints. The deployment checklist includes pre/during/post steps, and the troubleshooting section provides error recovery guidance. The local development workflow shows a clear multi-terminal setup with verification steps. | 3 / 3 |
Progressive Disclosure | References to related skills and external docs are well-signaled, but the file itself is quite long (~300 lines) with sections like Katana Configuration, Mining Modes, Network Forking, and Slot Deployment that could be split into separate reference files. The inline content is heavy for a SKILL.md overview. | 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
52a1507
- 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.