Configure Scarb.toml, dojo profiles, world settings, and dependencies. Use when setting up project configuration, managing dependencies, or configuring deployment environments.
83
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/skillEvaluation — 100%
↑ 1.31xAgent success when using this skill
Validation 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-crafted skill description that clearly identifies its niche in the Scarb/Dojo ecosystem. It provides specific configuration targets 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.
| 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 'environment config'. | 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 that would not 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 is a solid configuration reference skill with excellent actionability through complete, executable TOML examples. However, it's verbose with unnecessary meta-sections (When to Use, What This Skill Does, Quick Start prompts) and could benefit from validation workflows when modifying configurations. The content would be more token-efficient if detailed environment examples were moved to a separate reference file.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', and 'Quick Start' sections - Claude doesn't need prompt examples or descriptions of what the skill does
Add a validation workflow: after editing config, run 'sozo build' to verify syntax before deployment
Move detailed environment examples (Development/Production sections) to a separate EXAMPLES.md file and reference it from the main skill
| 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 repeat information Claude can infer. The Quick Start interactive/direct mode section adds little value. | 2 / 3 |
Actionability | Provides fully executable TOML configurations with complete, copy-paste ready examples for every configuration scenario. Includes specific commands for profile usage and concrete file naming conventions. | 3 / 3 |
Workflow Clarity | Steps are listed but validation is implicit. The 'Next Steps' section provides sequence but lacks explicit checkpoints. For configuration changes that could break deployments, there's no validate-then-apply workflow or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines) with detailed examples that 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 | |
Table of Contents
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.