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.
85
78%
Does it follow best practices?
Impact
100%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/dojo-model/SKILL.mdEvaluation results
100%
10%Player State Models for an On-Chain RPG
Player model with nested struct
dojo::model attribute
100%
100%
Drop trait derived
100%
100%
Serde trait derived
100%
100%
Key field present
100%
100%
Keys before data fields
100%
100%
ContractAddress key type
100%
100%
Nested struct Introspect
100%
100%
ContractAddress import
100%
100%
Introspect import
0%
100%
Nested struct not a model
100%
100%
100%
3%Guild Resource Tracker System
Composite key model and system read/write
Composite key fields
100%
100%
Keys before data fields
100%
100%
Drop and Serde derived
100%
100%
dojo::model attribute
100%
100%
ModelStorage import
100%
100%
World storage call
100%
100%
write_model usage
100%
100%
read_model usage
100%
100%
Tuple for composite read
100%
100%
world.uuid() usage
78%
100%
100%
7%Dungeon Crawler Entity System Design
ECS composition and global singleton
Enum derives Introspect
100%
100%
ECS separation
100%
100%
dojo::model on each model
100%
100%
Drop and Serde on all models
100%
100%
Key field in each model
100%
100%
Keys before data
100%
100%
Global singleton constant key
50%
100%
Singleton model has single key field
100%
100%
No monolithic entity struct
100%
100%
Copy trait on primitive-only models
100%
100%
- Repository
- steebchen/proof-of-war
- Commit
44466c6
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.