egs-game

Implement EGS-compatible on-chain games with Cairo contracts and denshokan-sdk frontends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EGS-game helps developers build composable, provable on-chain games and platform integrations that follow the Provable Games Embeddable Game Standard on Starknet, removing ambiguity around token-keyed storage, score reporting, and discovery metadata. It ensures game contracts expose standardized score and game-over interfaces, register SRC5 interface IDs for discovery, and integrate cleanly with MinigameToken and metagame platforms so sessions are transferable, verifiable, and platform-ready.

Core Features & Use Cases

  • IMinigameTokenData implementation for token-keyed score and game-over state so multiple concurrent sessions per player are supported.
  • SRC5 registration & Registry integration to enable discovery by MinigameToken and platforms.
  • Pre/post action hooks and ownership assertions to validate actions, wrap game logic, and emit callbacks for metagames.
  • Packed token ID encoding & batch queries for gas-efficient score retrieval and deterministic session metadata.
  • Frontend integration with denshokan-sdk for client decoding, token listing, and real-time score updates.
  • Use case: Implement a Cairo Minigame that mints sessions via a platform, tracks scores by token ID, and exposes batch endpoints for leaderboards.

Quick Start

Use the egs-game skill to implement IMinigameTokenData, register IMINIGAME_ID via SRC5, and wrap player actions with pre_action/post_action hooks to expose score and game_over by token ID.

Frequently Asked Questions about egs-game

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

FAQPage Schema
How do I implement score tracking for on-chain Cairo minigames on Starknet?

Score tracking for Cairo minigames on Starknet is implemented via the IMinigameTokenData interface, using token-keyed storage to map scores directly to token IDs. This method supports multiple concurrent game sessions per player with verifiable state.

How do I make a Starknet game discoverable by metagame platforms?

To make a Starknet game discoverable by platforms, register the IMINIGAME_ID interface ID using the SRC5 standard and Registry integration. This enables MinigameToken contracts and metagame platforms to locate your game sessions.

Can I use pre_action and post_action hooks for validating game logic in Starknet contracts?

Yes, pre_action and post_action hooks wrap player actions in Starknet contracts to validate logic, assert ownership, and emit callbacks for metagames. This ensures only authorized actions modify token-keyed game state and triggers platform events.

What is the best way to handle batch score queries for on-chain game leaderboards?

The best way to handle batch score queries for on-chain leaderboards is using packed token ID encoding and batch query endpoints. This approach enables gas-efficient score retrieval and game_over validation without querying each token individually.

Does the denshokan-sdk support real-time score updates for EGS-compatible games?

The denshokan-sdk supports frontend integration for EGS-compatible games, providing client decoding, token listing, and real-time score updates. It connects to Starknet contracts to render current game session states.

Why do I need packed token ID encoding for Starknet minigame sessions?

Packed token ID encoding is needed for Starknet minigame sessions to compress deterministic session metadata and reduce gas costs. It allows batch score and game_over queries to validate multiple provable game sessions efficiently.