Skills 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.
install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/abstrct/structs-power" ~/.claude/skills/clawdbot-skills-structs-power && rm -rf "$T"
manifest:
skills/abstrct/structs-power/SKILL.mdsource content
Structs Power
Important: Entity IDs containing dashes (like
3-1, 4-5) are misinterpreted as flags by the CLI parser. All transaction commands in this skill use -- before positional arguments to prevent this.
Procedure
- Assess power state — Query player:
. Compute:structsd query structs player [id]
. IfavailablePower = (capacity + capacitySecondary) - (load + structsLoad)
, player goes OFFLINE (cannot act). Player passive draw: 25,000 mW.load + structsLoad > capacity + capacitySecondary - Create substation — First create allocation from reactor/generator:
. Thestructsd tx structs allocation-create --allocation-type static|dynamic|automated|provider-agreement TX_FLAGS -- [source-id] [power]
flag accepts a PlayerId (e.g.,--controller
). If omitted, the creating player is the default controller. Then:1-42
.structsd tx structs substation-create TX_FLAGS -- [owner-id] [allocation-id] - Connect power —
to add source.structsd tx structs substation-allocation-connect -- [substation-id] [allocation-id]
to remove.structsd tx structs substation-allocation-disconnect -- [substation-id] [allocation-id] - Connect players —
to draw power.structsd tx structs substation-player-connect -- [substation-id] [player-id]
to remove.structsd tx structs substation-player-disconnect -- [substation-id] [player-id] - Migrate players —
.structsd tx structs substation-player-migrate TX_FLAGS -- [source-substation-id] [dest-substation-id] [player-id,player-id2,...] - Manage allocations — Update:
. Delete:structsd tx structs allocation-update -- [allocation-id] [new-power]
.structsd tx structs allocation-delete -- [allocation-id] - Delete substation —
(disconnect allocations/players first).structsd tx structs substation-delete -- [substation-id]
Commands Reference
| Action | Command |
|---|---|
| Substation create | |
| Substation delete | |
| Allocation connect | |
| Allocation disconnect | |
| Player connect | |
| Player disconnect | |
| Player migrate | |
| Allocation create | |
| Allocation update | |
| Allocation delete | |
TX_FLAGS:
--from [key-name] --gas auto --gas-adjustment 1.5 -y
Verification
- Player:
—structsd query structs player [id]
,capacity
,capacitySecondary
,load
, online status.structsLoad - Substation:
— connected allocations, players.structsd query structs substation [id] - Allocations:
,structsd query structs allocation-all-by-source [source-id]
— power flow.allocation-all-by-destination [dest-id]
How to Increase Capacity
If capacity is too low (or you're going offline), there are three paths:
| Method | Requires | Speed | Risk | Rate |
|---|---|---|---|---|
| Reactor infusion | Alpha Matter | Immediate | Low | 1g ≈ 1 kW (minus commission) |
| Generator infusion | Alpha Matter + generator struct | Immediate | High (irreversible, raidable) | 1g = 2-10 kW |
| Buy via agreement | A provider with capacity | Immediate | Medium (ongoing cost) | Varies by provider |
Most common: Infuse Alpha Matter into your guild's reactor. Capacity increases automatically.
For step-by-step workflows, see the structs-energy skill.
Error Handling
- Going offline: Load exceeds capacity. Deactivate structs immediately (
), then increase capacity — see thestruct-deactivate
skill for options.structs-energy - Allocation exceeds source: Source (reactor/provider) has limited capacity. Query source; create smaller allocation or add capacity.
- Substation delete failed: Ensure no players or allocations connected. Disconnect first.
- Automated allocation limit: One automated allocation per source. Attempting a second from the same source will error. Use static/dynamic for multiple.
- capacity=0 false positive: A player connected to a substation pool may show
while structs are online and drawing power. Checkcapacity=0
as the real indicator of functionality, notstructsLoad > 0
.capacity > 0
See Also
- structs-energy skill — "I need more energy" decision tree and workflows
- knowledge/mechanics/power — Formulas, capacity, load, online status
- knowledge/mechanics/building — Build power requirements
- knowledge/mechanics/resources — Reactor vs generator conversion rates