dojo-world

Grant and revoke owner and writer roles for Dojo world namespaces and resources.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shariqazeem/Prophecy-Roguelite --skill dojo-world-shariqazeem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dojo-world
Source: https://github.com/shariqazeem/Prophecy-Roguelite/tree/main/.agents/skills/dojo-world
Command: npx skills add https://github.com/shariqazeem/Prophecy-Roguelite --skill dojo-world-shariqazeem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dojo-world permission management centralizes and simplifies granting, revoking, and auditing access to namespaces and resources so teams can safely run on-chain game systems and contracts without accidental privilege escalation or unauthorized writes.

Core Features & Use Cases

  • Namespace and resource configuration: Define namespace-level and resource-specific owners and writers during deployment and runtime.
  • Granting and revoking roles: Use CLI commands or runtime Cairo calls to grant_writer, grant_owner, revoke_writer, and revoke_owner for precise access control.
  • Permission hierarchy and auditing: Support world owner, namespace owner, resource owner, and writer roles, emit permission-change events for monitoring, and include troubleshooting guidance for authorization errors.
  • Use case: Add a new movement system by granting writer permission to the my_game-Position resource and transfer namespace ownership when handing control to a multisig admin.

Quick Start

Grant writer permission to the movement system in the my_game namespace using the Sozo CLI or the world.grant_writer runtime call.

Frequently Asked Questions about dojo-world

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Dojo world permissions and access control for on-chain game systems?

Manage Dojo world permissions by defining namespace-level and resource-specific owners and writers during deployment and runtime. This centralizes access control, enabling teams to safely run on-chain game systems without accidental privilege escalation or unauthorized writes.

How do I grant writer permission to a Cairo system in a Dojo world namespace?

Grant writer permission to a Cairo system in a Dojo world namespace by using the Sozo CLI grant_writer command or the world.grant_writer runtime call. This authorizes specific systems to write to designated resources like my_game-Position.

What is the permission hierarchy when configuring access control in Dojo worlds?

The Dojo world permission hierarchy supports world owner, namespace owner, resource owner, and writer roles. This tiered structure ensures precise authorization delegation for deploying and managing on-chain game systems.

Can I transfer namespace ownership to a multisig admin in Starknet using Dojo?

Yes, you can transfer namespace ownership to a multisig admin in Starknet using Dojo by executing the revoke_owner and grant_owner operations. This securely delegates administrative control over on-chain game namespaces.

Why does my Dojo world deployment fail with an authorization error during CLI operations?

Dojo world deployment authorization errors during CLI operations occur when the signer lacks the required namespace or resource owner permissions. Troubleshooting involves verifying the current permission state programmatically and ensuring proper owner roles are granted.

Does Dojo world management emit events for permission auditing and monitoring?

Yes, Dojo world management emits permission-change events whenever writer or owner roles are granted or revoked. These events provide a reliable audit trail for monitoring access control modifications across namespaces and resources.