structs-economy
Manages economic operations in Structs. Covers reactor staking, energy providers, agreements, allocations, generator infusion, and token transfers. Use when staking Alpha Matter in reactors, creating or managing energy providers, negotiating agreements, allocating energy, infusing generators, transferring tokens, or managing economic infrastructure.
Best use case
structs-economy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manages economic operations in Structs. Covers reactor staking, energy providers, agreements, allocations, generator infusion, and token transfers. Use when staking Alpha Matter in reactors, creating or managing energy providers, negotiating agreements, allocating energy, infusing generators, transferring tokens, or managing economic infrastructure.
Teams using structs-economy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/structs-economy/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How structs-economy Compares
| Feature / Agent | structs-economy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manages economic operations in Structs. Covers reactor staking, energy providers, agreements, allocations, generator infusion, and token transfers. Use when staking Alpha Matter in reactors, creating or managing energy providers, negotiating agreements, allocating energy, infusing generators, transferring tokens, or managing economic infrastructure.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# Structs Economy ## Procedure 1. **Assess position** — Query player, reactor, provider, agreement state via `structsd query structs player/reactor/provider/agreement [id]`. 2. **Reactor staking** — Stake Alpha Matter: `structsd tx structs reactor-infuse [player-address] [reactor-address] [amount] TX_FLAGS`. The `amount` **must include the denomination**, e.g. `60000000ualpha` (not just `60000000`). This **automatically increases the player's capacity** — no allocation setup needed. The reactor's commission rate determines the split: player receives `power * (1 - commission)`, reactor keeps the rest. Unstake: `reactor-defuse [reactor-id]` (cooldown applies). Cancel cooldown: `reactor-cancel-defusion [reactor-id]`. Migrate: `reactor-begin-migration [player-address] [source-validator-address] [dest-validator-address] [amount]`. 3. **Generator infusion** — `structsd tx structs struct-generator-infuse [struct-id] [amount] TX_FLAGS`. **IRREVERSIBLE** — Alpha cannot be recovered. Higher conversion rates than reactors (2-10x) but generator is vulnerable to raids. 4. **Provider lifecycle** — Create: `provider-create [substation-id] [rate] [access-policy] [provider-penalty] [consumer-penalty] [cap-min] [cap-max] [dur-min] [dur-max] TX_FLAGS`. Valid `access-policy` values: `open-market` (anyone can buy), `guild-market` (guild members with sufficient rank can buy -- managed via guild rank permissions on the provider), `closed-market` (only players with explicit PermProviderOpen on the provider). Update capacity/duration/access via `provider-update-capacity-maximum`, `provider-update-duration-minimum`, etc. Delete: `provider-delete [provider-id]`. Withdraw earnings: `provider-withdraw-balance [provider-id]`. To grant guild members access to a `guild-market` provider: `permission-guild-rank-set [provider-id] [guild-id] 262144 [rank]` (PermProviderOpen). 5. **Agreements** — Open: `agreement-open [provider-id] [duration] [capacity] TX_FLAGS`. Close: `agreement-close [agreement-id]`. Adjust: `agreement-capacity-increase/decrease`, `agreement-duration-increase`. 6. **Allocations** — Create: `allocation-create [source-id] [power] --allocation-type static|dynamic|automated TX_FLAGS`. The `--controller` flag accepts a **PlayerId** (e.g., `1-42`). If omitted, the creating player is the default controller. Update: `allocation-update [allocation-id] [new-power]`. Delete: `allocation-delete [allocation-id]` — only the controlling player can delete an allocation. Transfer: `allocation-transfer [allocation-id] [new-controller]`. ### Allocation Type Comparison | Type | Updatable | Deletable | Auto-grows | Limit | Use Case | |------|-----------|-----------|------------|-------|----------| | `static` | No | No (while connected) | No | Unlimited | Fixed capacity routing | | `dynamic` | Yes | Yes | No | Unlimited | Flexible, managed routing | | `automated` | Yes | No | Yes (scales with source capacity) | One per source | Energy commerce (recommended) | | `provider-agreement` | System-managed | System-managed | System-managed | System-created | Auto-created when agreements open; never create manually | **Automated allocation limit**: Only one automated allocation per source is allowed. Attempting to create a second from the same source will error. Use `dynamic` type if you need multiple allocations from one source. **Recommended for energy sales**: Use `automated` allocations. When you infuse more alpha into a reactor, your capacity grows, and automated allocations proportionally increase energy flowing to your substations with no manual intervention. 7. **Token transfer** — `player-send [from-address] [to-address] [amount] TX_FLAGS`. ## Commands Reference | Action | Command | |--------|---------| | Reactor infuse | `structsd tx structs reactor-infuse [player-addr] [validator-addr] [amount]` (validator = `structsvaloper1...`, NOT reactor ID) | | Reactor defuse | `structsd tx structs reactor-defuse [reactor-id]` | | Reactor migrate | `structsd tx structs reactor-begin-migration [player-addr] [src-validator-addr] [dest-validator-addr] [amount]` | | Reactor cancel defusion | `structsd tx structs reactor-cancel-defusion [reactor-id]` | | Generator infuse | `structsd tx structs struct-generator-infuse [struct-id] [amount]` | | Provider create | `structsd tx structs provider-create [substation-id] [rate] [access] [prov-penalty] [cons-penalty] [cap-min] [cap-max] [dur-min] [dur-max]` | | Provider delete | `structsd tx structs provider-delete [provider-id]` | | Provider withdraw | `structsd tx structs provider-withdraw-balance [provider-id]` | | Agreement open | `structsd tx structs agreement-open [provider-id] [duration] [capacity]` | | Agreement close | `structsd tx structs agreement-close [agreement-id]` | | Allocation create | `structsd tx structs allocation-create [source-id] [power] --allocation-type [type]` | | Allocation update | `structsd tx structs allocation-update [allocation-id] [power]` | | Allocation delete | `structsd tx structs allocation-delete [allocation-id]` | | Player send | `structsd tx structs player-send [from] [to] [amount]` | **TX_FLAGS**: `--from [key-name] --gas auto --gas-adjustment 1.5 -y` **Important**: Entity IDs containing dashes (like `3-1`, `4-5`) are misinterpreted as flags by the CLI parser. Always place `--` between flags and positional args: `structsd tx structs command TX_FLAGS -- [entity-id] [other-args]` ## Verification - **Reactor**: `structsd query structs reactor [id]` — check `infusedAmount`, `defusionCooldown`. - **Provider**: `structsd query structs provider [id]` — verify capacity, rate, active agreements. - **Agreement**: `structsd query structs agreement [id]` — check status, capacity, duration. - **Allocation**: `structsd query structs allocation [id]` — confirm power, source, destination. - **Player balance**: `structsd query structs player [id]` — verify Alpha Matter after transfers. ## Error Handling - **Insufficient balance**: Check player Alpha Matter before infuse/send. Refine ore first. - **Provider capacity exceeded**: Query provider `capacityMaximum`; reduce agreement capacity or create new provider. - **Defusion cooldown**: Use `reactor-cancel-defusion` to re-stake during cooldown, or wait. - **Generator infuse failed**: Cannot undo. Verify struct is a generator type and amount is correct before submitting. ## See Also - [structs-energy skill](https://structs.ai/skills/structs-energy/SKILL) — "I need more energy" decision tree and workflows - [knowledge/economy/energy-market](https://structs.ai/knowledge/economy/energy-market) — Provider/agreement flow, pricing - [knowledge/economy/guild-banking](https://structs.ai/knowledge/economy/guild-banking) — Central Bank tokens - [knowledge/mechanics/resources](https://structs.ai/knowledge/mechanics/resources) — Alpha Matter, conversion rates - [knowledge/mechanics/power](https://structs.ai/knowledge/mechanics/power) — Capacity, load, online status
Related Skills
zhua-economy
爪爪自主经济系统 —— 技能变现、任务定价、收益分配、经济自治。Use when 爪爪需要建立经济系统、技能变现、或实现经济自主。
structsd-install
Installs the structsd binary from source. Covers Go, Ignite CLI, and building structsd for Linux and macOS. Use when structsd is not found, when setting up a new machine, or when the agent needs to install or update the Structs chain binary.
structs-streaming
Connects to the GRASS real-time event system via NATS WebSocket. Use when you need real-time game updates, want to react to events as they happen, need to monitor raids or attacks, watch for player creation, track fleet movements, or build event-driven tools. GRASS is the fastest way to know what's happening in the galaxy.
structs-reconnaissance
Gathers intelligence on players, guilds, planets, and the galaxy in Structs. Use when scouting enemy players, checking planet defenses, monitoring fleet movements, assessing guild strength, surveying the galaxy map, gathering intel before combat or raids, or updating competitive intelligence. Persists findings to memory/intel/.
structs-power
Manages power infrastructure in Structs. Covers substations, allocations, player connections, and power monitoring. Use when power is low or overloaded, creating or managing substations, connecting players to substations, allocating capacity, diagnosing offline status, or planning power budget for new structs.
structs-onboarding
Onboards a new player into Structs. Handles key creation/recovery, player creation (via reactor-infuse or guild signup), planet exploration, and initial infrastructure builds. Use when starting fresh, setting up a new agent, creating a player, claiming first planet, or building initial infrastructure. Build times range from ~17 min (Command Ship) to ~57 min (Ore Extractor/Refinery).
structs-mining
Executes resource extraction in Structs. Mines ore and refines it into Alpha Matter. Use when mining ore, refining ore, starting a mine-refine cycle, checking planet ore levels, or managing resource extraction. Mining takes ~17 hours and refining ~34 hours — both are background operations. Ore is stealable until refined.
structs-guild
Manages guild operations in Structs. Covers creation, membership, settings, and Central Bank token operations. Use when creating a guild, joining or leaving a guild, managing guild settings, minting or redeeming guild tokens, managing Central Bank collateral, or coordinating guild membership.
structs-guild-stack
Deploys the Guild Stack (Docker Compose) for local PostgreSQL access to game state. Use when you need faster queries for combat automation, real-time threat detection, raid target scouting, fleet composition analysis, or galaxy-wide intelligence. Advanced/optional -- CLI works for basic gameplay, but PG access transforms what is possible.
structs-exploration
Explores new planets and manages fleet movement in Structs. Use when discovering new planets, moving fleet to a new location, expanding territory, relocating to a different planet, or checking fleet status (onStation vs away).
structs-energy
Manages energy capacity in Structs. Covers increasing capacity (reactor infusion, generator infusion, buying agreements), selling surplus energy (creating providers), and diagnosing power problems. Use when capacity is too low, going offline, need more power for new structs, want to sell energy, or asking "how do I get more energy?"
structs-diplomacy
Handles permissions, address management, and inter-player coordination in Structs. Use when granting or revoking permissions on objects, registering new addresses, managing multi-address accounts, delegating authority to other players, or setting up address-level access control.