Structs Power
ReviewAudited by ClawScan on May 14, 2026.
Overview
This instruction-only skill is aligned with managing Structs power, but it can guide signed transactions that may disconnect players or alter/delete power infrastructure.
Use this skill only if you recognize Structs and have a trusted structsd setup. Run transactions interactively, verify IDs and amounts carefully, avoid `-y` unless the exact action is approved, and expect that delete/disconnect/migrate actions can affect other players.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken allocation or substation change could knock multiple players or structures offline.
The skill explicitly discloses that some power-management actions can propagate to downstream substations and players. This is expected for the stated purpose, but it is high-impact.
Power operations cascade. Deleting an allocation can take an entire substation's worth of players offline.
Use the interactive transaction prompts, verify every ID and power amount, and get explicit approval before deletes, disconnects, or migrations.
Using -y too casually could execute a transaction without the normal last-chance confirmation.
The skill documents an option that suppresses CLI confirmation prompts. It is framed with an approval requirement and is therefore a note rather than a concern.
TX_FLAGS_APPROVED (only after commander approval; suppresses the prompt): TX_FLAGS plus `-y`.
Do not use prompt-suppression unless the user has clearly approved the exact transaction and its target IDs.
Transactions may be signed as the configured account and can change that account's Structs power infrastructure.
Structs transactions require a configured signing key, meaning commands may act with the user's account authority. This is expected for the integration and no credential leakage is shown.
**Requires**: [`structsd`](https://structs.ai/skills/structsd-install/SKILL) on PATH and a configured signing key.
Confirm the `--from` key name before running transactions and use the least-privileged or intended signing key where possible.
Users must rely on their separately installed structsd binary and local key configuration.
The package has limited provenance information and relies on an external CLI setup rather than bundled code. No hidden installer or script is present, so this is a provenance/setup note.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Install structsd only from a trusted Structs source and verify the skill/version before using it for signed transactions.