Gotchi Equip
Analysis
The skill is coherent and does what it says, but it can submit Bankr transactions that change Aavegotchi wearable state and uses a Bankr API key.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
echo "Submitting transaction via Bankr..." RESPONSE="$(curl -sS -X POST "https://api.bankr.bot/agent/submit" ... -d @"$TEMP_TX")"
The equip flow submits a prepared transaction to Bankr, which is expected for this skill but can change on-chain Aavegotchi wearable state once run.
echo "Action: Unequip all wearables" ... RESPONSE="$(curl -sS -X POST "https://api.bankr.bot/agent/submit" ... -d @"$TEMP_TX")"
The unequip-all script is clearly named and documented, but it submits a transaction that sets all wearable slots to zero.
npm install
The skill requires installing npm dependencies before use; this is expected because the code uses viem to encode transaction calldata, and a package-lock file is included.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
key="${BANKR_API_KEY:-}" ... systemctl --user show-environment ... "$HOME/.openclaw/skills/bankr/config.json" ... "$HOME/.openclaw/workspace/skills/bankr/config.json"The skill retrieves a Bankr API key from documented environment and OpenClaw Bankr config locations so it can submit transactions.
