dojo-world
Manage world permissions, namespaces, resource registration, and access control. Use when configuring world ownership, setting up authorization policies, or managing resource permissions.
77
66%
Does it follow best practices?
Impact
97%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dojo-world/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is structurally sound with a clear 'what' and 'when' clause, earning full marks on completeness. However, the actions described are somewhat abstract and overlapping (permissions, access control, resource permissions), and the trigger terms lean technical without covering common user phrasings. The 'world' qualifier adds some distinctiveness but could be clearer about what system or platform this applies to.
Suggestions
List more concrete, distinct actions such as 'create namespaces', 'assign roles', 'grant or revoke access', 'register resources' instead of overlapping abstract terms.
Add natural user-facing trigger terms like 'who can access', 'roles', 'grant access', 'revoke permissions', or 'RBAC' to improve keyword coverage.
Clarify what 'world' refers to (e.g., a specific platform or game engine) to reduce conflict risk with generic permission-management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (permissions/access control) and lists several actions (manage permissions, namespaces, resource registration, access control), but these are somewhat abstract and overlapping rather than concrete distinct operations like 'create namespace', 'assign role', or 'revoke access'. | 2 / 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 an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'permissions', 'namespaces', 'access control', 'authorization policies', and 'resource permissions', but these are somewhat technical. Missing common user variations like 'who can access', 'roles', 'ACL', 'RBAC', or 'grant/revoke access'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'world permissions' and 'world ownership' terms provide some distinctiveness suggesting a specific platform or system, but 'access control', 'authorization policies', and 'resource permissions' are generic enough to potentially overlap with other permission-management skills. | 2 / 3 |
Total | 9 / 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 with excellent actionability—concrete CLI commands, TOML configs, and Cairo code examples cover the full permission management lifecycle. The main weaknesses are verbosity (some sections could be trimmed or extracted) and missing validation checkpoints in workflows involving destructive permission changes like ownership transfer. The troubleshooting section is helpful but should be integrated as verification steps within the workflows themselves.
Suggestions
Add explicit validation steps after permission changes (e.g., 'Verify: check `sozo auth list` or call `world.is_writer()` to confirm the grant took effect') especially for the ownership transfer workflow.
Extract Permission Patterns, Common Scenarios, and Permission Events into a separate reference file to reduce the main skill's token footprint.
Remove the 'When to Use This Skill' and 'What This Skill Does' sections—these duplicate information already conveyed by the title and description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary sections like 'When to Use This Skill' with example prompts, 'What This Skill Does' summary that repeats the heading, and 'Next Steps' with generic advice. The permission concepts section explaining owner vs writer is useful domain knowledge, but some explanations could be tighter. The Permission Events section and debug_permissions function add bulk without strong justification. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands (sozo auth grant/revoke), complete Cairo code examples for granting/revoking/checking permissions, and concrete TOML configuration examples. Code is copy-paste ready with realistic resource names and clear parameter patterns. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints. For permission management—which involves access control and can be destructive (e.g., revoking your own ownership)—there are no verification steps after granting/revoking permissions. The 'Transfer Namespace Ownership' example is particularly risky without a validation step between grant and revoke. The troubleshooting section partially compensates but doesn't integrate into workflows. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical progression from concepts to config to CLI to runtime to patterns. However, at ~200+ lines, some sections (Permission Events, Common Scenarios, Permission Patterns) could be split into referenced files. The 'Related Skills' section at the end provides good cross-references but the main body is monolithic. | 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.