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.
78
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 skill description that clearly defines its purpose and when to use it. The Dojo/ECS focus provides good distinctiveness, and the explicit 'Use when...' clause ensures proper triggering. However, it could benefit from more specific concrete actions and additional trigger terms that users might naturally use.
Suggestions
Expand concrete actions to be more specific, e.g., 'Create Dojo models, define entity keys, implement component traits, structure game state storage'
Add more natural trigger terms users might say, such as 'Cairo structs', 'Starknet game', 'on-chain state', or 'world components'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo models, game state) and some actions (key definitions, trait derivations, ECS patterns), but doesn't list multiple concrete actions like 'define entities, create components, implement storage patterns'. | 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', 'game entities', 'components', 'ECS patterns', but missing common variations users might say like 'Cairo', 'Starknet', 'on-chain game', 'world state', or 'structs'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Dojo framework and ECS game development patterns; unlikely to conflict with general coding skills or other game development tools due to specific terminology like 'Dojo', 'trait derivations', and 'ECS patterns'. | 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 usage from the content itself.
Add a validation step showing how to verify a model compiles correctly (e.g., `scarb build` command and expected output) before proceeding to system creation.
| 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 player-owned models, composite keys, singletons, and ECS composition. All code is copy-paste ready with proper imports and usage examples. | 3 / 3 |
Workflow Clarity | The skill covers model creation patterns 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, dojo-config) are clearly signaled at the end without deep nesting. | 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.