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.
82
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.07xAgent 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 reasonably well-structured description with clear 'what' and 'when' clauses targeting Dojo game development. The main weaknesses are moderate specificity in concrete actions and trigger terms that could include more user-natural variations. The domain-specific focus (Dojo/ECS) provides good distinctiveness.
Suggestions
Add more concrete actions like 'define entity structs', 'implement component storage', 'configure model keys' to improve specificity
Include additional trigger terms users might naturally say such as 'Cairo struct', 'data model', 'game data', or 'world state'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo models, game state) and mentions some actions (key definitions, trait derivations, ECS patterns), but doesn't list multiple concrete specific actions like 'define components', 'implement storage', 'configure serialization'. | 2 / 3 |
Completeness | Clearly answers both what ('Create Dojo models for storing game state with proper key definitions, trait derivations, and ECS patterns') and when ('Use when defining game entities, components, or state structures') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Dojo models', 'game state', 'entities', 'components', 'ECS patterns', but missing common variations users might say like 'struct', 'data model', 'storage schema', or 'Cairo models'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Dojo models', 'ECS patterns', and 'game state' creates a clear niche that is unlikely to conflict with general coding skills or other game development skills not specific to Dojo. | 3 / 3 |
Total | 10 / 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 skill with excellent actionability through concrete, executable Cairo code examples covering multiple model patterns. The main weaknesses are some unnecessary introductory sections that explain what the skill does rather than just doing it, and missing validation/verification guidance for ensuring models are correctly defined before use.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', and 'Quick Start' sections - they explain rather than instruct and Claude can infer when to use the skill
Add a validation step showing how to verify a model compiles correctly (e.g., `sozo build` command with expected output)
Consider adding a brief troubleshooting section for common model definition errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use This Skill' with example prompts and 'What This Skill Does' that explain things Claude can infer. The 'Quick Start' interactive/direct mode section adds little value. | 2 / 3 |
Actionability | Provides fully executable Cairo code examples throughout, with concrete patterns for different use cases (player-owned, composite keys, singletons, ECS). Code is copy-paste ready with proper imports and usage examples. | 3 / 3 |
Workflow Clarity | The skill covers model creation well but lacks explicit validation steps. The 'Next Steps' section mentions related skills but doesn't provide a clear workflow for verifying models work correctly before proceeding to systems. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from quick start to patterns to API reference. References to related skills (dojo-system, dojo-test, etc.) are one level deep and clearly signaled at the end. | 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 | |
- 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.