Configure Dojo world ownership, namespaces, and resource permissions via deployment TOMLs and WorldStorage API.
npx skills add https://github.com/dojoengine/book --skill dojo-world
Please help me install this Agent Skill. Skill: dojo-world Source: https://github.com/dojoengine/book/tree/main/skills/dojo-world Command: npx skills add https://github.com/dojoengine/book --skill dojo-world
Managing world permissions, namespaces, resource registrations, and access control in Dojo worlds can be error-prone without a centralized framework. This Skill provides a cohesive approach to configure and govern who can read, write, and manage resources at every scope.
Configure permissions: Grant writer permission to my system Check permissions: List permissions for my world
High-intent search queries and answers about installing and using this skill.
To configure Dojo world ownership, you apply configuration-based permissions in deployment TOMLs and enforce runtime access checks via the WorldStorage API. This grants or revokes writer and owner permissions across world, namespace, and resource scopes.
Dojo permissions delineate access scopes: World Owners manage global resources, Namespace Owners govern specific namespaces, Resource Owners control individual resources, and Writers hold delegated write access. These roles enforce hierarchical access control policies across the world.
You grant Dojo writer permissions by declaring access rules in your deployment TOML profiles or by applying runtime permission changes via the WorldStorage API. This explicitly authorizes specific systems to write to designated world resources.
Yes, Dojo supports runtime namespace management and permission changes through the WorldStorage API. You can dynamically grant or revoke writer and owner permissions, allowing flexible access control enforcement during world execution.
Yes, Dojo supports declarative access control configuration through deployment TOML profiles. You define owner and writer permissions for namespaces and resources at deploy time, ensuring policies are applied automatically during world initialization.
Dojo resource registration failures occur when the acting account lacks sufficient owner or writer permissions for the target namespace. Audit your WorldStorage API access policies and deployment TOMLs to verify the correct role assignments.
steebchenConfigure and manage Dojo project configuration files across environments.
dojoengineConfigure Dojo world ownership, namespaces, and resource permissions via deployment TOMLs and WorldStorage API.
cartridge-ggConfigure world ownership, namespace permissions, and authorization policies in Dojo worlds.
Await-0xManage Dojo world permissions for namespaces, writers, and owners via CLI and Cairo functions.
