How do I install the Gatedata Prediction Markets skill?

Run npx skillmds@latest add gate/gatedata-prediction-markets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gatedata Prediction Markets safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gatedata Prediction Markets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gatedata Prediction Markets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gatedata Prediction Markets?

gate (@gate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gatedata Prediction Markets by gate

Name: Gatedata Prediction Markets
Author: gate

Gatedata Prediction Markets

GateData prediction markets via MCP prediction_markets_query: search events, rankings, market detail, signals, order book. Triggers on 'prediction market', 'Polymarket', 'event odds', 'yes/no price', 'prediction ranking', '预测市场', '事件概率', '成交量排行'.

gate Updated Sep 17, 2026

File contents

GateData Prediction Markets

General Rules

⚠️ STOP — Read gatedata-runtime-rules.md first.

MCP server: GateData (production)
Scope required: prediction
Primary tool: prediction_markets_query (multi-task). Legacy prediction_* names are invoke aliases only — prefer prediction_markets_query + task.

When to use this skill

One tool, routed by task:

User intent	Call
Search events by topic/keyword	`task: search` + `query`
Top events by volume or liquidity	`task: rankings` + `ranking_type`
Full event + child markets	`task: event_detail` + `event_ref`/`event_id`
Model signal / edge on an event	`task: event_signal` + `event_ref`/`event_id`
Single market probability & rules	`task: market` + `market_id`
Yes/no order book	`task: order_book` + `venue` + `market_id`
Event overview	`task: summary`
Let API route from natural query	`task: auto` (default)

Do not call (planned): task: probability_history, task: volume_delta — not live; use market / summary / order_book instead.

Do not use for CEX crypto spot/perp prices → gatedata-market-research.
Do not use for news headlines → gatedata-signals-news.
Ambiguous entity (ticker vs contract) → gatedata-assets-resolve first.

object_refs chaining

task: search or task: rankings emits event / market refs.
Use refs in event_detail, market, event_signal tasks.
task: order_book needs venue + market_id (from prior market detail).

Typical chain: rankings → event_detail → order_book (same tool, changing task).

ranking_type guide

User says	`ranking_type`
"hottest", "top volume", "most traded"	`volume_24h`
"most liquid", "deepest markets"	`liquidity`

Optional: venue, status, limit, include_markets, depth.

Response presentation

Show implied probability / yes-no prices clearly.
Note resolution rules and status when present.
If task: event_signal returns 50301, explain signal is not ready yet.

References

---name: gatedata-prediction-marketsdescription: GateData prediction markets via MCP prediction_markets_query: search events, rankings, market detail, signals, order book. Triggers on 'prediction market', 'Polymarket', 'event odds', 'yes/no price', 'prediction ranking', '预测市场', '事件概率', '成交量排行'.---# GateData Prediction Markets## General Rules⚠️ STOP — Read [gatedata-runtime-rules.md](../gatedata-runtime-rules.md) first.- **MCP server:** `GateData` (production)- **Scope required:** `prediction`- **Primary tool:** `prediction_markets_query` (multi-task). Legacy `prediction_*` names are invoke aliases only — prefer `prediction_markets_query` + `task`.---## When to use this skillOne tool, routed by `task`:| User intent | Call ||-------------|------|| Search events by topic/keyword | `task: search` + `query` || Top events by volume or liquidity | `task: rankings` + `ranking_type` || Full event + child markets | `task: event_detail` + `event_ref`/`event_id` || Model signal / edge on an event | `task: event_signal` + `event_ref`/`event_id` || Single market probability & rules | `task: market` + `market_id` || Yes/no order book | `task: order_book` + `venue` + `market_id` || Event overview | `task: summary` || Let API route from natural query | `task: auto` (default) |**Do not call (planned):** `task: probability_history`, `task: volume_delta` — not live; use `market` / `summary` / `order_book` instead.**Do not use** for CEX crypto spot/perp prices → [gatedata-market-research](../gatedata-market-research/SKILL.md). **Do not use** for news headlines → [gatedata-signals-news](../gatedata-signals-news/SKILL.md). Ambiguous entity (ticker vs contract) → [gatedata-assets-resolve](../gatedata-assets-resolve/SKILL.md) first.---## object_refs chaining1. `task: search` or `task: rankings` emits `event` / `market` refs.2. Use refs in `event_detail`, `market`, `event_signal` tasks.3. `task: order_book` needs `venue` + `market_id` (from prior market detail).Typical chain: `rankings` → `event_detail` → `order_book` (same tool, changing `task`).---## ranking_type guide| User says | `ranking_type` ||-----------|----------------|| "hottest", "top volume", "most traded" | `volume_24h` || "most liquid", "deepest markets" | `liquidity` |Optional: `venue`, `status`, `limit`, `include_markets`, `depth`.---## Response presentation- Show implied probability / yes-no prices clearly.- Note resolution rules and `status` when present.- If `task: event_signal` returns `50301`, explain signal is not ready yet.---## References- [scenarios.md](./references/scenarios.md)- [troubleshooting.md](./references/troubleshooting.md)

Frequently asked questions