Skillv1.0.1

ClawScan security

Polymarket Copy Dynamic Roster Trader · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 28, 2026, 2:34 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's code and SKILL.md mostly match the stated copytrading purpose, but registry metadata and install information are inconsistent (missing required SIMMER_API_KEY and pip dependency), so verify dependencies and review the full code and package provenance before installing.
Guidance: What to check before installing: - Expect to provide a SIMMER_API_KEY and that the platform will need to install the 'simmer-sdk' Python package; the registry summary omitted these—confirm where/when dependencies are installed and pin package versions. - Review the complete trader.py (the posted version was truncated) to confirm there are no hidden endpoints, telemetry calls, or credential exfiltration. The visible code calls only predicting.top and data-api.polymarket.com and uses the Simmer SDK. - Run the skill in paper/sim mode first (SKILL defaults to paper when --live is not set) and enforce low COPY_MAX_USD / MAX_POSITIONS while verifying behavior. - Limit the SIMMER_API_KEY scope (use least privilege) and use a disposable/test key when first evaluating; rotate or revoke the key if you stop using the skill. - Verify the simmer-sdk package source (PyPI) and pin a known-good version, or vendor-review the SDK if you must rely on it for trade execution. - If you need higher assurance, sandbox the skill, run static analysis on the full trader.py, and confirm the platform will not leak environment variables to other skills or logs.

Review Dimensions

Purpose & Capability: noteThe skill claims to discover top Polymarket wallets and copytrade them via Simmer; the code and SKILL.md implement leaderboard scraping, rolling-PnL computation, roster construction, and use of the Simmer SDK—these capabilities align with the description. However, the registry summary at the top of the report lists no required env vars or dependencies, while both clawhub.json and SKILL.md declare a required SIMMER_API_KEY and the simmer-sdk pip package. That metadata mismatch is unexpected.
Instruction Scope: okSKILL.md and trader.py limit their runtime actions to fetching public leaderboards (predicting.top), fetching on-chain activity from Polymarket's data-api, computing scores, and calling Simmer's SDK copytrading endpoints. Instructions and code reference only SIMMER_* tunables and SIMMER_API_KEY; there are no instructions to read unrelated local files, system credentials, or to post data to unknown endpoints.
Install Mechanism: noteThis is an instruction-and-code skill with no formal install spec in the registry, but clawhub.json declares a pip dependency on simmer-sdk. Because there's no explicit install block in the registry metadata, the skill may rely on the platform to install simmer-sdk; confirm how dependencies are installed and from where (PyPI) and pin versions. No arbitrary download URLs or archive extraction were found.
Credentials: concernThe skill requires SIMMER_API_KEY (used directly by trader.py) and numerous optional SIMMER_* tunables—these are reasonable for a copytrading adapter. The concern is the inconsistency: the registry summary omitted required env vars while clawhub.json and the code do require SIMMER_API_KEY. That mismatch could cause accidental key exposure if users are unaware or provide credentials in the wrong place. Ensure the key is scoped to only the Simmer capabilities you intend to grant.
Persistence & Privilege: okThe skill is not always:true and autostart is false. clawhub.json marks automaton.managed with entrypoint trader.py (so the platform may run it), but there is no indication the skill modifies other skills or global agent settings. The agent will run the skill with access to the SIMMER_API_KEY when invoked.