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 well-crafted skill description that clearly identifies its domain (Dojo token implementation), lists specific actions, and provides explicit trigger guidance. It uses third person voice correctly and includes natural keywords that developers in the Dojo/Starknet ecosystem would use. The description is concise yet comprehensive.
| 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 and actionable skill covering the full lifecycle of Dojo tokens from implementation through deployment and indexing. Its main weakness is verbosity—the two complete contract implementations make it quite long, and the deployment/indexing workflow lacks explicit validation checkpoints. The troubleshooting section is a nice addition but would be more effective if validation steps were integrated into the workflow itself.
Suggestions
Add explicit validation checkpoints to the deployment workflow, e.g., verify contract address after migration, confirm Torii is indexing before querying.
Consider moving the full ERC20 and ERC721 contract implementations to separate reference files and keeping only a minimal example inline to reduce the skill's token footprint.
Remove the 'When to Use This Skill' and 'What This Skill Does' sections—they largely duplicate the opening sentence and add little value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with two complete contract implementations (ERC20 and ERC721) that are quite verbose. The 'When to Use This Skill' and 'What This Skill Does' sections add some redundancy. However, most content is code examples that serve a purpose, and there's minimal hand-holding explanation of basic concepts. | 2 / 3 |
Actionability | The skill provides fully executable Cairo code for both ERC20 and ERC721 implementations, concrete TOML configuration, CLI commands, SQL queries, and TypeScript SDK usage. All examples are copy-paste ready with realistic field names and patterns. | 3 / 3 |
Workflow Clarity | The deployment workflow mentions 'sozo build && sozo migrate' and noting contract addresses, but lacks explicit validation checkpoints. There's no verification step after deployment to confirm the contract is live, and no feedback loop between deploying and configuring Torii. The troubleshooting section partially compensates but doesn't constitute an inline validation step. | 2 / 3 |
Progressive Disclosure | The skill references other skills (dojo-deploy, dojo-indexer, dojo-model, etc.) and links to Origami docs, which is good. However, the two full contract implementations (~100+ lines of Cairo code) could be referenced as separate files rather than inlined, making the main skill quite long. The structure is logical but the inline code volume hurts discoverability. | 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
- steebchen/proof-of-war
- Commit
44466c6
- 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.