prediction-market-risk-review
affaan-m/ecc
Review prediction-market workflows for compliance, safety, data quality, privacy, and execution risk before handling auth or portfolio data.
What is prediction-market-risk-review?
This skill audits prediction-market, basket, oracle, and trading-agent workflows for regulatory compliance, security vulnerabilities, data quality issues, and privacy risks. Use it before any workflow accesses venue authentication, user portfolio data, API keys, or executes trades.
- Verify outputs are informational with no implicit buy/sell/hold recommendations
- Identify venue terms, geography restrictions, account limits, and API rule conflicts
- Assess market liquidity, spreads, resolution rules, and data staleness
- Enforce security boundaries: no private keys, seed phrases, or passwords in logs
- Minimize and redact user portfolio and financial data in public artifacts
- Flag execution-capable steps requiring separate approval and implementation plan
How to install prediction-market-risk-review
npx skills add null --skill prediction-market-risk-reviewHow to use prediction-market-risk-review
- 1.Run the skill before any workflow accesses venue auth, portfolio data, or API keys
- 2.Provide the workflow description, data sources, and intended outputs for review
- 3.Review the returned findings: scope, pass/warn/fail status, blocked actions, and mitigations
- 4.Address all warnings and failures before proceeding to implementation
- 5.Obtain explicit user approval for any execution-capable steps
Use cases
- Audit a trading bot workflow before connecting it to live exchange APIs
- Review an oracle-fed prediction market for data-quality and source-mixing issues
- Check a portfolio-analysis tool for privacy leaks before sharing outputs
- Validate a derivatives strategy workflow against venue restrictions and regulatory boundaries
- Approve a market-making agent's risk controls before enabling execution
- Compliance and risk officers reviewing AI trading workflows
- Developers building prediction-market or portfolio-analysis agents
- Financial technologists integrating third-party market data and APIs
- Teams deploying automated trading or execution systems
prediction-market-risk-review FAQ
Stop the workflow and address the failure before proceeding. Common failures include storing private keys, mixing public and private data sources without labels, or implicit trading recommendations. Implement the required mitigations and re-run the review.
No. This skill only reviews workflows for risk and compliance. It does not recommend buy/sell/hold actions or approve execution. Execution requires a separate implementation plan and explicit user approval.
Provide the workflow description, all data sources (venue APIs, oracles, knowledge bases), intended outputs, and any execution capabilities. The skill will assess scope, data quality, security, and privacy.
This skill is designed specifically for prediction-market, basket, oracle, and trading-agent workflows. It may not be applicable to other domains.
The skill requires explicit labeling of public vs. private sources and will flag any mixing without clear separation. Redact private sources in public artifacts.
Full instructions (SKILL.md)
Source of truth, from affaan-m/ecc.
name: prediction-market-risk-review description: 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. metadata: origin: ECC
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.
Related skills
More from affaan-m/ecc and the wider catalog.
prisma-patterns
Production Prisma ORM patterns, query optimization, and critical traps for TypeScript backends.
product-capability
Translate product intent into implementation-ready capability plans with explicit constraints and interfaces.
product-lens
Validate product direction and diagnose the "why" before building—run founder-level reviews and pressure-test ideas.
production-audit
Local production-readiness audit for shipped apps—no external data sharing, just risk assessment.
production-scheduling
Expert production scheduling for discrete/batch manufacturing: sequencing, bottleneck resolution, changeover optimization, and disruption response.
project-flow-ops
Coordinate GitHub and Linear by triaging issues, linking active work, and keeping execution synchronized across public and internal layers.