Structs Building
ReviewAudited by ClawScan on May 14, 2026.
Overview
This instruction-only Structs skill openly guides wallet-backed game transactions and long-running build jobs; the risks are expected account/resource changes rather than hidden code.
Before installing, make sure you trust your `structsd` installation and only run commands against the intended key/account. Treat build, compute, move, defense, stealth, and infusion commands as real transactions: confirm costs, target IDs, slots, and timing, and be especially careful with irreversible generator infusion or background jobs that auto-complete later.
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.
If used incorrectly, the agent could help submit transactions that consume resources or change the user's Structs assets.
The skill includes high-impact Structs actions that can irreversibly consume resources. This is purpose-aligned and explicitly disclosed, with escalation guidance.
`struct-generator-infuse` (Tier 2 — irreversible) — "Alpha Matter is annihilated in the conversion... There is no defusion."
Review every transaction prompt, especially irreversible infusion or long-build actions, and require explicit user approval before submitting.
The configured signing key determines which account the agent can act on when the user runs these commands.
The commands use a local key name to sign Structs transactions and spend gas/resources. This is expected for the stated purpose, and there is no evidence of credential exfiltration.
structsd tx structs struct-build-initiate --from [key-name] --gas auto --gas-adjustment 1.5 -- [player-id] ...
Use a dedicated or limited Structs key where possible, confirm the `--from` key before each transaction, and do not expose broader wallet credentials.
A build job may complete and change game state hours after launch, even if circumstances have changed.
The skill tells users to launch long-running background compute jobs that later auto-submit and auto-activate. This persistence is disclosed and tied to the build workflow.
"The build hashes for up to ~6.4 hours and auto-activates on completion." Log the PID to `memory/jobs/`; recall with `kill <pid>` if needed.
Launch background compute only after explicit approval, keep the PID, cancel jobs when needed, and avoid leaving stale jobs running.
Users must already have a trustworthy `structsd` binary and account configuration installed for these instructions to work safely.
The skill relies on the external `structsd` CLI, while the supplied requirements declare no required binaries. This is a documentation/provenance gap for setup, not hidden code in the skill.
structsd tx structs struct-build-compute -D 3 --from [key-name] --gas auto --gas-adjustment 1.5 -y -- [struct-id]
Install `structsd` only from official Structs sources and verify the binary/account setup before letting the agent suggest transactions.