elias/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-19 19:30:29 +08:00
Code Issues Packages Projects Releases Wiki Activity
everything-claude-code/skills/ito-market-intelligence/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

2.3 KiB
Raw Blame History

name, description, metadata
name description metadata
ito-market-intelligence Research prediction-market events, venues, underliers, liquidity, and news context for Itô basket workflows. Use for read-only market intelligence, API-gated Itô exploration, and source-grounded prediction-market briefings without investment advice or live trading.
origin
ECC

Itô Market Intelligence

Use this skill when a user wants prediction-market context, event discovery, venue comparison, basket theme exploration, or an Itô API-backed market brief.

This is a public teaser skill. It can work with public sources by default. Any Itô-backed data call requires explicit API access through ITO_API_KEY.

Guardrails

  • Do not provide investment, legal, tax, or trading advice.
  • Do not place, cancel, route, or simulate live orders.
  • Do not infer the user's financial situation unless they provide it.
  • Treat Polymarket, Kalshi, Itô, X, Exa, GitHub, and web data as source inputs, not as truth by themselves.
  • Separate facts, market-implied signals, and your interpretation.

Workflow

  1. Clarify the market theme, venue, geography, and time horizon.
  2. Gather public market data from venue docs/APIs or source-grounded research.
  3. If ITO_API_KEY is present and the user explicitly asks for Itô data, call only read endpoints and state that access is gated.
  4. Normalize event, underlier, liquidity, fee, resolution, and data-latency differences across venues.
  5. Produce a decision brief:
    • market/event summary
    • available venues and underliers
    • liquidity and data-quality caveats
    • relevant news/source context
    • open questions before any user action

Useful Skill Chains

  • Use deep-research or exa-search for source discovery.
  • Use x-api for public social signal discovery when X access is configured.
  • Use market-research for market sizing, competitors, or business use cases.
  • Use prediction-market-risk-review before any workflow touches user capital, portfolio data, or execution-capable credentials.

Output Contract

Default to a compact brief with source links and a clear caveat:

This is market intelligence, not investment or trading advice.

If access is missing, say:

Itô live basket/API data requires gated access. Request an ITO_API_KEY before
using Itô-backed reads.