Prediction Market Risk Review

Before you wire up any prediction market workflow to real APIs or user portfolios, run this review. It checks five gates: whether you're crossing into advice territory, venue and regulatory boundaries, data quality issues like stale prices or mixed sources, security problems like exposed keys or missing spend limits, and privacy leaks. The output tells you what passed, what needs mitigation, and what's blocked outright. Honest take: this is the kind of checklist you should already have in your head, but codifying it as a skill means you won't skip steps when you're moving fast or handing off context to an agent.

skills.sh installs: 5.3K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill prediction-market-risk-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Prediction Market Risk Review

Use this skill before a prediction-market workflow touches user financial context, venue authentication, portfolio data, automation, or execution-capable tools.

Review Gates

Advice Boundary

Confirm the output is informational.
Remove buy/sell/hold/size recommendations.
Keep manual user decision points explicit.

Venue And Regulatory Boundary

Identify venue terms, geography restrictions, account limits, and API rules.
Flag betting, derivatives, securities, or commodities ambiguity for legal review when relevant.
Do not bypass venue restrictions or rate limits.

Data Quality

Check market liquidity, spread, resolution rules, stale prices, and source timestamps.
Separate public venue data from Itô gated data.
Do not mix public and private sources without labels.

Security

Do not request or store private keys, seed phrases, or passwords.
Keep ITO_API_KEY and venue API keys out of logs and docs.
Use read-only scopes by default.
Require circuit breakers, spend limits, dry runs, and human approval before any private implementation adds execution.