Polymarket Bots by
Analysis
The skill coherently controls Dawn prediction-market bots, but it can log into an account, handle funding, approve strategy rules, and launch live budgeted trading runs, so it needs careful review before installation.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`dawn strategy rules <conversationId> approve-all` ... `dawn strategy launch <conversationId> --budget <usd> [--live] [--hours N]`
These commands let the agent approve all strategy rules and start a live strategy with a dollar budget; the instructions do not require a separate explicit confirmation before live launch or approve-all.
`dawn strategy launch <conversationId> --budget <usd> [--live] [--hours N]` ... `dawn run stop <conversationId>`
The launch command can create an active strategy run, `--hours` is optional, and stopping is a separate requested action, so a run may continue outside the immediate chat turn.
npm install -g @dawnai/cli
The global npm install is central to the skill's stated purpose, but the artifact does not pin a package version, so users rely on the current external package.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
1. Authenticate: `dawn auth login`. 2. Confirm funding path: `dawn account fund` (required for live runs).
The skill requires access to a user's Dawn account and funding flow; this is high-impact account authority, and the registry requirements list no primary credential.
