Polymarket Nordic Trader
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill matches its stated trading purpose, but it can execute real prediction-market trades and its credential and runtime requirements are under-declared in the registry metadata.
Treat this as an automated trading bot, not an instruction-only template. Install only if you trust the publisher and the simmer-sdk dependency, use a revocable low-limit API key, run in paper mode first, and do not enable live trading unless you are comfortable with the configured spending limits and lack of per-order confirmation.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If live mode is enabled, the skill can spend funds and change Polymarket positions across multiple markets.
This shows that live mode selects the real trading venue and the code programmatically submits trades. It is purpose-aligned and defaults to paper mode, but live mode can still mutate financial positions.
live=True venue="polymarket" (real trades, only with --live flag) ... r = client.trade( market_id=m.id, side=side, amount=size, ... )
Use paper mode first, set conservative position limits, and require explicit user approval before any --live run or live order placement.
A user may not realize before installation that the skill needs an API key that may authorize trading activity.
The registry-facing metadata says no credential is required, but the artifacts also show SIMMER_API_KEY is required and read by the code. For a trading bot, this is a material under-declaration of account authority.
Required env vars: none ... Env var declarations: none ... Primary credential: none
Declare SIMMER_API_KEY as a required credential, document what account authority it grants, and use a revocable, least-privilege key with spending limits if available.
Users may underestimate the code and dependency surface that will run for a financial automation skill.
This shows an external pip dependency and runnable automaton entrypoint, despite the registry summary saying there is no install spec and this is an instruction-only skill. The dependency is also unpinned.
"requires": { "env": [ "SIMMER_API_KEY" ], "pip": [ "simmer-sdk" ] }, ... "automaton": { "managed": true, "entrypoint": "trader.py" }Align registry metadata with clawhub.json, pin or otherwise verify the simmer-sdk dependency, and review the full published trader.py before enabling live trading.