dojo-config
Configure Scarb.toml, dojo profiles, world settings, and dependencies. Use when setting up project configuration, managing dependencies, or configuring deployment environments.
83
75%
Does it follow best practices?
Impact
100%
1.31xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dojo-config/SKILL.mdQuality
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 solid skill description that clearly identifies its domain (Dojo/Scarb project configuration) with specific artifacts and an explicit 'Use when' clause. Its main weakness is that trigger terms could be broader to capture more natural user phrasings, but the domain-specific terminology provides good distinctiveness.
Suggestions
Add more natural trigger term variations such as 'toml file', 'dojo config', 'Scarb configuration', 'project setup' to improve keyword coverage for how users might phrase their requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configure Scarb.toml, dojo profiles, world settings, and dependencies. These are distinct, named configuration artifacts rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure Scarb.toml, dojo profiles, world settings, dependencies) and 'when' (setting up project configuration, managing dependencies, configuring deployment environments) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Scarb.toml', 'dojo profiles', 'dependencies', and 'deployment environments', but misses common user variations like 'toml file', 'dojo config', 'world config', 'project setup', or 'Scarb configuration'. The terms are somewhat domain-specific and may not cover all natural phrasings. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of Scarb.toml, dojo profiles, and world settings creates a very specific niche tied to the Dojo/Starknet ecosystem. This is unlikely to conflict with generic configuration or dependency management 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 is a solid reference skill for Dojo configuration with excellent actionability—every configuration scenario has concrete, copy-paste ready TOML examples. The main weaknesses are the length (could benefit from splitting detailed examples into reference files) and the lack of explicit validation steps after configuration changes. Some introductory sections add little value and could be trimmed.
Suggestions
Add a validation step after configuration changes, e.g., 'Run `sozo build` to verify your configuration is valid before deploying'
Move the full environment examples (dev/production) and dependency examples to a separate reference file to reduce the main skill's length
Remove the 'Quick Start' interactive/direct mode section and 'When to Use This Skill' trigger phrases—these don't add actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary sections like 'When to Use This Skill' trigger phrases and 'What This Skill Does' summaries that repeat the description. The 'Quick Start' interactive/direct mode section adds little value. However, the configuration examples themselves are lean and well-structured. | 2 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready TOML configuration blocks for every scenario: Scarb.toml, profile configs, dependencies, permissions, environment examples for dev and production. Commands like `sozo build --profile mainnet` are specific and executable. | 3 / 3 |
Workflow Clarity | The profile system and configuration structure are clearly explained, but there's no validation workflow. After editing configuration files, there are no steps to validate the config is correct (e.g., `sozo build` to check, verify RPC connectivity). The troubleshooting section partially compensates but doesn't constitute explicit validation checkpoints in a workflow. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and sections, and references related skills at the end. However, the file is quite long (~200+ lines of configuration examples) and some sections like the full environment examples could be split into separate reference files. The references to other skills are present but the 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 | |
- 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.