Agent Skills
› NeverSight/learn-skills.dev
› prediction-market-risk-review
prediction-market-risk-review
GitHub用于审查预测市场工作流的风险控制技能。在涉及用户财务、身份验证或交易执行前，检查合规性、数据质量、隐私及安全风险，确保输出仅为信息性建议，禁止直接交易指令，并强制要求人工审批与缓解措施。
Trigger Scenarios
处理预测市场工作流
涉及用户金融上下文或账户认证
准备执行交易或访问API密钥
Install
npx skills add NeverSight/learn-skills.dev --skill prediction-market-risk-review -g -y
SKILL.md
Frontmatter
{
"name": "prediction-market-risk-review",
"origin": "ECC",
"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."
}
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.
Version History
- e0220ca Current 2026-07-06 00:00
