prediction-market-risk-review
This skill reviews prediction-market, basket, oracle, and trading-agent workflows for compliance, safety, data-quality, privacy, and execution risk before any workflow handles venue auth, user portfolio data, or trade planning. It helps developers and auditors ensure workflows meet regulatory and security standards, returning findings, blocked actions, and required mitigations.
npx skills add https://github.com/affaan-m/ecc --skill prediction-market-risk-reviewBefore / After Comparison
1 组Without this skill, teams manually review prediction-market workflows for compliance, security, and data quality, taking an average of 4 hours with a 30% error rate.
With this Skill, the review is automated, completing in 30 minutes with a 5% error rate.
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_KEYand 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.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill