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.
Privacy
- Minimize user portfolio, financial, and knowledge-base data.
- Redact private sources in public artifacts.
- Preserve only the fields needed for the review.
Output Contract
Return:
- scope reviewed
- pass/warn/fail findings
- blocked actions
- required mitigations
- safe next step
If any execution-capable step is requested, require a separate implementation
plan and explicit user approval.
1---2name: prediction-market-risk-review3description: Review prediction-market, basket, oracle, and trading-agent workflows for compliance, safety, data-quality, privacy, and execution risk. Use before any workflow handles venue auth, user portfolio data, API keys, or trade planning.4---56# Prediction Market Risk Review78Use this skill before a prediction-market workflow touches user financial9context, venue authentication, portfolio data, automation, or execution-capable10tools.1112## Review Gates1314### Advice Boundary1516- Confirm the output is informational.17- Remove buy/sell/hold/size recommendations.18- Keep manual user decision points explicit.1920### Venue And Regulatory Boundary2122- Identify venue terms, geography restrictions, account limits, and API rules.23- Flag betting, derivatives, securities, or commodities ambiguity for legal24 review when relevant.25- Do not bypass venue restrictions or rate limits.2627### Data Quality2829- Check market liquidity, spread, resolution rules, stale prices, and source30 timestamps.31- Separate public venue data from Itô gated data.32- Do not mix public and private sources without labels.3334### Security3536- Do not request or store private keys, seed phrases, or passwords.37- Keep `ITO_API_KEY` and venue API keys out of logs and docs.38- Use read-only scopes by default.39- Require circuit breakers, spend limits, dry runs, and human approval before40 any private implementation adds execution.4142### Privacy4344- Minimize user portfolio, financial, and knowledge-base data.45- Redact private sources in public artifacts.46- Preserve only the fields needed for the review.4748## Output Contract4950Return:51521. scope reviewed532. pass/warn/fail findings543. blocked actions554. required mitigations565. safe next step5758If any execution-capable step is requested, require a separate implementation59plan and explicit user approval.
sakamoto-family-smile