dojo-world

Grant and revoke writer and owner permissions for Dojo game resources.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-world-kepler22bee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dojo-world
Source: https://github.com/Kepler22bee/House-of-Stark/tree/main/contracts/.agents/skills/dojo-world
Command: npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-world-kepler22bee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and simplifies management of authorization for Dojo game worlds, removing ambiguity around who can write, own, and configure resources so developers can securely compose multi-system game architectures.

Core Features & Use Cases

  • Namespace and Resource Permissions: Grant and revoke writer and owner permissions at both namespace and individual resource levels.
  • Deployment and Runtime Support: Configure permissions in dojo_<profile>.toml and adjust them at runtime using Cairo WorldStorage APIs.
  • Auditing & Patterns: List current permissions, follow least-privilege patterns, and implement multi-system access strategies for modular game systems.

Quick Start

Grant writer permission to the my_game-Position resource for the movement system through your normal CLI or deployment configuration.

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 game resources?

Dojo world permissions and access control are managed by granting and revoking writer and owner permissions at namespace and resource levels using sozo auth CLI commands, dojo profile TOML configurations, or Cairo WorldStorage API calls.

How do I grant writer permissions to a system for a specific Dojo resource?

Grant writer permissions for a Dojo resource by using the sozo auth CLI command or configuring deployment-time permission mappings in your dojo profile TOML file to authorize the target system.

Can I configure Dojo access control permissions at runtime using Cairo?

Yes, runtime access control permissions in Dojo can be configured using Cairo WorldStorage API calls to dynamically grant, revoke, and check writer and owner permissions for game resources.

What is the best way to audit Dojo world namespace permissions?

Auditing Dojo world namespace permissions involves listing current writer and owner permissions to verify least-privilege patterns and ensure secure multi-system access strategies for modular game architectures.

Does dojo-world support both deployment-time and runtime permission management?

Yes, Dojo world permission management supports deployment-time configuration via dojo profile TOML entries and runtime adjustments through Cairo WorldStorage APIs for granting and revoking resource access.

Why should I use namespace-level access control for Dojo game systems?

Namespace-level access control secures multi-system game architectures by centralizing authorization, removing ambiguity around resource ownership, and enforcing least-privilege patterns across modular Dojo components.