Prediction Market Risk Review
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/everything-claude-code
prediction-market-risk-review is a Claude Code skill that runs a compliance and safety review gate over prediction-market and trading-agent workflows before they touch auth, portfolio data, keys, or execution.
About
prediction-market-risk-review is a Claude Code skill that reviews prediction-market, oracle, and trading-agent workflows for compliance, safety, data quality, privacy, and execution risk before they handle venue authentication, user portfolio data, API keys, or trade planning. It walks structured review gates covering the advice boundary (strip buy/sell/hold/size recommendations), a venue and regulatory boundary, data quality, security (no private keys, read-only scopes, keys out of logs), and privacy. Developers use it as a compliance checklist before shipping agents, dashboards, or APIs that integrate prediction-market venues.
- Compliance and safety review gate before a prediction-market workflow touches venue auth, portfolio data, or execution
- Review gates: advice boundary, venue/regulatory boundary, data quality, security, privacy
- Requires circuit breakers, spend limits, dry runs, and human approval before any execution
Prediction Market Risk Review by the numbers
- 1,398 all-time installs (skills.sh)
- +217 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #335 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
prediction-market-risk-review capabilities & compatibility
- Capabilities
- security audit · compliance review · risk review
- Use cases
- security audit · research
What prediction-market-risk-review says it does
Use this skill before a prediction-market workflow touches user financial context, venue authentication, portfolio data, automation, or execution-capable tools.
Do not request or store private keys, seed phrases, or passwords.
Use read-only scopes by default.
npx skills add https://github.com/affaan-m/everything-claude-code --skill prediction-market-risk-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
What it does
Run a structured compliance and safety review before a prediction-market or trading-agent workflow handles venue auth, portfolio data, API keys, or execution.
Who is it for?
Gating prediction-market or trading-agent workflows for compliance before they handle auth, portfolio data, or execution.
Skip if: Implementing execution itself; it requires a separate implementation plan and explicit user approval for any execution-capable step.
When should I use this skill?
Before a workflow touches user financial context, venue authentication, portfolio data, automation, or execution-capable tools.
What you get
A pass/warn/fail review with blocked actions, required mitigations, and a safe next step.
- scope reviewed
- pass/warn/fail findings
- blocked actions
By the numbers
- five review gates
- five-part output contract
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
Pick prediction-market-risk-review over oracle-research when the workflow already handles credentials, portfolio data, or execution—not when you only need market signal research.
FAQ
Does it block execution?
Any execution-capable step requires a separate implementation plan and explicit user approval; it requires circuit breakers, spend limits, dry runs, and human approval first.
What gates does it run?
Advice boundary, venue and regulatory boundary, data quality, security, and privacy.