Skillv1.0.0

ClawScan security

Polymarket Alpha Suite · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 10, 2026, 2:20 AM

Verdict: Benign
Confidence: medium
Model: gpt-5-mini
Summary: The package's code and runtime instructions line up with its stated purpose (Polymarket scanning and optional live trading); sensitive credentials (private key / API keys) are only needed for live order placement and are proportionate, but the registry metadata omits those env vars and the origin is unverified — review before giving live keys.
Guidance: This package appears to do what it claims: scan Polymarket and optionally place live trades. Things to consider before installing or running it: - Paper-trade first: all tools support dry-run/paper modes — exercise those before supplying any credentials. - Sensitive creds: live trading requires API keys or a private key (POLY_PK). Never paste your private key into code or commit it to git. Prefer read-only API keys where possible and keep keys in a secure secrets store. - Check the origin: the registry metadata shows no homepage and an unknown owner ID. If you don't trust the author, review all source files yourself before running, and run in an isolated environment (VM or container). - Local files: the tools write history/signals/trades JSON files under a local data/ directory. Expect local storage of trading activity. - Network calls: the scripts call Polymarket endpoints and Hyperliquid; this is expected for market data but means the code will make outbound network requests. - Minimal metadata mismatch: the skill package metadata lists no required env vars, but SKILL.md and the code do require optional live-trading variables — treat that as a documentation/metadata omission and verify env requirements before enabling live mode. If you plan to use live trading capability, audit the code paths that execute orders and consider using a small dedicated wallet with limited funds, rotating keys, and monitoring API usage.

Review Dimensions

Purpose & Capability: okName/description match the delivered artifacts: Node.js tools that query Polymarket (Gamma/CLOB), Hyperliquid, and implement arbitrage/alpha strategies. Binaries, endpoints, and files referenced are consistent with a Polymarket trading toolkit.
Instruction Scope: noteSKILL.md instructs running the included Node scripts and documents environment variables and .env usage for live trading. The instructions are scoped to market scanning, paper trading, and optional live trading. One inconsistency: registry metadata declared no required env vars, but SKILL.md and the code clearly reference POLYMARKET_* variables and POLY_PK for live trading — those are optional for paper/dry runs but are required for live order placement.
Install Mechanism: okNo install spec (instruction-only for the agent); the package is delivered as source files (Node scripts). No external archive downloads or installers are invoked by the skill itself. This is low installation risk, but executing untrusted JS source still requires caution.
Credentials: noteThe code optionally uses POLYMARKET_API_KEY, POLYMARKET_SECRET, POLYMARKET_PASSPHRASE, POLY_PK, POLY_FUNDER and similar variables for live trading. These credentials are proportionate to automated trading functionality. POLY_PK (private key) is highly sensitive but only required for live trading; the README/SETUP emphasize paper trading without credentials. The registry listing not declaring these env vars is an omission and should be corrected by the publisher.
Persistence & Privilege: okalways:false (normal). The tools persist local state (data/ directory, trades/signals JSON files) under the skill directory which is expected for trading history; they do not request system-wide config changes or other skills' credentials. Autonomous invocation is allowed by default but is not excessive here.