dojo-config
Configure Scarb.toml, dojo profiles, world settings, and dependencies. Use when setting up project configuration, managing dependencies, or configuring deployment environments.
79
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/skillValidation 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-structured skill description that clearly identifies its domain (Scarb/Dojo configuration) with specific capabilities and explicit usage triggers. The main weakness is that trigger terms lean technical, which may miss users who describe their needs in more casual language. Overall, it follows the recommended pattern and would perform well in skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure Scarb.toml, dojo profiles, world settings, and dependencies' - these are distinct, named configuration elements rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Configure Scarb.toml, dojo profiles, world settings, and dependencies') AND when ('Use when setting up project configuration, managing dependencies, or configuring deployment environments') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Scarb.toml', 'dojo profiles', 'dependencies', 'configuration', and 'deployment environments', but these are fairly technical terms. Missing common variations users might say like 'config file', 'project setup', 'toml', or 'settings file'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Scarb/Dojo ecosystem with distinct triggers like 'Scarb.toml', 'dojo profiles', and 'world settings' - these are unique identifiers unlikely to conflict with generic configuration 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 comprehensive, actionable configuration guidance with excellent TOML examples that are immediately usable. However, it's somewhat verbose with unnecessary meta-sections (When to Use, What This Does, Quick Start prompts) and could benefit from validation workflows when making configuration changes that affect deployments.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', and 'Quick Start' sections - they add little value and Claude can infer usage from the content
Add validation steps for configuration changes, e.g., 'After modifying Scarb.toml, run `scarb build` to verify syntax before deployment'
Consider moving the full environment examples (Development/Production) to a separate EXAMPLES.md file and keeping only one representative example inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good examples, but includes some unnecessary sections like 'When to Use This Skill' with example prompts and 'What This Skill Does' that restate obvious information. The Quick Start interactive/direct mode section adds little value. | 2 / 3 |
Actionability | Provides fully executable TOML configurations that are copy-paste ready. Each configuration section includes complete, working examples with realistic values and clear syntax. | 3 / 3 |
Workflow Clarity | The profile system and deployment workflow are explained, but lacks explicit validation checkpoints. For configuration changes that affect deployments, there's no verify-then-proceed pattern or error recovery guidance beyond basic troubleshooting. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~200 lines of configuration examples) when some could be split into separate reference files. The 'Related Skills' section provides good navigation, but inline content could be better distributed. | 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.