dojo-deploy

Deploy Dojo worlds to Katana, Sepolia, or Starknet mainnet.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires katana, sozo, torii, jq, curl.

What problem does it solve?

This Skill simplifies and automates deploying Dojo game worlds to local Katana, Sepolia testnet, or Starknet mainnet by removing manual setup, build, migration, and indexer configuration steps.

Core Features & Use Cases

  • Start and configure Katana: Launch a local sequencer with recommended options, optional persistent storage, and genesis Controller deployment for Cartridge Controller compatibility.
  • Build, migrate, and verify: Run sozo build and sozo migrate workflows, preview deployments with inspect, and extract addresses from generated manifests.
  • Torii indexing and deployment orchestration: Start the Torii indexer against a deployed world and manage deployment lifecycles, useful for local development, CI pipelines, and testnet/mainnet rollouts.
  • Use Case: For local development, use the provided deploy script to start Katana, build and migrate your world, extract the manifest, and bring up Torii for immediate testing.

Quick Start

Start Katana and deploy my world to the local Katana sequencer using the default dev profile.

Frequently Asked Questions about dojo-deploy

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

FAQPage Schema
How do I deploy a Dojo world to a local Katana sequencer?

To deploy a Dojo world to a local Katana sequencer, start Katana, run sozo build, execute sozo migrate with your profile, and extract addresses from the generated manifest, automating local development setup for immediate testing.

What tools do I need installed to deploy a Dojo world?

You need katana, sozo, torii, jq, and curl available in your system PATH to deploy Dojo worlds, handling local sequencing, building, migrating, indexing, and data extraction across local and live networks.

Can I deploy my Dojo world to Starknet mainnet or Sepolia testnet?

Yes, you can deploy Dojo worlds to Sepolia testnet or Starknet mainnet using sozo migrate to push contracts, which generates a manifest file containing the world and contract addresses for verification.

How does the Torii indexer work with a deployed Dojo world?

The Torii indexer starts against your deployed Dojo world to index events and state changes, managing the deployment lifecycle and enabling querying of world data for local development, CI pipelines, and testnet rollouts.

What is the best way to preview a Dojo deployment before migrating?

The best way to preview a Dojo deployment is using sozo inspect before running sozo migrate, allowing you to verify the build output and expected contract changes without committing state to Katana or live networks.

Where do I find world and contract addresses after deploying with sozo?

After deploying with sozo, you find world and contract addresses by extracting them from the generated manifest JSON file, where the specific profile used during migration produces a corresponding manifest file containing these deployment addresses.