Skillv1.0.4

ClawScan security

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

Scanner verdict

SuspiciousMar 4, 2026, 4:05 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill largely does what it claims (Polymarket + skillpay billing), but there are clear mismatches between the declared metadata and the runtime instructions (missing declared env vars), and contradictory statements about the time window for volume calculations — so you should review the payment requirements and code before using.
Guidance: This skill appears to implement a Polymarket volume tracker and charges via skillpay.me, which is consistent — but the package metadata failed to declare the required payment credentials. Before installing or running: (1) Inspect the script (you already have it) and confirm you are comfortable providing a skillpay.me API key and user ID; (2) Only give a key with minimal permission/scope for billing and avoid reusing high-privilege keys; (3) Verify skillpay.me is legitimate and the Skill ID matches what you expect; (4) Note the documentation inconsistency: some places claim 'last 10 minutes' while the data source notes 'total (lifetime)' — ask the author which metric is used and whether the time-window behavior suits you; (5) If you want to try without paying, use the provided --skip-payment/testing option, but be aware behavior may differ; (6) Ask the publisher to update the registry metadata to declare SKILLPAY_API_KEY and SKILLPAY_USER_ID as required env vars and to clarify the time-window semantics. If you cannot validate these points, do not provide real payment credentials.

Review Dimensions

Purpose & Capability: noteThe skill's actual network activity (Polymarket Gamma API, Polymarket CLOB trades, and skillpay.me billing) is consistent with a 'Polymarket Volume Tracker' that charges per call. However the registry metadata declares no required environment variables or credentials while the runtime instructions and code require a skillpay API key and user ID — that mismatch is unexpected and reduces trust.
Instruction Scope: concernSKILL.md and the script instruct the agent to call only Polymarket and skillpay.me endpoints (no unrelated external hosts), which is within the stated purpose. But there are contradictory statements about whether volumes are lifetime vs 'last 10 minutes' and the SKILL.md requires providing an API key and user ID (or env vars) even though the skill metadata lists none. The instructions also require payment per call (and provide a skip-payment testing flag) — the payment flow and requirement should be clearly declared in registry metadata.
Install Mechanism: okNo install spec (script is pure Python using standard library urllib). Nothing is downloaded or written by an automated installer, so install risk is low.
Credentials: concernThe runtime expects a SKILLPAY_API_KEY and SKILLPAY_USER_ID (CLI flags or env vars) to charge users, but the skill's declared 'required env vars' is empty. Requiring a payment API key is proportional to the billing feature, but the lack of declaration is an incoherence and a usability/security risk: users may not realize they must provide credentials or how they're used. The skill does not request unrelated credentials.
Persistence & Privilege: okThe skill is not marked always:true and does not attempt to modify other skills or system-wide configuration. It runs as a short-lived script and does network calls only to the service endpoints described.