dojo-init
Initialize new Dojo projects with proper directory structure, configuration files, and dependencies. Use when starting a new Dojo game project or setting up the initial project structure.
86
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 — 100%
↑ 1.47xAgent 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 that clearly communicates both purpose and trigger conditions. The main weakness is moderate specificity - it could benefit from more concrete details about what exactly gets created. The Dojo-specific focus provides good distinctiveness.
Suggestions
Add more specific concrete actions like 'creates Scarb.toml, world config, and component directories' to improve specificity
Include additional trigger term variations like 'create', 'scaffold', 'bootstrap', 'init', or 'start' that users commonly use when initializing projects
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo projects) and mentions actions like 'directory structure, configuration files, and dependencies', but doesn't list multiple specific concrete actions (e.g., which config files, what dependencies, specific directory names). | 2 / 3 |
Completeness | Clearly answers both what ('Initialize new Dojo projects with proper directory structure, configuration files, and dependencies') and when ('Use when starting a new Dojo game project or setting up the initial project structure') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Dojo', 'project', 'initialize', 'setup', 'game project', but misses common variations users might say like 'create new project', 'scaffold', 'bootstrap', 'init', or 'new game'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to 'Dojo' game projects with clear niche - unlikely to conflict with generic project initialization skills due to the specific framework/platform mention. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%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 project initialization skill with excellent actionability and workflow clarity. The main weakness is some verbosity in introductory sections that explain what the skill does rather than just doing it. The configuration examples and development workflow are well-structured and immediately usable.
Suggestions
Remove or condense the 'When to Use This Skill' and 'What This Skill Does' sections - Claude can infer these from the content itself
Consider moving the full Scarb.toml and dojo_dev.toml examples to a referenced file, keeping only the essential fields inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' and 'What This Skill Does' that repeat information Claude can infer. The configuration file examples are useful but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable commands (sozo init, katana, sozo build), complete configuration file examples that are copy-paste ready, and a clear development workflow with specific commands. | 3 / 3 |
Workflow Clarity | The development workflow section provides a clear 5-step sequence with explicit commands. The customization section provides logical next steps. For a project initialization skill, this level of workflow guidance is appropriate. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of headers, and explicit references to related skills (dojo-model, dojo-system, dojo-test, dojo-deploy) for next steps. Content is appropriately structured for a single skill file. | 3 / 3 |
Total | 11 / 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.