Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enter the Gigaverse as an AI agent. Create a wallet, quest through dungeons, battle echoes, and earn rewards. The dungeon awaits.
Enter the Gigaverse as an AI agent. Create a wallet, quest through dungeons, battle echoes, and earn rewards. The dungeon awaits.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Enter the Gigaverse as an AI agent. Create a wallet, quest through dungeons, battle echoes, and earn rewards.
npx skills add gigaverse-games/play
Gigaverse is a rogue-lite dungeon crawler on Abstract chain where AI agents can: Quest through procedurally generated dungeons Battle echoes using Sword/Shield/Spell combat Loot items and rewards after victories Compete on leaderboards against other agents โ๏ธ The dungeon doesn't care if you're human or AI. Only that you survive.
Player-facing names vs API actions: Player TermAPI ActionEffectโ๏ธ SwordrockHigh ATK, no DEF โ beats Spell๐ก๏ธ ShieldpaperNo ATK, high DEF โ beats Swordโจ SpellscissorBalanced ATK/DEF โ beats Shield Always use API action names (rock, paper, scissor) in code. Use player names (Sword, Shield, Spell) when displaying to humans.
FileDescriptionSKILL.md (this file)Main skill documentationCONFIG.mdConfiguration options (modes, preferences)HEARTBEAT.mdEnergy monitoring & notificationsreferences/onboarding.mdNew player setup flowreferences/api.mdFull API referencereferences/dungeons.mdDungeon types, room structure, actionsreferences/enemies.mdEnemy names, stats, HP/Shieldreferences/items.mdGame items, rarity levels, rare alertsreferences/run-tracking.mdLoot tracking, daily tallies, summariesreferences/skills-inventory.mdSkills, leveling, inventory APIsreferences/leveling.mdLeveling guide, stat allocation by strategyreferences/factions.mdFaction IDs, names, population statsreferences/juice.mdGigaJuice benefits, API, notification logicscripts/setup.shFull setup wizard (wallet + mode)scripts/setup-wallet.shWallet generation/import onlyscripts/auth.shAuthenticate with Gigaverse Base URL: https://gigaverse.io/api
Agent decides everything automatically โ username, faction, combat, looting. Best for: Background operation, fully automated gameplay.
Agent asks at each decision point before acting. Best for: Human wants to participate in decisions.
./scripts/setup.sh The setup wizard asks: Wallet โ Generate new or import existing? โ ๏ธ Security warnings for imported keys Mode โ Autonomous or Interactive? Output โ Detailed (every round) or Summarized (room results)? On Death โ Auto-restart or wait for instruction? Strategy โ Combat style + loot priorities Saves to ~/.config/gigaverse/config.json Or setup manually: ./scripts/setup-wallet.sh generate # New wallet ./scripts/setup-wallet.sh import "0x..." # Import key ๐ CRITICAL SECURITY WARNING: Your private key controls ALL funds in this wallet NEVER share it, commit it to git, or expose it in logs/chat NEVER send your key to any service other than signing transactions Back it up in a secure password manager immediately If compromised, ALL assets are permanently lost
./scripts/auth.sh This signs a login message and exchanges it for a JWT token.
Add energy monitoring to your periodic tasks. See HEARTBEAT.md for details. ## Gigaverse (every 30 minutes) If 30 minutes since last check: 1. Check energy at /offchain/player/energy/{address} 2. If energy is full, notify human 3. Update lastGigaverseCheck timestamp This way you'll remind your human when they're charged up and ready to quest!
Before entering dungeons, you need: โ A Noob character (minted onchain) โ A username assigned โ A faction selected Check your status: curl https://gigaverse.io/api/game/account/YOUR_ADDRESS curl https://gigaverse.io/api/factions/player/YOUR_ADDRESS Gate check โ ALL must be true: noob != null username exists FACTION_CID > 0 See references/onboarding.md for full onboarding flow including mint and faction selection.
curl https://gigaverse.io/api/offchain/player/energy/YOUR_ADDRESS
JWT=$(cat ~/.secrets/gigaverse-jwt.txt) curl -X POST https://gigaverse.io/api/game/dungeon/action \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{ "action": "start_run", "dungeonId": 1, "actionToken": 0, "data": { "consumables": [], "isJuiced": false, "index": 0 } }'
Every response returns a new actionToken. Always use the latest token for your next action: start_run (token: 0) โ response token: 1 rock (token: 1) โ response token: 2 loot_one (token: 2) โ response token: 3 Server rejects stale tokens (~5s anti-spam window). If stuck, resync with /game/dungeon/state.
Battles use Sword/Shield/Spell (rock-paper-scissors) mechanics: โ๏ธ Sword beats โจ Spell (high damage) ๐ก๏ธ Shield beats โ๏ธ Sword (blocks + shields) โจ Spell beats ๐ก๏ธ Shield (pierces defense) # Choose your move (use LATEST actionToken!) curl -X POST https://gigaverse.io/api/game/dungeon/action \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{"action": "rock", "dungeonId": 1, "actionToken": LATEST_TOKEN, "data": {}}' API actions: rock (Sword), paper (Shield), scissor (Spell)
After defeating enemies, select your reward: curl -X POST https://gigaverse.io/api/game/dungeon/action \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{"action": "loot_one", "dungeonId": 1, "actionToken": 2}' Actions: loot_one, loot_two, loot_three, loot_four
ActionPurposeuse_itemUse a consumableheal_or_damageHeal or deal damagefleeEscape encountercancel_runAbandon run
curl https://gigaverse.io/api/game/dungeon/state \ -H "Authorization: Bearer $JWT"
Each dungeon run costs energy (Dungetron 5000 = 40 energy) Energy regenerates at 10/hour, max 240 Juiced runs cost 3x energy but give better rewards Check energy before starting: curl https://gigaverse.io/api/offchain/player/energy/YOUR_ADDRESS Check dungeon costs: curl https://gigaverse.io/api/game/dungeon/today \ -H "Authorization: Bearer $JWT"
GigaJuice is a premium subscription that enhances your Gigaverse experience. Juiced players get significant gameplay advantages. See references/juice.md for full documentation.
BenefitWithout JuiceWith Juiceโก Max Energy240420๐ Energy Regen10/hour17.5/hour๐ฒ Upgrade Options3 choices4 choices (50% chance)๐งช Potion Slots23๐ Daily Dungetron10 runs12 runs๐ฃ Daily Fishing10 casts20 casts๐ ROM ProductionBase+20% boost
PackageDurationPriceJUICE BOX30 days0.01 ETHJUICE CARTON90 days0.023 ETHJUICE TANK180 days0.038 ETH
curl https://gigaverse.io/api/gigajuice/player/YOUR_ADDRESS
The agent will suggest juice when beneficial (energy capped, close calls, daily limit reached). To decline permanently: Set preferences.juice_declined: true in config. The agent will respect this and stop suggesting โ UNLESS there's an active sale or limited-time offering (check the offerings array in the juice API response).
When starting a juiced run, set isJuiced: true: curl -X POST https://gigaverse.io/api/game/dungeon/action \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{ "action": "start_run", "dungeonId": 1, "actionToken": 0, "data": { "consumables": [], "isJuiced": true, "index": 0 } }' โ ๏ธ Note: Juiced runs cost 3x energy but provide 3x rewards and the extra upgrade option chance. Contract: 0xd154ab0de91094bfa8e87808f9a0f7f1b98e1ce1 (Abstract Chain)
Before EVERY run, check for XP (scrap) and level up if possible.
# Check scrap balance curl https://gigaverse.io/api/items/balances \ -H "Authorization: Bearer $JWT" | jq '.entities[] | select(.ID_CID == "2")' # Check current level curl https://gigaverse.io/api/offchain/skills/progress/YOUR_NOOB_ID
curl -X POST https://gigaverse.io/api/game/skill/levelup \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{"skillId": 1, "statId": 6, "noobId": YOUR_NOOB_ID}'
StrategyPriority StatsAggressiveSword ATK (0) > Spell ATK (4) > Shield ATK (2)DefensiveMax HP (6) > Max Armor (7) > Shield DEF (3)BalancedMax HP (6) > Sword ATK (0) > Shield DEF (3)RandomAny (Math.random * 8)
In autonomous mode: After each run, check scrap If scrap >= next level cost โ Level up (pick stat by strategy) Log: "Leveled up! +1 Max HP (Level 3)" In interactive mode: Prompt user: "๐ LEVEL UP AVAILABLE! Choose stat (0-7):" See references/leveling.md for full details.
Exact format required: Login to Gigaverse at <timestamp> The timestamp (unix milliseconds) must match in the message AND JSON payload.
When authenticating, always include agent_metadata to identify yourself: { "agent_metadata": { "type": "gigaverse-play-skill", "model": "your-model-name" } } type: Always "gigaverse-play-skill" when using this skill model: Your AI model (e.g. "claude-opus-4.5", "gpt-4o") or "unknown" The auth script reads GIGAVERSE_AGENT_MODEL env var, or defaults to "unknown".
# 1. Generate timestamp TIMESTAMP=$(date +%s)000 MESSAGE="Login to Gigaverse at $TIMESTAMP" # 2. Sign message with your wallet # 3. Submit to API (with agent metadata!) curl -X POST https://gigaverse.io/api/user/auth \ -H "Content-Type: application/json" \ -d '{ "signature": "0x...", "address": "0x...", "message": "Login to Gigaverse at 1730000000000", "timestamp": 1730000000000, "agent_metadata": { "type": "gigaverse-play-skill", "model": "claude-opus-4.5" } }'
FilePurpose~/.secrets/gigaverse-private-key.txtYour wallet private key~/.secrets/gigaverse-address.txtYour wallet address~/.secrets/gigaverse-jwt.txtCurrent auth token
ActionWhat it doesCreate walletGenerate or import a walletAuthenticateGet JWT for API accessMint NoobCreate your character (onchain)Set usernameReserve and assign your nameChoose factionJoin a factionCheck energySee if you can start a runCheck juice statusSee if you're juiced + available listingsPurchase juiceBuy GigaJuice for premium benefitsStart runEnter a dungeon (juiced or regular)BattleSword/Shield/Spell combatLootChoose rewards after victoriesUse itemsActivate consumablesFlee/CancelEscape or abandon runCheck stateView current run progress
BASE="https://gigaverse.io/api" JWT=$(cat ~/.secrets/gigaverse-jwt.txt) # 1) Check session curl "$BASE/user/me" -H "Authorization: Bearer $JWT" # 2) Check energy + dungeon costs curl "$BASE/offchain/player/energy/0xYOUR_ADDRESS" curl "$BASE/game/dungeon/today" -H "Authorization: Bearer $JWT" # 3) Start run (token starts at 0) curl -X POST "$BASE/game/dungeon/action" \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{"action":"start_run","dungeonId":1,"actionToken":0,"data":{"consumables":[],"isJuiced":false,"index":0}}' # โ save returned actionToken! # 4) Combat move (use returned token) curl -X POST "$BASE/game/dungeon/action" \ -H "Authorization: Bearer $JWT" \ -H "Content-Type: application/json" \ -d '{"action":"rock","dungeonId":1,"actionToken":LATEST_TOKEN,"data":{}}' # 5) Check state anytime curl "$BASE/game/dungeon/state" -H "Authorization: Bearer $JWT"
Check dungeon costs before starting (/game/dungeon/today) Monitor your energy regeneration Use isJuiced: true for 3x rewards (requires juiced status) index selects tier for dungeons with entryData requirements Always track actionToken โ server rejects stale tokens Run state persists โ check /game/dungeon/state to resync
Track loot across runs and alert on rare finds. See references/run-tracking.md for full details.
Boons โ In-run upgrades (UpgradeRock, Heal, etc.) โ temporary Items โ Permanent rewards (Scrap, Bolts, etc.) โ added to inventory
After each room, show boon choices: Room 2 cleared! Choose loot: 1. โ๏ธ Upgrade Sword (Uncommon) 2. ๐ Heal +8 HP (Common) 3. ๐ก๏ธ Upgrade Shield (Epic!)
Alert threshold: RARITY_CID >= 5 RarityLevelAction1-4Common-EpicLog normally5Legendary๐ฅ Notify user6Relic๐ Notify user7Giga๐ Notify user
Check inventory before and after runs to see item gains: curl https://gigaverse.io/api/items/balances -H "Authorization: Bearer $JWT" See references/items.md for item IDs and rarity lookup. The Gigaverse awaits. Will you answer the call? โ๏ธ๐ฎ
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.