affaan-m/ecc

prediction-market-risk-review

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.

All-time #3446 Trending #2774 First seen May 25, 2026
8-week activity · all time api

Installation

$ npx skills add affaan-m/ecc --skill prediction-market-risk-review

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from affaan-m/ecc · top by installs.

npx skills add affaan-m/ecc

Browse all from affaan-m/ecc

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 254.3K
License LICENSE
Default branch main
Open issues 54
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
origin
ECC

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,882 B
  • docs SUMMARY.md 264 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,994 installs

SKILL.md

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 ITOAPIKEY 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:

  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.