Structs Combat
ReviewAudited by ClawScan on May 14, 2026.
Overview
The visible artifacts are coherent for a Structs combat helper, but using it can sign real Structs transactions, spend gas, and run a long raid job, so confirm targets and keys carefully.
Use this only if you intend to let the agent help with Structs combat transactions. Verify the structsd binary and signing key, confirm every target and guild boundary, avoid -y except for the documented raid approval flow, and monitor any background raid compute until it finishes.
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.
Wrong IDs, wrong weapon choices, or premature approval could attack the wrong target, spend gas, change account state, or trigger in-game retaliation.
The skill provides CLI transaction commands for attacks and raids, including a raid command that suppresses confirmation with -y after an approval block.
`structsd tx structs struct-attack ...`; `structsd tx structs planet-raid-compute -D 3 --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [fleet-id]`
Verify target IDs, guild boundaries, weapon selection, and gas implications before allowing any transaction; use -y only where the skill’s approval block has been satisfied.
A configured key can authorize account-mutating actions and gas spending if the user confirms the transaction or allows the approved -y flow.
The skill depends on a local signing key via structsd so it can authorize transactions for the selected account.
**Requires**: [`structsd`](https://structs.ai/skills/structsd-install/SKILL) on PATH and a configured signing key.
Use a dedicated, low-value Structs key where possible, confirm the `--from` key name before transactions, and avoid exposing keys beyond the Structs CLI.
A raid may complete after circumstances change, while a fleet is locked away, potentially causing loss or retaliation.
The raid flow intentionally starts a long-running background operation that can submit a transaction later.
Launch raid compute in a background terminal — it may take minutes to hours depending on difficulty. Use `-D 3` for zero wasted CPU. Compute auto-submits the complete transaction.
Start raid compute only when you can track it, record active jobs, and review the reconnect/async flow before launching new actions.
If the local structsd binary or signing-key setup is not trusted, it could affect all transactions run through this skill.
The registry metadata lists no required binaries or install spec, but the skill requires an external CLI installed separately. This is expected for an instruction-only Structs skill, but the CLI itself is outside the reviewed package.
**Requires**: [`structsd`](https://structs.ai/skills/structsd-install/SKILL) on PATH and a configured signing key.
Install structsd only from the official Structs source, verify the version, and treat the local CLI/key configuration as part of the trust boundary.