L2复合技能 — 编排12个只读MCP工具调用,跨越Gate-Info MCP(8个工具)和Gate-News MCP(4个工具),将多源市场情报聚合为结构化、带引用的报告。
无交易、兑换、质押或任何资金移动操作。
触发场景:用户意图是"研究/理解/分析"——市场概览、单币分析、多币比较、技术趋势、事件归因、风险检查或每日简报。
目标用户:休闲/初学者交易者、内容导向用户以及在行动前需要快速了解市场、币种或风险的决策前用户。
通用规则
⚠️ 停止 — 在继续之前,您必须阅读并严格遵循共享运行时规则。在阅读所有规则之前,请勿选择或调用任何工具。这些规则具有最高优先级。
→ 阅读 gate-runtime-rules.md
- 仅调用本技能明确列出的MCP工具。即使MCP服务器中存在未在此处记录的工具,也不得调用。
MCP依赖
必需的MCP服务器
使用的MCP工具
查询操作(只读)
- info_coin_get_coin_info
- info_compliance_check_token_security
- info_marketsnapshot_get_market_snapshot
- info_markettrend_get_indicator_history
- info_markettrend_get_kline
- info_markettrend_get_technical_analysis
- info_onchain_get_token_onchain
- info_platformmetrics_get_defi_overview
- news_events_get_event_detail
- news_events_get_latest_events
- news_feed_get_social_sentiment
- news_feed_search_news
认证
安装检查
- 必需:Gate-Info
- 安装:为您的IDE运行安装程序技能
- Cursor:
gate-mcp-cursor-installer
- Codex:
gate-mcp-codex-installer
- Claude:
gate-mcp-claude-installer
- OpenClaw:
gate-mcp-openclaw-installer
MCP模式
阅读并严格遵循 references/mcp.md,然后执行本技能的研究助手工作流程。
SKILL.md 保留路由逻辑、信号设计和报告语义。
references/mcp.md 是信号到工具执行、并行策略和回退策略的权威MCP编排层。
领域知识
常见误解
| 误解 | 真相 |
|---|
| "分析BTC然后帮我买入"会触发交易 | 本技能仅产生分析。执行意图被路由到交易技能(例如 gate-exchange-spot)。 |
| 分析结论 = 投资建议 | 输出必须区分"数据驱动分析"和"投资建议"。永不承诺回报。 |
设计原理:5维度信号叠加
用户查询通常跨越多个分析维度(例如,"BTC表现如何?"意味着基本面+技术面+新闻)。强制单一意图分类是脆弱的。本技能使用维度信号叠加而非N选1分类:从查询中独立检测5个信号维度,每个激活的维度贡献一组工具调用,最终工具集是它们的并集。运行5个独立的二分类器比1个九分类器稳定得多。
工具清单(12个唯一工具,全部只读,无需认证)
| # | MCP服务 | 工具名称 | 用途 |
|---|
| 1 | Gate-Info | info_marketsnapshot_get_market_snapshot | 实时币种快照(价格、变化、OI、资金费率) |
| 2 | Gate-Info | info_coin_get_coin_info | 币种基本面(项目、资金、代币经济学) |
| 3 | Gate-Info | info_markettrend_get_kline | K线OHLCV数据 |
| 4 | Gate-Info | info_markettrend_get_indicator_history | 技术指标历史(RSI/MACD/布林带/MA) |
| 5 | Gate-Info | info_markettrend_get_technical_analysis | 多时间周期复合信号 |
| 6 | Gate-Info | info_platformmetrics_get_defi_overview | DeFi概览(TVL、DEX成交量、稳定币供应) |
| 7 | Gate-Info | info_compliance_check_token_security | 代币合约安全审计(30+风险标志) |
| 8 | Gate-Info | info_onchain_get_token_onchain | 链上异常(大额转账、交易所流向) |
| 9 | Gate-News | news_events_get_latest_events | 重大事件列表及影响分析 |
| 10 | Gate-News | news_events_get_event_detail | 事件详情(原因、影响、时间线) |
| 11 | Gate-News | news_feed_search_news | 新闻搜索(按重要性或时间) |
| 12 | Gate-News | news_feed_get_social_sentiment | 社交媒体情绪(KOL数量、倾向) |
L1技能到工具映射
| L1技能 | 使用的工具 |
|---|
| gate-info-marketoverview | info_marketsnapshot_get_market_snapshot, info_platformmetrics_get_defi_overview, news_events_get_latest_events |
| gate-info-coinanalysis | info_coin_get_coin_info, info_marketsnapshot_get_market_snapshot, info_markettrend_get_technical_analysis, news_feed_search_news, news_feed_get_social_sentiment |
| gate-info-trendanalysis | info_markettrend_get_kline, info_markettrend_get_indicator_history, info_markettrend_get_technical_analysis, info_marketsnapshot_get_market_snapshot |
| gate-info-coincompare | info_marketsnapshot_get_market_snapshot x N, info_coin_get_coin_info x N, info_markettrend_get_technical_analysis x N(可选) |
| gate-info-riskcheck | info_compliance_check_token_security, info_coin_get_coin_info |
| gate-news-briefing | news_events_get_latest_events, news_feed_search_news, news_feed_get_social_sentiment |
| gate-news-eventexplain | news_events_get_latest_events, info_marketsnapshot_get_market_snapshot, news_events_get_event_detail, info_onchain_get_token_onchain, news_feed_search_news |
关键参数说明
info_marketsnapshot_get_market_snapshot:始终传递 source="spot" 以避免非标准交易对数据污染。
info_markettrend_get_kline:始终传递 source="spot" — 没有此约束,价格数据可能包含DEX非标准交易对,导致价格错误。这是必需参数。
info_compliance_check_token_security:需要 chain 参数;对主要币种(BTC/ETH)跳过,因为合约审计不适用。
info_onchain_get_token_onchain:某些代币返回空结果——这是预期的;跳过链上部分并注明"链上数据不可用"。
工作流程
有关具体提示示例和每个场景的预期行为,请参见 references/scenarios.md。
MCP工具调用:只有第3步调用Gate-Info/Gate-News MCP工具(info_、news_)。第1、2、4、5步是编排、信号规划、聚合和格式化——这些步骤中无MCP工具调用。
第1步:意图门控 — 研究 vs. 执行
确定用户是想研究还是执行。
- 研究意图(进入本技能):理解、分析、比较、简报、风险检查、趋势、为什么涨跌、情绪、基本面、是否值得买入、概览、报告。
- 执行意图(路由离开):买入、卖出、兑换、质押、转账、提现、下单、平仓。
如果用户混合两者(例如"分析BTC然后买入"),分成两个阶段:在本技能内完成研究阶段,然后将执行阶段路由到适当的交易技能(例如 gate-exchange-spot)。
要提取的关键数据:
intent_type: "research" 或 "execution"
第2步:参数提取与5维度信号检测
从用户查询中提取参数:
symbols[]: 币种代码(0到N)。将项目名称映射到代码(Solana -> SOL, Chainlink -> LINK)。
sector: 可选板块(DeFi、Layer2、Meme等)
time_range: 时间范围(默认24h)
然后独立评估5个信号维度(非排他性,多个可以触发):
| 信号 | 维度 | 触发条件 | 触发关键词(仅说明性英文提示;匹配任何人类语言中的意图,而非字面字符串) | 激活的工具 |
|---|
| S1 | 市场/宏观 | 无特定币种 + 广泛市场关注 | market, overall, sector, broad market, majors, macro, daily brief, today, rates / policy, hot sectors, tape, whole-market view | info_marketsnapshot_get_market_snapshot(BTC/ETH/主流币), info_platformmetrics_get_defi_overview, news_events_get_latest_events |
| S2 | 基本面/项目 | 特定币种 + 项目属性关注 | fundamentals, project, funding, team, tokenomics, worth buying, upside, quality, how is it | info_coin_get_coin_info({symbol}), info_marketsnapshot_get_market_snapshot({symbol}) |
| S3 | 技术面/K线 | 特定币种 + 价格/指标关注;或 用户措辞(任何语言)语义上要求整体/全面读取,包括每个币种的市场或技术立场(通常与基本面一起)。基于意图,而非封闭关键词列表。 | 价格/指标: K-line, candlestick, support, resistance, levels, overbought, oversold, RSI, MACD, Bollinger, technicals, trend, pattern, trajectory, outlook, follow-up path · 整体: comprehensive, holistic, full picture, overall | info_markettrend_get_kline, info_markettrend_get_indicator_history, info_markettrend_get_technical_analysis, info_marketsnapshot_get_market_snapshot |
| S4 | 新闻/情绪/归因 | 事件或原因关注(币种可选) | why pumping, dumping, up, down, reason, catalyst, news, narrative, sentiment, event, what happened, rebound, recovery | news_events_get_latest_events, news_feed_search_news, news_feed_get_social_sentiment, news_events_get_event_detail(条件性), info_onchain_get_token_onchain(条件性) |
| S5 | 安全/风险 | 合约安全/诈骗风险关注;或 用户的措辞(任何语言)语义上表达长期持有正在讨论的代币,或 币种选择(选择/比较哪个币种更优)。使用意图语义,而非固定关键词列表。不要将单独的英文"long-term"本身视为长期持有分支的充分条件,没有更清晰的持有/选择意图。 | 安全: safe, risk, contract security, honeypot, rug, scam, audit, trustworthy, screen, token risk, due diligence · 长期/选择: 从上下文推断含义 — 无封闭关键词列表 | info_compliance_check_token_security, info_coin_get_coin_info |
回退规则(当没有信号明确激活时):
symbols == 0 -> 激活 S1(市场概览)
symbols == 1 -> 激活 S2 + S3(单币全面 = 基本面 + 技术面)
symbols >= 2 -> 激活 S2 x N(多币比较)
symbols >= 2 并且 用户语义上要求全面/整体的多币视图(与单币S2+S3相同意图)-> 也激活 S3 x N(即 S2 x N + S3 x N)
筛选模式(当 symbols == 0 且查询包含筛选提示 — 例如 filter, find, recommend, which, ranking, top, screen, pick, best, shortlist, highest potential):
- 阶段1:激活S1获取主流币快照
- LLM中间聚合:从阶段1结果中提取币种代码
- 阶段2:按剩余信号关键词激活S2/S3/S4/S5
要提取的关键数据:
symbols[]: 币种代码列表
sector: 板块过滤器(如果有)
time_range: 时间范围
activated_signals[]: 激活的信号维度列表(S1-S5)
screening_mode: 布尔值
信号路由示例(英文表述;相同路由逻辑适用于任何语言中的等效问题):
| 用户查询(示例) | symbols | 激活的信号 | 说明 |
|---|
| "How is BTC doing?" | [BTC] | S2 + S3(回退) | 无明确维度关键词;回退:单币全面 |
| "Show me DOT support and resistance" | [DOT] | S3 | 支撑/阻力措辞触发技术面 |
| "DOT support levels plus the latest news" | [DOT] | S3 + S4 | 技术面 + 新闻双重激活 |
| "Why did the market crash yesterday?" | [] | S4 + S1 | 为什么/崩盘触发S4;市场上下文触发S1 |
| "Is sentiment recovering?" | [] | S4(+ S1如果范围是"market") | 恢复/情绪触发S4;如果是市场范围则添加S1 |
| "Is ADA safe?" | [ADA] | S5 | 安全措辞触发安全 |
| "Full weekend research report on XRP — price, news, and risk" | [XRP] | S2 + S3 + S4 + S5 | 完整研究报告意味着所有维度 |
| "Compare BTC, ETH, and SOL" | [BTC,ETH,SOL] | S2 x 3(回退) | 多币,无额外关键词;回退:比较 |
| "Comprehensive comparison of BTC, ETH, and SOL" | [BTC,ETH,SOL] | S2 x 3 + S3 x 3 | 全面多币 -> 叠加每个币种的技术面 |
| "Long-term hold: compare BTC, ETH, and SOL holistically" | [BTC,ETH,SOL] | S2 x 3 + S3 x 3 + S5 x 3 | 长期选择 + 整体视图通常意味着基本面 + 技术面 + 风险 |
| "Daily market brief — majors, hot sectors, drivers, and tomorrow's outlook" | [] | S1 + S4 + S3(BTC) | 宏观简报 + 原因 + 展望 -> S1, S4, 可选S3用于趋势 |
| "Screen the top 5 gainers today and analyze the most promising one" | [] | S1 -> S2 + S3(筛选) | 筛选 + 涨幅最大/潜力 -> P1快照,P2深入分析选中的币种 |
| "Why is DeFi up? Leader coin fundamentals and technicals" | [] (+ sector) | S1 + S4 -> S2 + S3 | 板块 + 为什么 -> S1/S4然后领导币种 -> S2 + S3 |
| "Which coins are oversold? Pick two and analyze them" | [] | S1 -> S3 + S2(筛选) | 开放式which + 超卖/超买 + 选 -> 筛选;P2 S3 + S2 |
| "Check ADA token risk and fundamentals" | [ADA] | S5 + S2 | 尽职调查 + 代币安全 + 基本面 -> S5 + S2 |
第3步:组装工具集并执行
将所有激活信号的工具集合并,按工具名称+参数去重,然后执行:
并行执行(同一阶段内的工具没有依赖——同时调用):
串行依赖(下一阶段依赖上一阶段LLM聚合):
- 筛选模式:阶段1快照结果 -> LLM提取币种 -> 阶段2使用这些币种。
- 归因分支(S4):
news_events_get_latest_events 结果决定是否调用 news_events_get_event_detail(找到事件)或跳过(无事件)。
去重规则:同一请求中相同工具+相同参数只调用一次;结果在多个聚合步骤中重用。
使用以下参数约定调用每个激活的工具:
调用 info_marketsnapshot_get_market_snapshot:
symbol={symbol}, timeframe="1d", source="spot"
调用 info_coin_get_coin_info:
query={symbol}, scope="full"
调用 info_markettrend_get_kline:
symbol={symbol}, timeframe="1d", limit=90, source="spot"
调用 info_markettrend_get_indicator_history:
symbol={symbol}, indicators=["rsi","macd","bollinger","ma"]
调用 info_markettrend_get_technical_analysis:
symbol={symbol}
调用 info_platformmetrics_get_defi_overview:
category="all"
调用 info_compliance_check_token_security:
token={symbol}, chain={chain}
调用 info_onchain_get_token_onchain:
token={symbol}
调用 news_events_get_latest_events:
time_range={time_range}, limit=10
调用 news_events_get_event_detail:
event_id={event_id}
调用 news_feed_search_news:
coin={symbol}, limit=5, sort_by="importance"
调用 news_feed_get_social_sentiment:
coin={symbol}
要提取的关键数据:
tool_results{}: 工具名称到响应数据的映射
failed_tools[]: 超时或返回错误的工具
第4步:LLM多源聚合
将所有工具响应传递给LLM进行聚合:
- 合并所有维度的数据为连贯的叙述。
- 去重重叠信息(例如,多个快照调用中的价格)。
- 冲突解决:如果来源相互矛盾,呈现双方观点并注明出处——永远不要将矛盾结论合并为一句话。
- 数据时间戳:为每个数据点标注其近似数据时间(例如,"截至2026-03-21 12:00 UTC")。不要在输出中包含内部工具名称或API字段名称。
- 缺失数据:如果工具失败或返回空,注明"此部分数据不可用"——永远不要编造数据。
要提取的关键数据:
aggregated_report: 结构化报告内容
data_sources[]: 贡献数据的工具列表
data_timestamps: 近似数据新鲜度
第5步:输出结构化报告
根据激活的信号选择适当的报告模板,然后输出最终报告。始终在末尾包含免责声明。
要提取的关键数据:
final_report: Markdown字符串 — 用户面向的报告正文(模板填充;可能优化第4步的aggregated_report);必须包含标准免责声明。
报告模板
模板A:市场概览简报(S1主导)
## Market Overview BriefData Time: {timestamp}
Market Snapshot
| Metric | Value | 24h Change |
|---|
| BTC | ${btc_price} | {btc_change_24h}% |
| ETH | ${eth_price} | {eth_change_24h}% |
| Total Crypto Market Cap | ${total_mcap} | {mcap_change}% |
| Fear & Greed Index | {fear_greed} | {sentiment_label} |
DeFi Overview
| Metric | Value |
|---|
| Total TVL | ${tvl} |
| DEX 24h Volume | ${dex_volume} |
| Stablecoin Total Supply | ${stablecoin_supply} |
| Long/Short Ratio | {long_short_ratio} |
Key Events (Past 24h)
- {event_title} — {impact_summary}
- ...
Market Sentiment
- Social Sentiment Score: {score} ({bias})
- Key Discussions: {summary of trending topics}
Summary & Outlook
{LLM 3-5 sentence synthesis: current market phase, primary drivers, key risks}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
模板B:单币深度分析(S2+S3主导)
## {symbol} Research ReportData Time: {timestamp}
1. Fundamentals
| Metric | Value |
|---|
| Project | {project_name} |
| Sector | {category} |
| Market Cap | ${market_cap} |
| FDV | ${fdv} |
| Circulating / Total Supply | {circulating} / {total} |
| Key Investors | {investors} |
{Tokenomics summary; flag upcoming large unlocks}2. Market & Technical Analysis
| Metric | Value | Status |
|---|
| Price | ${price} | — |
| 24h Change | {change_24h}% | {Up/Down/Flat} |
| 7d Change | {change_7d}% | {Up/Down/Flat} |
| RSI(14) | {rsi} | {Overbought/Oversold/Neutral} |
Technical Signals:
- Short-term (1h/4h): {signal}
- Medium-term (1d): {signal}
- Support: ${support} | Resistance: ${resistance}
3. News & Sentiment
Recent News:
- {title} — {summary} ({source}, {time})
- ...
Social Sentiment: {sentiment_score} ({bias}) — {summary}
4. Risk Alerts
{Data-driven alerts: RSI extremes, volume anomalies, funding rate, upcoming unlocks, low liquidity}
5. Overall Assessment
{LLM 3-5 sentence synthesis: market phase, drivers, risks}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
模板C:多币比较(S2 x N)
## Multi-Coin Comparison: {coin1} vs {coin2} vs ...Data Time: {timestamp}
Comparison Table
| Metric | {coin1} | {coin2} | {coin3} |
|---|
| Price | ${price1} | ${price2} | ${price3} |
| Market Cap | ${mcap1} | ${mcap2} | ${mcap3} |
| 24h Change | {chg1}% | {chg2}% | {chg3}% |
| RSI(14) | {rsi1} | {rsi2} | {rsi3} |
| Sector | {cat1} | {cat2} | {cat3} |
| Risk Level | {risk1} | {risk2} | {risk3} |
Per-Coin Highlights
{coin1}: {1-2 sentence highlight}
{coin2}: {1-2 sentence highlight}
Comparative Assessment
{LLM analysis: relative strengths/weaknesses, risk comparison, suitability for different strategies}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
模板D:事件归因(S4主导)
## Market Movement AttributionData Time: {timestamp}
What Happened
{Brief description of the price movement or market event}
Root Cause Analysis
- {event/cause 1}: {explanation with data}
- {event/cause 2}: {explanation}
On-Chain Evidence
{On-chain flow data if available, otherwise "On-chain data unavailable"}
Current Sentiment
- Social Score: {score} ({bias})
- Recovery Signal: {recovering/still negative/neutral}
Outlook
{LLM forward-looking assessment based on event + sentiment + technical data}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
模板E:风险检查(S5主导)
## {symbol} Security & Risk ReportData Time: {timestamp}
Contract Security Audit
| Check | Result | Detail |
|---|
| Honeypot | {Yes/No} | {detail} |
| Hidden Owner | {Yes/No} | {detail} |
| Buy/Sell Tax | {buy_tax}% / {sell_tax}% | {normal/abnormal} |
| Holder Concentration | {top10_pct}% | {concentrated/distributed} |
| Overall Risk Level | {Low/Medium/High} | {flags_count} flags |
Fundamentals Cross-Check
| Metric | Value |
|---|
| Project | {project_name} |
| Market Cap | ${market_cap} |
| Active Addresses | {address_count} |
Risk Summary
{LLM synthesis: overall risk assessment, specific concerns, red flags}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
判断逻辑摘要
| 条件 | 操作 |
|---|
| 用户意图是"执行"(买入/卖出/兑换/质押) | 路由到适当的交易技能;不要进入本技能 |
| 用户提及DEX/链上地址/流动性池 | 路由到 gate-dex-market 或DEX相关技能 |
| 无币种且无明确维度关键词 | 回退:激活S1(市场概览) |
| 1个币种且无明确维度关键词 | 回退:激活S2 + S3(单币全面) |
| 2+个币种且无明确维度关键词 | 回退:激活S2 x N(多币比较) |
| 2+个币种且用户语义上要求全面/整体多币分析(相同意图可能以任何语言表达) | 激活S2 x N + S3 x N |
| Symbols == 0 + 筛选关键词(filter/find/top/which) | 进入筛选模式:S1在P1 -> 提取币种 -> P2目标信号 |
| 查询包含"research report"或"full report" | 激活所有信号:S2 + S3 + S4 + S5 |
| 单个工具超时或返回空 | 跳过该维度;注明"此维度暂时不可用" |
| 所有工具失败 | 返回错误;建议稍后重试 |
info_markettrend_get_kline 返回异常价格 | 可能缺少source=spot约束;带参数重试 |
| 用户要求"分析然后买入" | 完成研究(本技能)然后路由执行到交易技能 |
| 多个来源数据矛盾 | 呈现双方观点并注明出处;不要合并 |
错误处理
| 错误类型 | 处理 |
|---|
| 币种未找到 | 请用户验证币种名称或代码 |
| 单个工具超时 | 跳过该维度;注明"此维度暂时不可用" |
| 所有工具失败 | 返回错误消息;建议稍后重试 |
| 未配置Gate-News MCP | 仅使用Gate-Info工具(8个工具);将新闻/情绪部分标记为"无数据" |
| 未配置Gate-Info MCP | 关键—无法继续;引导用户安装Gate-Info MCP |
info_onchain_get_token_onchain返回空 | 某些代币的预期行为;跳过链上部分并注明 |
对BTC/ETH调用info_compliance_check_token_security | 跳过主要币种的合约审计;注明"不适用于原生链资产" |
| 用户询问NFT/期权/其他未覆盖类别 | 说明覆盖范围边界;如有专用技能则路由 |
L1/L2路由策略
当用户查询可以由单个L1技能的工具集处理时(例如,"BTC怎么样?"只需要coinanalysis的5个工具),这个L2仍然作为所有"研究"意图的统一入口点:
- 短路优化:如果激活的信号仅映射到一个L1的工具,只调用该子集并生成报告——无需调用所有12个工具。
- 原则:通过这个L2统一入口确保一致的"研究"体验;在内部,根据需要调用1到12个工具。
DEX/链上边界处理
本技能仅使用Gate-Info MCP和Gate-News MCP。它不包含 gate-dex- 或链上地址跟踪功能。
| 情况 | 检测信号 | 操作 |
|---|
| 用户明确提及DEX | "DEX", "on-chain", "liquidity pool", "Uniswap", "wallet address" | 路由到 gate-dex-market 或DEX技能;不要进入本技能 |
| 模糊的"liquidity"无CEX/DEX上下文 | "this coin's liquidity" | 默认为CEX解释;如果用户澄清DEX,重新路由 |
| 用户询问NFT/期权 | "NFT", "options", "derivatives" | 说明覆盖范围边界;如有专用技能则路由 |
| 用户问"这个币在Gate上架了吗?" | "listed", "can I buy" | 简要上市检查+风险说明;或路由到上市/新币技能 |
| 多语言或混合语言用户输入 | 不适用 | 正常解析意图;如有"研究"意图且无DEX/执行信号,进入本技能 |
无需确认
这个L2不涉及任何交易确认机制,因为:
- 所有12个工具调用都是只读查询(
info_ / news_);零 cex_ 写操作
- 无资产变更、下单、转账或模式切换
- 无需API密钥/密钥/OAuth2
如果用户附加执行意图(例如"分析然后买入"),本技能仅完成研究阶段。执行阶段被路由到适当的交易技能(例如 gate-exchange-spot),该技能应用其自己的操作草稿 -> 用户确认 -> 执行流程。
工具降级矩阵
| 工具 | 降级策略 |
|---|
info_onchain_get_token_onchain | 某些代币返回空;跳过链上部分并注明"链上数据不可用" |
info_compliance_check_token_security | 需要chain参数;对主要币种(BTC/ETH)跳过;注明"不适用于原生链资产" |
news_events_get_event_detail | 依赖P1的event_id;如果P1无事件,跳过(进入P2b分支) |
info_marketsnapshot_get_market_snapshot | 如果超时,重试一次;仍然失败则跳过快照部分 |
| 任何其他工具 | 单个工具失败:跳过该维度,注明"此维度暂时不可用" |
| 所有工具 | 如果所有工具失败:返回错误消息,建议稍后重试 |
跨技能路由
| 用户后续意图 | 路由到 |
|---|
| "买入它" / "下单" | gate-exchange-spot |
| "开期货仓位" | gate-exchange-futures |
| "兑换它" | gate-exchange-flashswap |
| "质押它" | gate-exchange-staking 或 gate-exchange-simpleearn |
| "查看我的资产" | gate-exchange-assets |
| "跟踪这个钱包地址" | gate-info-addresstracker |
| "显示DEX数据" | gate-dex-market |
安全规则
- 无投资建议:所有输出都是数据驱动的分析。每个报告必须包含免责声明:"不构成投资建议"。
- 无价格预测:不要输出具体目标价格或方向性预测(例如"将达到100K美元")。
- 无资金操作:本技能仅调用只读的
info_ 和 news_ 工具。永不调用 cex_ 工具。
- 数据透明度:为每个部分标注近似数据时间(例如"数据截至...")。使用自然语言来源标签(例如"Gate市场数据"、"Gate新闻")而非内部工具名称或API字段名称。永远不要在面向用户的输出中暴露
info_、news_、cex_ 工具标识符或原始JSON字段名称(例如 snapshot_time、total_defi_tvl)。
- 无数据编造:当工具返回空或失败时,清楚说明"数据不可用"——永远不要编造数字。
- 冲突披露:当来源相互矛盾时,呈现双方观点并注明出处,而不是默默选择一方。
- 无需认证:所有12个工具都是公共只读的;无需API密钥或OAuth2。
- 输出中无内部标识符:最终面向用户的报告不得包含任何内部工具名称(例如
info_marketsnapshot_get_market_snapshot、news_events_get_latest_events)、API字段名称(例如 snapshot_time、total_defi_tvl、total_liquidation_24h、market_cap)或MCP服务前缀(info_、news_、cex_*)。仅使用自然语言描述呈现所有数据。工具名称和字段名称是内部编排细节——它们永远不应泄露到报告中。
- 年龄限制:本技能仅面向年满18岁且具有完全民事行为能力的用户,与Gate平台要求一致。
- 数据流声明:所有数据仅通过Gate MCP流向Gate API。不会向第三方传输用户数据。
L2 composite skill — orchestrates 12 read-only MCP Tool Calls across Gate-Info MCP (8 tools) and Gate-News MCP (4 tools) to aggregate multi-source market intelligence into structured, citation-backed reports. No trading, swaps, staking, or any fund-moving operations.
Trigger Scenarios: User intent is "research / understand / analyze" — market overview, single-coin analysis, multi-coin comparison, technical trends, event attribution, risk check, or daily briefing.
Target Users: Casual / beginner traders, content-oriented users, and pre-decision users who need to quickly understand the market, a coin, or risk before acting.
General Rules
⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
Do NOT select or call any tool until all rules are read. These rules have the highest priority.
→ Read gate-runtime-rules.md
- Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they
exist in the MCP server.
MCP Dependencies
Required MCP Servers
| MCP Server | Status |
|---|
| Gate-Info | ✅ Required |
MCP Tools Used
Query Operations (Read-only)
- info_coin_get_coin_info
- info_compliance_check_token_security
- info_marketsnapshot_get_market_snapshot
- info_markettrend_get_indicator_history
- info_markettrend_get_kline
- info_markettrend_get_technical_analysis
- info_onchain_get_token_onchain
- info_platformmetrics_get_defi_overview
- news_events_get_event_detail
- news_events_get_latest_events
- news_feed_get_social_sentiment
- news_feed_search_news
Authentication
Installation Check
- Required: Gate-Info
- Install: Run installer skill for your IDE
- Cursor:
gate-mcp-cursor-installer
- Codex:
gate-mcp-codex-installer
- Claude:
gate-mcp-claude-installer
- OpenClaw:
gate-mcp-openclaw-installerMCP Mode
Read and strictly follow references/mcp.md, then execute this skill's research-copilot workflow.
SKILL.md keeps routing logic, signal design, and report semantics.
references/mcp.md is the authoritative MCP orchestration layer for signal-to-tool execution, parallel strategy, and fallback policy.
Domain Knowledge
Common Misconceptions
| Misconception | Truth |
|---|
| "Analyze BTC then buy it for me" will trigger a trade | This Skill only produces analysis. Execution intent is routed to trading skills (e.g., gate-exchange-spot). |
| Analysis conclusions = investment advice | Output must distinguish "data-driven analysis" from "investment advice". Never promise returns. |
Design Rationale: 5-Dimension Signal Stacking
User queries often span multiple analysis dimensions (e.g., "How is BTC doing?" implies fundamentals + technicals + news). Forcing a single-intent classification is fragile. This Skill uses dimension signal stacking instead of N-choose-1 classification: independently detect 5 signal dimensions from the query, each activated dimension contributes a set of Tool Calls, and the final tool set is their union. Running 5 independent binary classifiers is far more stable than 1 nine-way classifier.
Tool Inventory (12 unique tools, all read-only, no auth required)
| # | MCP Service | Tool Name | Purpose |
|---|
| 1 | Gate-Info | info_marketsnapshot_get_market_snapshot | Real-time coin snapshot (price, change, OI, funding rate) |
| 2 | Gate-Info | info_coin_get_coin_info | Coin fundamentals (project, funding, tokenomics) |
| 3 | Gate-Info | info_markettrend_get_kline | K-line OHLCV data |
| 4 | Gate-Info | info_markettrend_get_indicator_history | Technical indicator history (RSI/MACD/Bollinger/MA) |
| 5 | Gate-Info | info_markettrend_get_technical_analysis | Multi-timeframe composite signals |
| 6 | Gate-Info | info_platformmetrics_get_defi_overview | DeFi overview (TVL, DEX volume, stablecoin supply) |
| 7 | Gate-Info | info_compliance_check_token_security | Token contract security audit (30+ risk flags) |
| 8 | Gate-Info | info_onchain_get_token_onchain | On-chain anomalies (large transfers, exchange flows) |
| 9 | Gate-News | news_events_get_latest_events | Major event list with impact analysis |
| 10 | Gate-News | news_events_get_event_detail | Event detail (cause, impact, timeline) |
| 11 | Gate-News | news_feed_search_news | News search (by importance or time) |
| 12 | Gate-News | news_feed_get_social_sentiment | Social media sentiment (KOL volume, bias) |
L1 Skill to Tool Mapping
| L1 Skill | Tools Used |
|---|
| gate-info-marketoverview | info_marketsnapshot_get_market_snapshot, info_platformmetrics_get_defi_overview, news_events_get_latest_events |
| gate-info-coinanalysis | info_coin_get_coin_info, info_marketsnapshot_get_market_snapshot, info_markettrend_get_technical_analysis, news_feed_search_news, news_feed_get_social_sentiment |
| gate-info-trendanalysis | info_markettrend_get_kline, info_markettrend_get_indicator_history, info_markettrend_get_technical_analysis, info_marketsnapshot_get_market_snapshot |
| gate-info-coincompare | info_marketsnapshot_get_market_snapshot x N, info_coin_get_coin_info x N, info_markettrend_get_technical_analysis x N (optional) |
| gate-info-riskcheck | info_compliance_check_token_security, info_coin_get_coin_info |
| gate-news-briefing | news_events_get_latest_events, news_feed_search_news, news_feed_get_social_sentiment |
| gate-news-eventexplain | news_events_get_latest_events, info_marketsnapshot_get_market_snapshot, news_events_get_event_detail, info_onchain_get_token_onchain, news_feed_search_news |
Key Parameter Notes
info_marketsnapshot_get_market_snapshot: Always pass source="spot" to avoid non-standard pair data contamination.
info_markettrend_get_kline: Always pass source="spot" — without this constraint, price data may include DEX non-standard pairs, producing incorrect prices. This is a mandatory parameter.
info_compliance_check_token_security: Requires chain parameter; skip for major coins (BTC/ETH) where contract audit is not applicable.
info_onchain_get_token_onchain: Some tokens return empty results — this is expected; skip the on-chain section and annotate "On-chain data unavailable".
Workflow
For concrete prompt examples and expected behavior per scenario, see references/scenarios.md.
MCP tool calls: Only Step 3 invokes Gate-Info / Gate-News MCP tools (info_, news_). Steps 1, 2, 4, and 5 are orchestration, signal planning, aggregation, and formatting — no MCP tool call in those steps.
Step 1: Intent Gate — Research vs. Execution
Determine if the user wants to research or execute.
- Research intent (enter this Skill): understand, analyze, compare, briefing, risk check, trend, why pumping/dumping, sentiment, fundamentals, worth buying, overview, report.
- Execution intent (route away): buy, sell, swap, stake, transfer, withdraw, place order, close position.
If the user mixes both (e.g., "analyze BTC then buy"), split into two phases: complete the research phase within this Skill, then route the execution phase to the appropriate trading skill (e.g., gate-exchange-spot).
Key data to extract:
intent_type: "research" or "execution"
Step 2: Parameter Extraction & 5-Dimension Signal Detection
Extract parameters from the user query:
symbols[]: Coin tickers (0 to N). Map project names to tickers (Solana -> SOL, Chainlink -> LINK).
sector: Optional sector (DeFi, Layer2, Meme, etc.)
time_range: Time scope (default 24h)
Then independently evaluate each of the 5 signal dimensions (non-exclusive, multiple can fire):
| Signal | Dimension | Trigger Condition | Trigger Keywords (illustrative English cues only; match intent in any human language, not literal string-only) | Activated Tools |
|---|
| S1 | Market / Macro | No specific coin + broad market focus | market, overall, sector, broad market, majors, macro, daily brief, today, rates / policy, hot sectors, tape, whole-market view | info_marketsnapshot_get_market_snapshot(BTC/ETH/top coins), info_platformmetrics_get_defi_overview, news_events_get_latest_events |
| S2 | Fundamentals / Project | Specific coin + project attribute focus | fundamentals, project, funding, team, tokenomics, worth buying, upside, quality, how is it | info_coin_get_coin_info({symbol}), info_marketsnapshot_get_market_snapshot({symbol}) |
| S3 | Technicals / K-line | Specific coin + price/indicator focus; or user wording (any language) semantically asks for a holistic / comprehensive read that includes market or technical stance per coin (often alongside fundamentals). Intent-based, not a closed keyword list. | Price / indicators: K-line, candlestick, support, resistance, levels, overbought, oversold, RSI, MACD, Bollinger, technicals, trend, pattern, trajectory, outlook, follow-up path · Holistic: comprehensive, holistic, full picture, overall | info_markettrend_get_kline, info_markettrend_get_indicator_history, info_markettrend_get_technical_analysis, info_marketsnapshot_get_market_snapshot |
| S4 | News / Sentiment / Attribution | Event or reason focus (coin optional) | why pumping, dumping, up, down, reason, catalyst, news, narrative, sentiment, event, what happened, rebound, recovery | news_events_get_latest_events, news_feed_search_news, news_feed_get_social_sentiment, news_events_get_event_detail (conditional), info_onchain_get_token_onchain (conditional) |
| S5 | Security / Risk | Contract security / scam-risk focus; or the user’s wording (any language) semantically expresses long-term holding of the token(s) under discussion, or coin selection (choosing / comparing which coin(s) to favor). Use intent semantics, not a fixed keyword list. Do not treat a bare English "long-term" by itself as sufficient for the long-term-holding branch without clearer hold / selection intent. | Security: safe, risk, contract security, honeypot, rug, scam, audit, trustworthy, screen, token risk, due diligence · Long-term / selection: infer meaning from context — no closed keyword list | info_compliance_check_token_security, info_coin_get_coin_info |
Fallback rules (when no signal is explicitly activated):
symbols == 0 -> activate S1 (market overview)
symbols == 1 -> activate S2 + S3 (single-coin comprehensive = fundamentals + technicals)
symbols >= 2 -> activate S2 x N (multi-coin comparison)
symbols >= 2 and the user semantically asks for a comprehensive / holistic multi-coin view (same spirit as single-coin S2+S3) -> also activate S3 x N (i.e. S2 x N + S3 x N)
Screening mode (when symbols == 0 and the query contains screening cues — e.g. filter, find, recommend, which, ranking, top, screen, pick, best, shortlist, highest potential):
- Phase 1: Activate S1 to fetch top-coin snapshots
- LLM intermediate aggregation: Extract symbols from Phase 1 results
- Phase 2: Activate S2/S3/S4/S5 per remaining signal keywords
Key data to extract:
symbols[]: List of coin tickers
sector: Sector filter if any
time_range: Time scope
activated_signals[]: List of activated signal dimensions (S1-S5)
screening_mode: Boolean
Signal Routing Examples (English phrasing; same routing logic applies to equivalent questions in any language):
| User Query (example) | symbols | Activated Signals | Explanation |
|---|
| "How is BTC doing?" | [BTC] | S2 + S3 (fallback) | No explicit dimension keywords; fallback: single-coin comprehensive |
| "Show me DOT support and resistance" | [DOT] | S3 | Support / resistance wording triggers Technicals |
| "DOT support levels plus the latest news" | [DOT] | S3 + S4 | Technicals + News dual activation |
| "Why did the market crash yesterday?" | [] | S4 + S1 | Why / crash triggers S4; market context triggers S1 |
| "Is sentiment recovering?" | [] | S4 (+ S1 if "market" scope) | Recovery / sentiment triggers S4; add S1 if query is market-wide |
| "Is ADA safe?" | [ADA] | S5 | Safety wording triggers Security |
| "Full weekend research report on XRP — price, news, and risk" | [XRP] | S2 + S3 + S4 + S5 | Full research report implies all dimensions |
| "Compare BTC, ETH, and SOL" | [BTC,ETH,SOL] | S2 x 3 (fallback) | Multi-coin, no extra keywords; fallback: comparison |
| "Comprehensive comparison of BTC, ETH, and SOL" | [BTC,ETH,SOL] | S2 x 3 + S3 x 3 | Comprehensive multi-coin -> stack technicals per coin |
| "Long-term hold: compare BTC, ETH, and SOL holistically" | [BTC,ETH,SOL] | S2 x 3 + S3 x 3 + S5 x 3 | Long-term selection + holistic view often implies fundamentals + technicals + risk |
| "Daily market brief — majors, hot sectors, drivers, and tomorrow's outlook" | [] | S1 + S4 + S3(BTC) | Macro brief + causes + outlook -> S1, S4, optional S3 for trend |
| "Screen the top 5 gainers today and analyze the most promising one" | [] | S1 -> S2 + S3 (screening) | Screening + top gainers / potential -> P1 snapshots, P2 deep dive on picked symbol |
| "Why is DeFi up? Leader coin fundamentals and technicals" | [] (+ sector) | S1 + S4 -> S2 + S3 | Sector + why -> S1/S4 then leader symbol -> S2 + S3 |
| "Which coins are oversold? Pick two and analyze them" | [] | S1 -> S3 + S2 (screening) | Open-ended which + oversold/overbought + pick -> screening; P2 S3 + S2 |
| "Check ADA token risk and fundamentals" | [ADA] | S5 + S2 | Due diligence + token safety + fundamentals -> S5 + S2 |
Step 3: Assemble Tool Set & Execute
Combine all activated signal tool sets into a union, deduplicate by tool name + parameters, then execute:
Parallel execution (tools within the same Phase have no dependencies — call simultaneously):
- All tools in a Phase are dispatched in parallel.
Serial dependencies (next Phase depends on previous Phase LLM aggregation):
- Screening mode: Phase 1 snapshot results -> LLM extracts symbols -> Phase 2 uses those symbols.
- Attribution branch (S4):
news_events_get_latest_events result determines whether to call news_events_get_event_detail (event found) or skip (no event).
Deduplication rule: Same tool + same parameters within one request is called only once; the result is reused across multiple aggregation steps.
Call each activated tool with the parameter conventions below:
Call info_marketsnapshot_get_market_snapshot with: symbol={symbol}, timeframe="1d", source="spot"
Call info_coin_get_coin_info with: query={symbol}, scope="full"
Call info_markettrend_get_kline with: symbol={symbol}, timeframe="1d", limit=90, source="spot"
Call info_markettrend_get_indicator_history with: symbol={symbol}, indicators=["rsi","macd","bollinger","ma"]
Call info_markettrend_get_technical_analysis with: symbol={symbol}
Call info_platformmetrics_get_defi_overview with: category="all"
Call info_compliance_check_token_security with: token={symbol}, chain={chain}
Call info_onchain_get_token_onchain with: token={symbol}
Call news_events_get_latest_events with: time_range={time_range}, limit=10
Call news_events_get_event_detail with: event_id={event_id}
Call news_feed_search_news with: coin={symbol}, limit=5, sort_by="importance"
Call news_feed_get_social_sentiment with: coin={symbol}
Key data to extract:
tool_results{}: Map of tool name to response data
failed_tools[]: Tools that timed out or returned errors
Step 4: LLM Multi-Source Aggregation
Pass all tool responses to the LLM for aggregation:
- Merge data from all dimensions into a coherent narrative.
- Deduplicate overlapping information (e.g., price from multiple snapshot calls).
- Conflict resolution: If sources contradict each other, present both viewpoints with attribution — never merge contradictory conclusions into one sentence.
- Data timestamp: Label each data point with its approximate data time (e.g., "as of 2026-03-21 12:00 UTC"). Do NOT include internal tool names or API field names in the output.
- Missing data: If a tool failed or returned empty, annotate "Data unavailable for this section" — never fabricate data.
Key data to extract:
aggregated_report: Structured report content
data_sources[]: List of tools that contributed data
data_timestamps: Approximate data freshness
Step 5: Output Structured Report
Select the appropriate report template based on the activated signals, then output the final report. Always include the disclaimer at the end.
Key data to extract:
final_report: Markdown string — user-facing report body (template-filled; may refine aggregated_report from Step 4); must include the standard disclaimer.
Report Template
Template A: Market Overview Brief (S1 dominant)
## Market Overview BriefData Time: {timestamp}
Market Snapshot
| Metric | Value | 24h Change |
|---|
| BTC | ${btc_price} | {btc_change_24h}% |
| ETH | ${eth_price} | {eth_change_24h}% |
| Total Crypto Market Cap | ${total_mcap} | {mcap_change}% |
| Fear & Greed Index | {fear_greed} | {sentiment_label} |
DeFi Overview
| Metric | Value |
|---|
| Total TVL | ${tvl} |
| DEX 24h Volume | ${dex_volume} |
| Stablecoin Total Supply | ${stablecoin_supply} |
| Long/Short Ratio | {long_short_ratio} |
Key Events (Past 24h)
- {event_title} — {impact_summary}
- ...
Market Sentiment
- Social Sentiment Score: {score} ({bias})
- Key Discussions: {summary of trending topics}
Summary & Outlook
{LLM 3-5 sentence synthesis: current market phase, primary drivers, key risks}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
Template B: Single-Coin Deep Dive (S2+S3 dominant)
## {symbol} Research ReportData Time: {timestamp}
1. Fundamentals
| Metric | Value |
|---|
| Project | {project_name} |
| Sector | {category} |
| Market Cap | ${market_cap} |
| FDV | ${fdv} |
| Circulating / Total Supply | {circulating} / {total} |
| Key Investors | {investors} |
{Tokenomics summary; flag upcoming large unlocks}2. Market & Technical Analysis
| Metric | Value | Status |
|---|
| Price | ${price} | — |
| 24h Change | {change_24h}% | {Up/Down/Flat} |
| 7d Change | {change_7d}% | {Up/Down/Flat} |
| RSI(14) | {rsi} | {Overbought/Oversold/Neutral} |
Technical Signals:
- Short-term (1h/4h): {signal}
- Medium-term (1d): {signal}
- Support: ${support} | Resistance: ${resistance}
3. News & Sentiment
Recent News:
- {title} — {summary} ({source}, {time})
- ...
Social Sentiment: {sentiment_score} ({bias}) — {summary}
4. Risk Alerts
{Data-driven alerts: RSI extremes, volume anomalies, funding rate, upcoming unlocks, low liquidity}
5. Overall Assessment
{LLM 3-5 sentence synthesis: market phase, drivers, risks}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
Template C: Multi-Coin Comparison (S2 x N)
## Multi-Coin Comparison: {coin1} vs {coin2} vs ...Data Time: {timestamp}
Comparison Table
| Metric | {coin1} | {coin2} | {coin3} |
|---|
| Price | ${price1} | ${price2} | ${price3} |
| Market Cap | ${mcap1} | ${mcap2} | ${mcap3} |
| 24h Change | {chg1}% | {chg2}% | {chg3}% |
| RSI(14) | {rsi1} | {rsi2} | {rsi3} |
| Sector | {cat1} | {cat2} | {cat3} |
| Risk Level | {risk1} | {risk2} | {risk3} |
Per-Coin Highlights
{coin1}: {1-2 sentence highlight}
{coin2}: {1-2 sentence highlight}
Comparative Assessment
{LLM analysis: relative strengths/weaknesses, risk comparison, suitability for different strategies}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
Template D: Event Attribution (S4 dominant)
## Market Movement AttributionData Time: {timestamp}
What Happened
{Brief description of the price movement or market event}
Root Cause Analysis
- {event/cause 1}: {explanation with data}
- {event/cause 2}: {explanation}
On-Chain Evidence
{On-chain flow data if available, otherwise "On-chain data unavailable"}
Current Sentiment
- Social Score: {score} ({bias})
- Recovery Signal: {recovering/still negative/neutral}
Outlook
{LLM forward-looking assessment based on event + sentiment + technical data}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
Template E: Risk Check (S5 dominant)
## {symbol} Security & Risk ReportData Time: {timestamp}
Contract Security Audit
| Check | Result | Detail |
|---|
| Honeypot | {Yes/No} | {detail} |
| Hidden Owner | {Yes/No} | {detail} |
| Buy/Sell Tax | {buy_tax}% / {sell_tax}% | {normal/abnormal} |
| Holder Concentration | {top10_pct}% | {concentrated/distributed} |
| Overall Risk Level | {Low/Medium/High} | {flags_count} flags |
Fundamentals Cross-Check
| Metric | Value |
|---|
| Project | {project_name} |
| Market Cap | ${market_cap} |
| Active Addresses | {address_count} |
Risk Summary
{LLM synthesis: overall risk assessment, specific concerns, red flags}
Data sourced from Gate-Info MCP and Gate-News MCP. Analysis is data-driven and does not constitute investment advice.
Judgment Logic Summary
| Condition | Action |
|---|
| User intent is "execute" (buy/sell/swap/stake) | Route to appropriate trading skill; do NOT enter this Skill |
| User mentions DEX / on-chain address / liquidity pool | Route to gate-dex-market or DEX-related skill |
| No symbols and no explicit dimension keywords | Fallback: activate S1 (market overview) |
| 1 symbol and no explicit dimension keywords | Fallback: activate S2 + S3 (single-coin comprehensive) |
| 2+ symbols and no explicit dimension keywords | Fallback: activate S2 x N (multi-coin comparison) |
| 2+ symbols and user semantically asks for comprehensive/holistic multi-coin analysis (same intent may be expressed in any language) | Activate S2 x N + S3 x N |
| Symbols == 0 + screening keywords (filter/find/top/which) | Enter screening mode: S1 in P1 -> extract symbols -> targeted signals in P2 |
| Query contains "research report" or "full report" | Activate all signals: S2 + S3 + S4 + S5 |
| A single tool times out or returns empty | Skip that dimension; annotate "Data unavailable" |
| All tools fail | Return error; suggest retry later |
info_markettrend_get_kline returns abnormal prices | Likely missing source=spot constraint; retry with parameter |
| User asks "analyze then buy" | Complete research (this Skill) then route execution to trading skill |
| Contradictory data from multiple sources | Present both viewpoints with attribution; do not merge |
Error Handling
| Error Type | Handling |
|---|
| Coin not found | Ask user to verify the coin name or ticker |
| Single tool timeout | Skip that dimension; note "This dimension is temporarily unavailable" |
| All tools fail | Return error message; suggest retry later |
| No Gate-News MCP configured | Use only Gate-Info tools (8 tools); mark news/sentiment sections as "No data" |
| No Gate-Info MCP configured | Critical — cannot proceed; guide user to install Gate-Info MCP |
info_onchain_get_token_onchain returns empty | Expected for some tokens; skip on-chain section with note |
info_compliance_check_token_security on BTC/ETH | Skip contract audit for major coins; note "Not applicable for native chain assets" |
| User asks about NFT / options / other uncovered categories | Explain coverage boundary; route to specialized skill if available |
L1/L2 Routing Strategy
When a user query can be handled by a single L1 Skill's tool set (e.g., "How is BTC?" only needs coinanalysis's 5 tools), this L2 still serves as the unified entry point for all "research" intents:
- Short-circuit optimization: If the activated signals map to only one L1's tools, call only that subset and produce the report — no need to invoke all 12 tools.
- Principle: Unified entry via this L2 ensures consistent "research" experience; internally, 1 to 12 tools are called as needed.
DEX / On-Chain Boundary Handling
This Skill uses only Gate-Info MCP and Gate-News MCP. It does not include gate-dex- or on-chain address tracking capabilities.
| Situation | Detection Signal | Action |
|---|
| User mentions DEX explicitly | "DEX", "on-chain", "liquidity pool", "Uniswap", "wallet address" | Route to gate-dex-market or DEX skill; do NOT enter this Skill |
| Ambiguous "liquidity" without CEX/DEX context | "this coin's liquidity" | Default to CEX interpretation; if user clarifies DEX, re-route |
| User asks about NFT / options | "NFT", "options", "derivatives" | Explain coverage boundary; route to specialized skill if available |
| User asks "Is this coin listed on Gate?" | "listed", "can I buy" | Brief listing check + risk note; or route to listing/new-coin skill |
| Multi-language or mixed-language user input | N/A | Parse intent normally; if "research" intent with no DEX/execution signals, enter this Skill |
No Confirmation Required
This L2 does not involve any trading confirmation mechanism because:
- All 12 Tool Calls are read-only queries (
info_ / news_); zero cex_ write operations
- No asset changes, order placement, transfers, or mode switches
- No API Key / Secret / OAuth2 required
If the user appends execution intent (e.g., "analyze then buy"), this Skill completes the research phase only. The execution phase is routed to the appropriate trading skill (e.g., gate-exchange-spot), which applies its own Action Draft -> User Confirm -> Execute flow.
Tool Degradation Matrix
| Tool | Degradation Strategy |
|---|
info_onchain_get_token_onchain | Some tokens return empty; skip on-chain section and annotate "On-chain data unavailable" |
info_compliance_check_token_security | Requires chain parameter; skip for major coins (BTC/ETH); annotate "Not applicable for native chain assets" |
news_events_get_event_detail | Depends on event_id from P1; if no events in P1, skip (go to P2b branch) |
info_marketsnapshot_get_market_snapshot | If timeout, retry once; if still fails, skip snapshot section |
| Any other tool | Single tool failure: skip that dimension, annotate "This dimension is temporarily unavailable" |
| All tools | If all tools fail: return error message, suggest retry later |
Cross-Skill Routing
| User Follow-up Intent | Route To |
|---|
| "Buy it" / "Place an order" | gate-exchange-spot |
| "Open a futures position" | gate-exchange-futures |
| "Swap it" | gate-exchange-flashswap |
| "Stake it" | gate-exchange-staking or gate-exchange-simpleearn |
| "Check my assets" | gate-exchange-assets |
| "Track this wallet address" | gate-info-addresstracker |
| "Show DEX data" | gate-dex-market |
Safety Rules
- No investment advice: All output is data-driven analysis. Every report must include the disclaimer: "does not constitute investment advice."
- No price predictions: Do not output specific target prices or directional predictions (e.g., "will reach $100K").
- No fund operations: This Skill calls only read-only
info_ and news_ tools. Never call cex_ tools.
- Data transparency: Label approximate data time for each section (e.g., "Data as of ..."). Use natural-language source labels (e.g., "Gate market data", "Gate news") instead of internal tool names or API field names. Never expose
info_, news_, cex_ tool identifiers or raw JSON field names (e.g., snapshot_time, total_defi_tvl) in user-facing output.
- No data fabrication: When a tool returns empty or fails, clearly state "Data unavailable" — never fabricate numbers.
- Conflict disclosure: When sources contradict, present both sides with attribution rather than silently picking one.
- No auth required: All 12 tools are public read-only; no API Key or OAuth2 is needed.
- No internal identifiers in output: The final user-facing report must NOT contain any internal tool names (e.g.,
info_marketsnapshot_get_market_snapshot, news_events_get_latest_events), API field names (e.g., snapshot_time, total_defi_tvl, total_liquidation_24h, market_cap), or MCP service prefixes (info_, news_, cex_*). Present all data using natural-language descriptions only. Tool names and field names are internal orchestration details — they must never leak into the report.
- Age restriction: This skill is intended for users aged 18 or above with full civil capacity, consistent with Gate's platform requirements.
- Data flow declaration: All data flows exclusively through Gate MCP to Gate API. No user data is transmitted to third parties.