dojo-token
Implement, deploy, and index ERC20 and ERC721 tokens in Dojo. Use when adding token contracts, deploying them, or configuring Torii to index balances and transfers.
87
82%
Does it follow best practices?
Impact
99%
2.35xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly defines its scope within the Dojo/Torii ecosystem for token implementation. It uses proper third-person voice, lists concrete actions, includes domain-specific trigger terms that users would naturally use, and has an explicit 'Use when...' clause. The description is concise yet comprehensive enough to distinguish it from other blockchain or smart contract skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'implement, deploy, and index ERC20 and ERC721 tokens' along with specific sub-actions like 'adding token contracts, deploying them, configuring Torii to index balances and transfers.' | 3 / 3 |
Completeness | Clearly answers both what ('Implement, deploy, and index ERC20 and ERC721 tokens in Dojo') and when ('Use when adding token contracts, deploying them, or configuring Torii to index balances and transfers') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ERC20', 'ERC721', 'tokens', 'Dojo', 'deploy', 'Torii', 'index', 'balances', 'transfers', 'token contracts'. These are the exact terms a developer in this ecosystem would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: ERC20/ERC721 tokens specifically in the Dojo framework with Torii indexing. This is unlikely to conflict with other skills due to the very specific technology stack mentioned. | 3 / 3 |
Total | 12 / 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 comprehensive skill with excellent actionability—providing complete, executable Cairo contracts, deployment configs, and query examples. Its main weaknesses are verbosity (two full contract implementations inline make it long) and a lack of explicit workflow sequencing with validation checkpoints between the deploy and index steps. The troubleshooting section is a nice practical addition.
Suggestions
Add an explicit numbered workflow sequence (implement → build → deploy → verify deployment → configure Torii → verify indexing) with validation checkpoints at each stage
Consider moving the full ERC20 and ERC721 contract implementations to a referenced file (e.g., EXAMPLES.md) and keeping only a minimal snippet inline to reduce token usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with two complete contract implementations (ERC20-like and ERC721-like) that are quite verbose. Some sections like 'When to Use This Skill' and 'What This Skill Does' are redundant with each other. However, most content is substantive and not explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable Cairo code for both ERC20 and ERC721 implementations, concrete TOML configuration snippets, CLI commands, SQL queries, and TypeScript SDK examples. All code is copy-paste ready with realistic examples. | 3 / 3 |
Workflow Clarity | The deployment workflow mentions 'sozo build && sozo migrate' and noting contract addresses, but lacks explicit validation checkpoints. There's no verify step after deployment, no feedback loop for checking if contracts deployed correctly before configuring Torii. The overall flow (implement → deploy → configure Torii → query) is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | The skill references other skills (dojo-deploy, dojo-indexer) appropriately, but the inline content is quite long with two full contract implementations that could be referenced externally. The structure is reasonable with clear sections, but the balance between overview and detail leans too heavily toward inline detail. | 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.