dojo-world
Manage world permissions, namespaces, resource registration, and access control. Use when configuring world ownership, setting up authorization policies, or managing resource permissions.
80
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 — 97%
↑ 1.18xAgent success when using this skill
Validation for skill structure
Discovery
77%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 description that clearly articulates specific capabilities and includes explicit 'Use when' guidance. The main weakness is the somewhat technical terminology that may not match how users naturally phrase requests, and the permission/access control domain could overlap with other similar skills without the 'world' context being more prominent.
Suggestions
Add more natural user-facing trigger terms like 'who can access my world', 'sharing', 'user roles', or 'grant access'
Emphasize the 'world' context more prominently in the trigger terms to reduce conflict risk with general permission management skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Manage world permissions, namespaces, resource registration, and access control' - these are distinct, concrete capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Manage world permissions, namespaces, resource registration, and access control') and when ('Use when configuring world ownership, setting up authorization policies, or managing resource permissions') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'permissions', 'namespaces', 'access control', 'authorization policies', but these are somewhat technical. Missing common user variations like 'who can access', 'sharing settings', or 'user roles'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'world' context provides some specificity, but terms like 'permissions', 'access control', and 'authorization' are common across many systems. Could potentially conflict with general IAM, database permissions, or file system permission skills. | 2 / 3 |
Total | 10 / 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 guidance for Dojo world permission management with excellent executable code examples across CLI, config files, and Cairo. However, it's verbose with unnecessary framing sections, lacks validation checkpoints for permission operations, and could benefit from splitting detailed content into separate reference files.
Suggestions
Remove the 'When to Use This Skill' and 'What This Skill Does' sections - Claude doesn't need prompt examples or summaries of what the skill covers
Add explicit validation steps after permission changes (e.g., 'After granting, verify with: sozo auth list | grep <resource>')
Move the detailed 'Permission Patterns' and 'Common Scenarios' sections to a separate PATTERNS.md file, keeping only quick references in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations like the 'When to Use This Skill' section with example prompts and the 'What This Skill Does' summary that Claude doesn't need. The permission concepts section is useful but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable code examples for CLI commands, Cairo code for granting/revoking permissions, and configuration file formats. All examples are copy-paste ready with specific syntax and real patterns. | 3 / 3 |
Workflow Clarity | Steps are listed for common scenarios but lack explicit validation checkpoints. For permission management (which can be destructive), there's no verify-after-grant pattern or rollback guidance. The troubleshooting section helps but doesn't integrate into workflows. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a long monolithic document (~300 lines) that could benefit from splitting detailed patterns and troubleshooting into separate files. The 'Related Skills' section provides good cross-references but 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 | |
- 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.