Aavegotchi Baazaar
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for Aavegotchi marketplace use, but it can use a wallet private key to broadcast irreversible Base transactions, so users should keep dry-run and explicit confirmation safeguards in place.
Before installing, treat this as a real-wallet transaction skill: use a limited wallet, keep DRY_RUN enabled until you have reviewed the exact transaction, require explicit confirmation before any cast send, verify Base chain ID 8453 and the from address, and revoke approvals you no longer need.
Findings (3)
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 the private key is exposed or misused, funds or NFTs in the wallet could be lost.
The skill requires a wallet private key to sign transactions. This is expected for on-chain buying/listing, but it gives the skill high-impact authority over the funded wallet.
`PRIVATE_KEY`: EOA private key used for `cast send` (never print/log).
Use a dedicated low-balance wallet, never paste the private key into chat, keep it only in the environment, and verify every transaction before broadcasting.
Approvals and transactions can authorize token/NFT movement or spend real funds on-chain.
The skill documents broadcast-capable commands, including NFT operator approvals. The instructions say these should only be done when explicitly instructed, making this purpose-aligned but high-impact.
Set approval (broadcast; do this only when explicitly instructed): `~/.foundry/bin/cast send "<NFT_CONTRACT_ADDRESS>" 'setApprovalForAll(address,bool)' "$DIAMOND" true ... --private-key "$PRIVATE_KEY"`
Only approve exact intended assets and amounts where possible, review the transaction summary, and revoke unnecessary approvals after use.
Local commands run in the user's environment, so mistakes or unsafe substitutions could have local or financial impact.
The skill relies on local shell commands and inline Python snippets. The artifact includes explicit restrictions and validation guidance, so this appears expected and controlled.
This skill includes shell commands... Never execute user-provided strings as shell code (avoid `eval`, `bash -c`, `sh -c`).
Run commands only from the documented templates, validate all addresses and numeric values, and avoid modifying the shell snippets unless you understand the effects.