structs-onboarding_skill

Overview

This skill onboards a new player into Structs and automates the first setup tasks. It guides key creation or recovery, player creation (via reactor-infuse or guild signup), first planet exploration, and initial infrastructure builds like Command Ship, Ore Extractor, and Refinery. It is designed for starting fresh or provisioning a new agent quickly and reproducibly.

How this skill works

The skill sequences CLI and helper-script operations: manage local keys, detect or create a player record, and either delegate to a reactor or run a guild signup script to create the player. After player creation it issues planet-explore and orchestrates struct build flows using build-initiate and build-compute commands, respecting charge, ambits, and proof-of-work difficulty. The bundled create-player script handles mnemonic generation, signing, guild POST, and polling to confirm player creation.

When to use it

• Starting a fresh Structs agent or human-controlled player
• Migrating or recovering an identity and adding it to local keyring
• Creating a player without existing $alpha via a guild signup
• Claiming and exploring your first planet after player creation
• Bootstrapping core infrastructure: Command Ship, Ore Extractor, and Refinery

Best practices

• Never overwrite existing personal identity files; merge new identity entries instead
• Store mnemonics securely (env var, .env excluded from git, or secret store) and avoid printing them to logs
• Always include -- before positional entity IDs when running structsd tx commands to avoid CLI flag parsing issues
• Initiate all planned builds early and use struct-build-compute -D 3 to minimize wasted CPU and complete quickly
• Never run two concurrent build-compute jobs with the same signing key to avoid sequence conflicts

Example use cases

• Agent provisioning: create key, run reactor-infuse if you hold $alpha, then explore and build a Command Ship
• Guild signup: use the create-player script to generate a mnemonic, sign proxy, POST to guild API, and poll until player exists
• Fresh human user: recover mnemonic into local keyring, query address, run planet-explore, then initiate and compute builds
• Asynchronous onboarding: kick off build-initiate for multiple structs and run compute jobs in background terminals, returning later to verify completion