Back to skill
Skillv1.0.0
ClawScan security
Polymarket Cryptos Maker 5m · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
ReviewMar 16, 2026, 9:11 AM
- Verdict
- Review
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's code generally matches a Polymarket market-maker, but it reads sensitive environment variables (wallet private key), fails to declare them in metadata or runtime docs, and advertises an automated stop-loss that is only tracked in a simulated balance — these inconsistencies are risky and need clarification before use.
- Guidance
- Do not run this against a real wallet until you verify and test it yourself. Key points to check before installing/using: 1) The script reads .env and expects WALLET_PRIVATE_KEY and LIVE_TRADING but the SKILL.md and metadata do not mention these — supply a private key only to code you fully trust. 2) The advertised "8% Stop-Loss" is implemented against an internal simulated balance (INITIAL_BALANCE/currentBalance) and is not tied to actual on-chain balances or exchange account data — it may not protect real funds. 3) The package.json requires @polymarket/clob-client, ethers and dotenv; run npm install in a controlled environment and inspect installed packages. 4) Prefer testing in a dry-run or sandbox (LIVE_TRADING unset/false) and with a throwaway wallet with minimal funds. 5) If you need this skill, ask the publisher to update SKILL.md and registry metadata to declare required env vars, explain how stop-loss maps to real balances, and include explicit install/run instructions. If you are not comfortable auditing the code and npm dependencies yourself, do not provide your wallet private key or enable LIVE_TRADING.
Review Dimensions
- Purpose & Capability
- concernThe name/description and the code both implement a continuous Polymarket market-making bot (placing sell orders on both sides). However, the metadata declares no required credentials/env vars while the code expects LIVE_TRADING and WALLET_PRIVATE_KEY (loaded via dotenv). That mismatch is unexplained and problematic for a trading skill.
- Instruction Scope
- concernSKILL.md tells the user how to launch the script in the background but omits crucial operational details: it does not mention that you must set LIVE_TRADING or provide WALLET_PRIVATE_KEY (or a .env file), and it does not instruct installing Node dependencies. The README claims an automated 8% stop-loss, but the code's stop-loss uses an internal simulated balance (INITIAL_BALANCE/currentBalance) and is not tied to on-chain or actual wallet balances — this could mislead users into thinking their real funds are protected.
- Install Mechanism
- noteNo install spec is provided (instruction-only), but package.json lists dependencies (@polymarket/clob-client, ethers, dotenv). The SKILL.md does not instruct to run npm install or otherwise install dependencies; that omission is a usability/safety concern but not itself an active install risk. Dependencies are from npm (traceable), not a remote archive.
- Credentials
- concernThe package uses dotenv and reads process.env.LIVE_TRADING and process.env.WALLET_PRIVATE_KEY (sensitive). Metadata declared no required env or primary credential — omitting a required private key is an incoherence. Requesting a wallet private key is expected for a trading bot, but the missing documentation and simulated stop-loss make that access disproportionate without clearer safeguards.
- Persistence & Privilege
- okThe skill does not request 'always: true' and does not modify other skill/system configs. It runs as a user-launched Node process; autonomous invocation is permitted by platform defaults but not specifically privileged by this skill.
