Skip to content
cccskills
FreePublished on GitHubEnglish overview

prediction-market-risk-review

Review prediction-market and trading-agent workflows before they handle account access, portfolio data, or trade planning. Produces structured findings on venue rules, data quality, security, privacy, and execution risks, with required safeguards and a safe next step.

OriginalShow the original 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.

Run score Not tested

See how to install

Good for

  • Review workflows before adding venue authentication
  • Check how portfolio data and API keys are handled
  • Review market data quality and source labels
  • Identify venue restrictions and legal review needs
  • Assess safeguards before adding trade execution

Overview

What it does

This skill reviews risks in prediction markets, where people trade on event outcomes, and in trading-agent workflows. It checks trading-service terms, geographic restrictions, stale prices, liquidity, outcome resolution rules, API key handling, and how much personal portfolio data is stored. Results cover the reviewed scope, pass/warn/fail findings, actions to block, required mitigations, and a safe next step.

When it helps

Use it before handling trading-service authentication or portfolio data, or before adding trade planning and automation. It also helps when public data and restricted-access data are mixed, or when checking whether informational output has crossed into trading recommendations.

Example requests

  • “Review this prediction-market workflow for service rules, data quality, and privacy risks.”
  • “Check how API keys and portfolio data are handled, and list the required mitigations.”
  • “Before adding trade execution, identify safeguards and actions that should be blocked.”

Notes

Buy, sell, hold, and trade-size recommendations are outside its scope. Unclear legal questions are flagged for legal review. Trade execution requires a separate implementation plan and explicit user approval. The review also checks safeguards such as circuit breakers, spending limits, and dry runs.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt prohibits collecting private keys and logging API keys, and requires explicit approval and spending limits before execution.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodThe workflow defines review checks and outputs without requiring tool installation or obtaining API keys.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

  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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC287.7KUpdated Oct 21, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC287.7KUpdated Oct 21, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC287.7KUpdated Oct 21, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC287.7KUpdated Oct 21, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC287.7KUpdated Oct 5, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC287.7KUpdated Oct 21, 2026

See all skills by affaan-m

Report a problem with this skill