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.
83
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 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, initializes Cairo contracts, sets up world configuration'
Include additional trigger term variations like 'create', 'scaffold', 'bootstrap', 'init dojo', 'new dojo app'
| 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 keywords like 'Dojo', 'project', 'initialize', 'setup', and 'game project', but missing common variations users might say like 'create new project', 'scaffold', 'bootstrap', or 'init'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Dojo' framework and 'game project' creates a clear niche that is unlikely to conflict with generic project initialization skills or other framework-specific skills. | 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 skill with excellent actionability and workflow clarity, providing complete executable examples and clear step-by-step guidance. The main weakness is some verbosity in introductory sections that explain what the skill does rather than just doing it. The structure and progressive disclosure are well-executed with clear navigation to related skills.
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 merging the 'Quick Start' section directly into the main flow rather than having a separate introductory section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' and 'What This Skill Does' that explain obvious context. The content is mostly efficient but could be tightened by removing redundant explanations and combining related sections. | 2 / 3 |
Actionability | Provides fully executable commands and complete configuration file examples. The quick start, development workflow, and customization sections give copy-paste ready code and clear step-by-step instructions. | 3 / 3 |
Workflow Clarity | The development workflow section provides a clear 5-step sequence from initialization through testing. Steps are numbered, commands are explicit, and the flow is logical with no ambiguity about order or dependencies. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from quick start to detailed configuration to customization. References to related skills are clearly signaled at the end, and content is appropriately structured without deep nesting. | 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.