Prediction Market Risk Review
- 1.3k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
prediction-market-risk-review is a security checker skill that audits prediction-market, oracle, basket, and trading-agent workflows for compliance, safety, data-quality, privacy, and execution risk before developers con
About
prediction-market-risk-review is an ECC-origin agent skill that gates prediction-market and trading automation workflows before they handle venue authentication, user portfolio data, API keys, or trade planning. Review gates cover advice boundaries—keeping outputs informational without buy/sell/hold sizing recommendations—and venue plus regulatory concerns alongside data-quality and privacy checks. Developers invoke prediction-market-risk-review when building agents that interact with prediction markets, oracle feeds, basket strategies, or execution-capable trading tools and need a structured preflight audit. The skill emphasizes explicit manual decision points and removal of direct trading recommendations from agent outputs before any workflow touches user financial context.
- 5 review gates covering Advice Boundary, Venue & Regulatory Boundary, Data Quality, Security, and Privacy
- Explicitly removes buy/sell/hold/size recommendations while preserving informational output
- Flags venue terms, geography restrictions, liquidity issues, stale prices, and regulatory ambiguity
- Enforces read-only scopes, circuit breakers, spend limits, dry runs, and human approval gates
- Separates public venue data from private Itô gated data with mandatory labeling
Prediction Market Risk Review by the numbers
- 1,271 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #348 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill prediction-market-risk-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.3k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you security-review prediction market trading agents?
Audit prediction-market, oracle, basket, and trading-agent workflows for compliance, safety, data-quality, privacy, and execution risk before they touch real fina
Who is it for?
Developers building prediction-market or trading agents who must preflight compliance, privacy, and execution risks before live venue credentials.
Skip if: General application security reviews unrelated to trading venues, oracle feeds, or portfolio-handling agent workflows.
When should I use this skill?
A prediction-market workflow will touch venue auth, API keys, user portfolio data, automation, or execution-capable trading tools.
What you get
Risk review gate checklists, advice-boundary fixes, and compliance notes for prediction-market workflows.
- Risk review gate checklist
- Compliance and privacy findings
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_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:
1. scope reviewed 2. pass/warn/fail findings 3. blocked actions 4. required mitigations 5. safe next step
If any execution-capable step is requested, require a separate implementation plan and explicit user approval.
Related skills
Entra App RegistrationCorrectly register an application in Microsoft Entra ID, configure OAuth 2.0 flows, request the right API permissions, and generate working MSAL authentication snippets484k1.3kAzure ComplianceRun automated Azure compliance scans, security posture checks, and Key Vault expiration audits before deploying.484k1.3k
Openclaw Secure Linux CloudDeploy and harden an OpenClaw agent instance on a Linux cloud server following battle-tested security defaults.270k72
Better Auth Best PracticesCorrectly configure Better Auth for secure authentication with database adapters, sessions, OAuth, email/password, and plugins in TypeScript projects.80.9k206
Firebase Security Rules AuditorAutomatically audit Firebase Firestore security rules for bypass vulnerabilities and logic gaps before deploying.80.4k397
Audit WebsiteRun comprehensive audits that surface SEO, performance, security, technical, and content issues with LLM-optimized reports and health scores.65.6k85How it compares
Use prediction-market-risk-review for finance-agent compliance preflight rather than generic OWASP or dependency vulnerability scans.
FAQ
When must prediction-market-risk-review run?
prediction-market-risk-review should run before any workflow handles venue authentication, user portfolio data, API keys, trade planning, or other execution-capable financial tooling.
What advice rules does prediction-market-risk-review enforce?
prediction-market-risk-review confirms outputs stay informational, removes buy/sell/hold sizing recommendations, and keeps manual user decision points explicit in trading-agent responses.