dojo-model
Create Dojo models for storing game state with proper key definitions, trait derivations, and ECS patterns. Use when defining game entities, components, or state structures.
85
78%
Does it follow best practices?
Impact
100%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dojo-model/SKILL.mdQuality
Discovery
85%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 well-crafted skill description that clearly identifies its niche (Dojo framework game models with ECS patterns) and includes an explicit 'Use when' trigger clause. The main weakness is that trigger terms could be broader to capture more natural user phrasings, particularly around Cairo/Starknet ecosystem terminology that users working with Dojo would likely mention.
Suggestions
Expand trigger terms to include ecosystem-related keywords users might naturally say, such as 'Cairo struct', 'Starknet game', 'world state', or 'schema definition'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating Dojo models, storing game state, defining key definitions, trait derivations, and ECS patterns. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create Dojo models with proper key definitions, trait derivations, and ECS patterns) and 'when' (when defining game entities, components, or state structures) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Dojo models', 'game state', 'ECS patterns', 'entities', 'components', but misses common variations users might say such as 'struct', 'schema', 'world state', 'Starknet game', or 'Cairo model'. The terms are somewhat niche and technical. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific Dojo framework reference combined with ECS patterns and game state focus. Unlikely to conflict with generic game development or generic model creation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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, well-structured skill with excellent actionability — every pattern includes complete, executable Cairo code. The main weaknesses are some unnecessary preamble sections (When to Use, What This Skill Does, Quick Start interactive mode) that consume tokens without adding value, and the lack of any validation or verification steps for the model definitions. The model patterns and API reference sections are the strongest parts.
Suggestions
Remove or significantly trim the 'When to Use This Skill', 'What This Skill Does', and 'Quick Start' sections — they describe the skill rather than instruct, and Claude doesn't need prompting examples.
Add a brief validation step after model creation, such as verifying compilation with `sozo build` or checking model registration, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use This Skill' and 'What This Skill Does' which describe rather than instruct. The 'Quick Start' interactive/direct mode section adds little value. However, the core model patterns and API sections are well-condensed. | 2 / 3 |
Actionability | The skill provides fully executable Cairo code examples for every pattern — player-owned models, composite keys, singletons, ECS composition, and all CRUD operations. Import statements, read/write patterns, and field type references are all concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers model creation patterns well but lacks validation checkpoints. There's no guidance on verifying models compile correctly, no error recovery steps, and the 'Next Steps' section is just a list of other skills rather than a validated workflow. For a skill involving on-chain state definitions, some validation guidance would be valuable. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections progressing from quick start to patterns to API reference. References to related skills (dojo-system, dojo-test, dojo-config) are one level deep and clearly signaled. The content length is appropriate for inline presentation without needing external files. | 3 / 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.