Prediction Market Risk Review

作者 affaan-mef648e01899b无许可证275K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库3天前更新

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.

AI 生成的概览

审查预测市场、篮子、预言机与交易代理工作流中的合规、安全、数据质量、隐私与执行风险。

功能
该技能为预测市场与交易代理工作流提供结构化的前置风险审查。它按审查关卡依次检查建议边界、场所与监管限制、数据质量、安全与隐私,并输出包含审查范围、通过/警告/失败结论、被阻止的操作、所需缓解措施以及安全下一步的报告。当涉及可执行步骤时,它还要求单独的实现计划和用户明确批准。
适用场景
在预测市场工作流涉及场所认证、用户投资组合或财务数据、API 密钥、自动化或交易规划之前使用。它适合作为引入任何可执行工具之前的把关环节。
运行要求
无需脚本或工具,仅为指令型技能。它提及 ITO_API_KEY 和场所 API 密钥等环境变量,这些必须避免出现在日志和文档中,并假定审查者可以访问被审查的工作流。

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.

来源与署名

来源:affaan-m/ecc位于skills/prediction-market-risk-review提交ef648e0

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架