Snakey
Analysis
This skill is a disclosed USDC prize game, but it asks for a wallet private key and provides one-command flows that can spend funds to enter games.
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.
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.
`snakey join` | Join next game ($3 USDC) ... `const result = await client.play('MyBot');` ... `// Play a game (handles payment, waiting, everything)`The skill exposes simple CLI/SDK paths that can initiate a paid USDC game entry and handle the payment automatically, but the artifact does not describe explicit approval prompts, spend caps, or containment for repeated paid actions.
`"install": [ { "type": "npm", "package": "@snakey/sdk", "global": false } ]` and `SDK: npm install @snakey/sdk`The skill depends on an external npm package to perform the wallet/game actions. That dependency is expected for the stated SDK-based purpose, but the artifact does not pin a version or include the package contents.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
`privateKey: process.env.WALLET_PRIVATE_KEY` ... `Mainnet: ... Private key for signing x402 payments`
The skill requires direct access to a wallet private key for payment signing. A raw wallet private key can authorize broader wallet activity than just a single game entry unless the user strictly isolates the wallet.
