prediction-market-risk-review

Use it when:: A prediction-market, basket, oracle or trading-agent workflow is about to handle venue logins, API keys, portfolio data or trade planning.
It does:: Checks five gates: advice boundary, venue and regulatory limits, data quality, security and privacy.
You get:: Pass, warn or fail findings, the actions it blocks, required mitigations and a safe next step.
Blocks:: Buy, sell, hold or sizing recommendations, and any execution step without a separate implementation plan and your explicit approval.

TL;DR

A review gate from ECC, run before a prediction-market workflow touches anything financial or execution-capable. The advice gate keeps output informational, strips buy, sell, hold and sizing recommendations and keeps manual decision points explicit. The venue gate looks at terms, geography restrictions, account limits and API rules, flags betting, derivatives, securities or commodities ambiguity for legal review, and refuses to bypass restrictions or rate limits. The data gate checks liquidity, spreads, resolution rules, stale prices and timestamps, and labels public venue data apart from the gated data of Itô, an API it names by its ITO_API_KEY. The security gate forbids requesting or storing private keys, seed phrases or passwords, keeps the Itô and venue API keys out of logs and docs, defaults to read-only scopes, and requires circuit breakers, spend limits, dry runs and human approval before any execution is added. The privacy gate minimizes portfolio, financial and knowledge-base data and redacts private sources in public artifacts. It changes nothing itself: it reports.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill prediction-market-risk-review

skills.sh page Source on GitHub All skills from affaan-m/ecc

Total Downloads: 5,200 on skills.sh, Nov 9, 2026
Repo stars: 299,776 affaan-m/ecc
First seen: May 25, 2026 on skills.sh

Weekly Downloads

444

+71% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	259
Sep 28	158
Oct 5	138
Oct 12	226
Oct 19	405
Oct 26	399
Nov 2	468
Nov 9	444

Category	category:security category:software-engineering Compliance, guardrails, skill vetting and browser fingerprinting. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	finance security privacy guardrails

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter

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

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.