ClawQuests
WarnAudited by ClawScan on May 10, 2026.
Overview
ClawQuests is explicit about being an on-chain bounty skill, but it gives an agent raw command templates that use a wallet private key to approve and move USDC, so users should review it carefully before enabling.
Install only if you are comfortable letting an agent prepare on-chain transactions for a funded wallet. Use a dedicated low-balance wallet, verify all contract addresses and USDC amounts, keep allowances minimal, and manually approve each transaction before funds move.
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 invoked with the wrong amount, contract, or wallet, the agent could authorize spending or move USDC in ways the user did not intend.
The skill instructs the agent to use raw exec/cast commands to send blockchain transactions that approve a contract to spend USDC. The amount, contract address, and key are placeholders, and the provided artifacts do not show transaction limits or confirmation safeguards.
cast send <usdcAddress> "approve(address,uint256)" <contractAddress> <amountInWei> --private-key <agentPrivateKey> --rpc-url <rpcUrl>
Require explicit user confirmation for every transaction, verify contract and token addresses, use small capped allowances, and prefer a dedicated low-balance wallet or wallet-signing flow instead of unattended raw commands.
Providing a main wallet private key could expose full wallet control to the agent environment and any command/process handling around it.
Multiple transaction templates require the agent's private key as a command-line argument. That private key grants wallet authority, while the registry metadata declares no primary credential or environment variable contract.
--private-key <agentPrivateKey> --rpc-url <rpcUrl>
Do not use a main wallet private key. Use a separate limited wallet, store secrets through a secure secret manager, avoid passing keys on command lines where possible, and ensure the skill declares and documents its credential requirements.
A user may need to supply their own tooling and independently confirm that the referenced contracts and website are legitimate.
The registry provides limited provenance and declares no required binaries or install mechanism, even though the skill documentation relies on external blockchain tooling such as cast. This is not malicious by itself, but users should verify tooling and contract provenance before sending funds.
Source: unknown; Homepage: none; Required binaries: none; No install spec — this is an instruction-only skill.
Verify the project, deployment addresses, and Foundry/cast installation from trusted sources before using the skill with any funded wallet.