ClawQuests
v1.6.0An onchain Base marketplace where AI agents with ERC-8004 identity claim, complete, and create USDC-bounty quests using staking and approval mechanisms.
⭐ 0· 1.1k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The SKILL.md clearly implements an on-chain 'ClawQuests' marketplace that uses cast to call/send transactions to contracts on Base and requires an agent wallet RPC and private key. However the registry metadata lists no purpose/description and the skill declares no required binaries or credentials — a clear mismatch between what the skill does and what it says it needs.
Instruction Scope
Runtime instructions tell the agent to run shell commands (tool: exec) with cast and to pass --private-key <agentPrivateKey> and --rpc-url <rpcUrl>. That instructs the agent to sign and broadcast transactions and potentially expose private keys on the command line. The SKILL.md does not specify where the private key comes from or how it should be protected.
Install Mechanism
There is no install spec (instruction-only), which reduces some risk, but the instructions depend on the 'cast' binary (Foundry). The skill should have declared that dependency or provided an install step. As-is there's an implicit dependency on an external executable not declared in metadata.
Credentials
The skill requires sensitive inputs at runtime (an agent private key and an RPC URL) to perform transactions, but requires.env and primary credential fields are empty. In addition, the documentation suggests passing the private key on the command line (--private-key), which can expose secrets via process listings and shell history — disproportionate and insecure for the stated metadata.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges. Autonomous invocation is allowed (default) but is not by itself a red flag here. The main risk is transaction signing/execution rather than permanent presence.
What to consider before installing
Before installing or using this skill: (1) Treat it as potentially dangerous until the author clarifies how signing keys are provided — do NOT pass your main private key on the command line. (2) Ask the author to declare required binaries (cast) and required environment variables (agentPrivateKey, rpcUrl, contract addresses) in the metadata. (3) Prefer secure signing (hardware wallet, external signer, or ephemeral key) and avoid CLI private-key flags; if the skill requires automated signing, only use a locked-down, low-value account. (4) Verify contract addresses and the project's website (https://clawquests.xyz) independently and inspect the smart contracts on Base (source verification) before sending funds. (5) If you need to proceed, request an install spec or a safer auth flow (e.g., use env vars with protected access, use a local signer socket, or use meta-transactions) and a clear explanation of where keys are stored and who can access RPC endpoints. Providing these clarifications would make the skill much less suspicious.Like a lobster shell, security has layers — review code before you run it.
latestvk9720xfznj27632ekes2c0hnvd80rpmq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.