dojo-system
Create Dojo systems that implement game logic, modify model state, and handle player actions. Use when implementing game mechanics, player commands, or automated logic.
76
66%
Does it follow best practices?
Impact
95%
1.69xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dojo-system/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is structurally sound with both 'what' and 'when' clauses clearly present, which is its strongest aspect. However, the actions described remain at a moderate level of abstraction, and the trigger terms could be more comprehensive with Dojo-specific terminology and common user phrasings. The description would benefit from more concrete actions and stronger domain-specific keywords to reduce overlap risk.
Suggestions
Add more concrete actions specific to Dojo systems, e.g., 'define system functions, execute world state transitions, validate player inputs, emit events'.
Include more Dojo-specific trigger terms such as 'ECS system', '#[dojo::contract]', 'world dispatcher', or 'Cairo system' to improve distinctiveness and matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo systems) and some actions (implement game logic, modify model state, handle player actions), but these are somewhat general rather than listing multiple concrete, specific actions like 'spawn entities, process combat, manage inventory'. | 2 / 3 |
Completeness | Clearly answers both 'what' (create Dojo systems that implement game logic, modify model state, handle player actions) and 'when' (Use when implementing game mechanics, player commands, or automated logic) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Dojo systems', 'game logic', 'player actions', 'game mechanics', 'player commands', but misses common variations users might say such as 'system contract', 'world state', 'ECS', or specific Dojo framework terminology that would improve matching. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Dojo systems' provides some distinctiveness, but terms like 'game logic', 'game mechanics', and 'player actions' are broad enough to potentially overlap with other game development skills that aren't Dojo-specific. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%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, actionable skill for Dojo system generation with excellent executable code examples and a useful quick-reference table. Its main weaknesses are redundancy (imports, events, and world access explained multiple times) and lack of validation checkpoints in the workflow for what is essentially a destructive/stateful operation (writing smart contracts). Tightening the content by removing duplicate explanations and adding compile/test validation steps would significantly improve it.
Suggestions
Remove duplicate explanations of imports, events, and world access - consolidate the 'Essential Imports' section and 'Key Concepts' section into one, keeping only the quick reference table and the full system example.
Add explicit validation checkpoints to the workflow, such as 'Compile with `sozo build` after creating the system' and 'Run `sozo test` before proceeding to deployment'.
Move the full system structure example to a separate EXAMPLES.md file and keep only a minimal example in the main skill, with a clear reference link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has significant redundancy - the imports section, events, and world access patterns are explained multiple times (Essential Imports section, then again in System Structure, then again in Key Concepts). The 'When to Use This Skill' and 'What This Skill Does' sections add little value. However, the core content is domain-specific enough that most of it earns its place. | 2 / 3 |
Actionability | The skill provides fully executable Cairo code examples throughout, including complete contract structures, import statements, model read/write operations, event emissions, and configuration files. The quick reference table and copy-paste ready code blocks make this highly actionable. | 3 / 3 |
Workflow Clarity | The system structure and design patterns are clearly presented, but there are no validation checkpoints in the workflow. For a skill involving smart contract generation that modifies game state, there should be explicit validation steps (e.g., compile check, permission verification). The 'Next Steps' section lists follow-up actions but doesn't integrate them into a validated workflow. | 2 / 3 |
Progressive Disclosure | The skill references related skills (dojo-test, dojo-model, etc.) at the end, which is good. However, the main content is quite long with repeated patterns that could be extracted into reference files. The Essential Imports section, System Structure, and Key Concepts sections overlap significantly and could benefit from better organization with the detailed example moved to a separate file. | 2 / 3 |
Total | 9 / 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.