Gatedata market research

Skill gate/gate-data-ai-agent/skills/gatedata-market-research

GateData market data via MCP: spot/perp prices, K-line, order book, CEX depth, derivatives, liquidation heatmap. Triggers on 'BTC price', 'ETH K-line', 'order book', 'funding rate', 'open interest', 'liquidation', 'how much is', '现价', 'K线', '盘口', '资金费率'.From its SKILL.md

Install

npx -y skills add gate/gate-data-ai-agent --skill gatedata-market-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, 852 tokens by cl100k_base, as published. Nobody here has run it

GateData Market Research

General Rules

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

MCP server: GateData (production)
Scope required: markets
Only call tools listed in this skill. Tool schemas live in MCP tools/list; follow AgentCard hints in descriptions.

When to use this skill

User intent	Primary tool
Current price, 24h change, volume	`markets_get_snapshot`
OHLCV / chart / history	`markets_get_kline`
Single-venue order book, spread	`markets_get_order_book_current`
Recent trades / tape	`markets_get_recent_trades`
Liquidity change over time	`markets_get_liquidity_history`
Cross-venue aggregated depth	`markets_get_cex_depth`
Per-venue funding / OI	`markets_get_cex_derivatives`
Asset-level derivatives summary	`markets_get_derivatives`
Liquidation clusters / heatmap	`markets_get_liquidation_heatmap`

Do not use for prediction markets → gatedata-prediction-markets.
Do not use for news/sentiment → gatedata-signals-news.

object_refs chaining

First call may use query (e.g. BTC, ETH, AAPL).
Read metadata.object_refs from the response.
Pass refs in subsequent calls to avoid re-resolution and 40001 ambiguous errors.

Example chain: markets_get_snapshot → markets_get_kline → markets_get_order_book_current.

Ambiguity handling

When the API returns 40001 or metadata.candidates:

If user named a venue (Binance, Gate), add venue + market_type (spot / perp).
If multiple listings match, ask one clarifying question OR pick listing_id from candidates.
For pairs like ETH_USDT without venue, always disambiguate before order book / kline.

Tool quick reference

Tool	Required inputs	Next tools
`markets_get_snapshot`	`query` or `object_refs`	`markets_get_kline`, `markets_get_order_book_current`
`markets_get_kline`	`timeframe` + symbol/ref	`markets_get_order_book_current`, `markets_get_recent_trades`
`markets_get_order_book_current`	pair/ref; venue if ambiguous	`markets_get_cex_depth`, `markets_get_recent_trades`
`markets_get_recent_trades`	pair/ref	`markets_get_order_book_current`, `markets_get_kline`
`markets_get_liquidity_history`	listing/ref + time range	`markets_get_cex_depth`
`markets_get_cex_depth`	asset/pair/ref	`markets_get_derivatives`
`markets_get_cex_derivatives`	asset/ref	`markets_get_liquidation_heatmap`
`markets_get_derivatives`	asset/ref	`markets_get_liquidation_heatmap`
`markets_get_liquidation_heatmap`	asset/ref	`markets_get_derivatives`

Response presentation

Always show updated_at or candle time when quoting prices.
Mention data_status / limitations if partial or delayed.
Free tier sample symbols: BTC, ETH, SOL (crypto); AAPL, NVDA, TSLA (TradFi).

References

scenarios.md — example dialogues
troubleshooting.md — auth, scope, ambiguity

What ships with it: 2 files

4.5 KB alongside SKILL.md

references/

scenarios.md2.7 KB
troubleshooting.md1.8 KB