elias/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-23 21:59:30 +08:00
Code Issues Packages Projects Releases Wiki Activity
everything-claude-code/skills/prediction-market-risk-review/SKILL.md
BERORINPO db7f2a6fd5 fix(skills): move top-level origin frontmatter key under metadata 
The official Agent Skills spec (agentskills.io/specification) whitelists exactly
6 top-level frontmatter keys (name/description/license/compatibility/metadata/
allowed-tools). A top-level `origin` key fails the official validator
(anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate).

This moves `origin: X` -> `metadata.origin: X` across the canonical skills/
tree, preserving each value verbatim. Frontmatter-only, minimal diff.

- 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata)
- origin values preserved verbatim (verified 251/251)
- YAML validated on all changed files
- scoped to canonical skills/ only (docs/<lang> translations + tool mirrors
  .cursor/.kiro/.agents left untouched; presumably regenerated from canonical)

Addresses #2233
2026-06-11 21:12:21 +09:00

1.8 KiB
Raw Blame History

name, description, metadata
name description metadata
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.
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:

  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.