dojo-test
Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions. Use when testing game logic, verifying state changes, or ensuring system correctness.
83
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 — 99%
↑ 2.02xAgent success when using this skill
Validation for skill structure
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 defines its purpose for Dojo testing with specific technical terminology. It includes both what the skill does and when to use it with explicit triggers. The main weakness is trigger term coverage could include more natural variations users might use when asking for help with tests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write tests', 'using spawn_test_world, cheat codes, and assertions', 'testing game logic, verifying state changes, ensuring system correctness'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions') and when ('Use when testing game logic, verifying state changes, or ensuring system correctness') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'tests', 'Dojo models', 'systems', 'game logic', 'state changes', but missing common variations users might say like 'unit tests', 'test cases', 'testing framework', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Dojo-specific terminology ('Dojo models', 'spawn_test_world', 'cheat codes') that creates a clear niche unlikely to conflict with general testing skills or other framework-specific skills. | 3 / 3 |
Total | 11 / 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 skill provides excellent actionable guidance with comprehensive, executable Cairo test examples covering unit tests, integration tests, cheat codes, and common patterns. However, it's somewhat verbose with unnecessary meta-sections and could benefit from better progressive disclosure by moving detailed examples to separate reference files. The workflow guidance lacks explicit validation/debugging checkpoints for when tests fail.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', and 'Quick Start' sections - these explain obvious context that Claude doesn't need
Add explicit guidance for debugging failing tests (e.g., 'If test fails: check assertion message, verify model registration, ensure permissions are synced')
Consider moving detailed test patterns and cheat code examples to a separate DOJO_TEST_PATTERNS.md file, keeping SKILL.md as a concise overview
| 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' that explain obvious context. The 'Quick Start' interactive/direct mode section adds little value for Claude. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Cairo code examples throughout. Test patterns, cheat codes, and integration test examples are concrete and complete with proper imports and assertions. | 3 / 3 |
Workflow Clarity | Test organization and structure are clear, but lacks explicit validation checkpoints. The 'Next Steps' section mentions running tests but doesn't provide feedback loops for handling test failures or debugging strategies. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~250 lines) with detailed examples that could be split into separate reference files. The 'Related Skills' section provides good navigation but inline content is heavy. | 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 | |
- 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.