Polymarket 交易助手

AdvisoryAudited by Static analysis on May 10, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

The agent could place real-money Polymarket trades without the user reviewing each order.

Why it was flagged

The artifact explicitly offers an agent-directed live trading workflow without human confirmation, which is high-impact financial mutation.

Skill content
danger-auto-trade-polymarket ... 全自动交易(无需确认) ... 无需人工确认,AI 自主完成市场扫描、概率评估、仓位计算和实盘下单
Recommendation

Disable or remove the no-confirmation mode by default; require explicit per-trade approval, fixed maximum exposure, and paper-trading dry runs before live orders.

What this means

If invoked directly or by another skill, a mistaken or manipulated amount could create a larger trade than intended.

Why it was flagged

The executable trading path posts caller-supplied order amounts; no maximum amount or per-order confirmation is visible in this script, despite documentation mentioning risk controls.

Skill content
const orderAmount = amount ?? (size && price ? size * price : 0); ... createAndPostMarketOrder({ tokenID, amount: orderAmount, side }, ...)
Recommendation

Enforce hard caps, balance checks, and confirmation inside the trading script itself, not only in surrounding instructions.

What this means

An error in one trade attempt could cancel unrelated open Polymarket orders in the same account.

Why it was flagged

A single order execution error can trigger account-wide cancellation rather than limiting cleanup to the order created by that invocation.

Skill content
catch (err: any) { ... await client!.cancelAll(); ... }
Recommendation

Only cancel orders created by the current operation, and require user confirmation before any account-wide cancel-all action.

What this means

Anyone or any agent process with access to that key file could potentially trade with the wallet's funds.

Why it was flagged

Using a raw wallet private key is expected for automated trading, but in combination with no-confirmation live trading it grants broad signing authority and is not reflected in the registry's credential declarations.

Skill content
PRIVATE_KEY ... Your wallet's private key ... MetaMask: Settings → Security → Export Private Key
Recommendation

Use a dedicated low-balance trading wallet, strict file permissions, and declared secret storage; avoid using a main wallet private key.

What this means

This indicates unsafe credential hygiene and creates uncertainty about whether a real credential or account identifier was bundled.

Why it was flagged

The distributed package contains a plaintext key-like value and wallet address, while metadata says there is no primary credential.

Skill content
API 密钥 019e113b-87e1-... 地址 0x70e0...
Recommendation

Remove bundled secrets, rotate any real exposed key, and use explicit environment-variable or secret-manager declarations instead.

What this means

The agent may install or execute code from an unexpected local path, especially if stale or unreviewed files already exist there.

Why it was flagged

The skill instructs dependency installation and later execution from a hard-coded Claude directory, not the reviewed OpenClaw skill path; stderr suppression also reduces install visibility.

Skill content
cd ~/.claude/skills/api-trade-polymarket/scripts && npm install 2>/dev/null
Recommendation

Use OpenClaw `{baseDir}` paths, declare installation requirements, and avoid suppressing install output for a wallet-enabled trading skill.