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.
79
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 — 95%
↑ 1.69xAgent success when using this skill
Validation for skill structure
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.
This description has good structure with an explicit 'Use when' clause and covers both what and when. However, it lacks specificity in concrete actions and misses key trigger terms that would help distinguish it as a Dojo/Cairo/Starknet blockchain game development skill rather than generic game development.
Suggestions
Add specific trigger terms like 'Dojo', 'Cairo', 'Starknet', 'on-chain game', or 'blockchain game' to improve discoverability and reduce conflict with generic game dev skills.
Replace abstract actions with concrete examples like 'define system contracts', 'emit events', 'query world state', or 'implement move/attack/spawn mechanics'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dojo systems) and lists some actions (implement game logic, modify model state, handle player actions), but the actions are somewhat abstract rather than concrete specific operations like 'spawn entities' or 'process combat calculations'. | 2 / 3 |
Completeness | Clearly answers both what (create Dojo systems for game logic, model state, player actions) and when (implementing game mechanics, player commands, or automated logic) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'game logic', 'player actions', 'game mechanics', and 'player commands', but misses common variations users might say like 'Dojo', 'Cairo', 'on-chain game', 'blockchain game', or 'Starknet'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'Dojo systems' provides some specificity, but 'game logic' and 'player actions' are generic enough to potentially conflict with other game development skills. Could benefit from mentioning the specific tech stack (Cairo/Starknet). | 2 / 3 |
Total | 9 / 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 skill provides solid, actionable guidance for creating Dojo systems with executable code examples and good organization. However, it suffers from some redundancy (world_default() explained multiple times) and lacks explicit validation workflows for verifying system correctness. The progressive disclosure and actionability are strong points.
Suggestions
Consolidate the world_default() explanations into a single section to reduce redundancy
Add an explicit validation workflow: 'After writing your system: 1. Run scarb build 2. Check for compilation errors 3. Run tests with dojo-test skill'
Remove the duplicate event emission example - keep either the one in Essential Imports or Key Concepts, not both
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some redundancy, particularly explaining world_default() multiple times and repeating similar code patterns. The import reference table is efficient, but the overall content could be tightened by consolidating duplicate explanations. | 2 / 3 |
Actionability | Provides fully executable Cairo code examples with proper imports, complete system structure, and copy-paste ready patterns. The code is concrete and specific with real function implementations. | 3 / 3 |
Workflow Clarity | Steps for creating systems are implicit rather than explicit. The 'Next Steps' section lists follow-up actions but lacks validation checkpoints. No explicit workflow for verifying system correctness before deployment. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Essential Imports, Quick Start, System Structure, Key Concepts). References to related skills are clearly signaled at the end. Content is appropriately structured for discovery. | 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.