Back to Details

gate-info-web3

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

gate-info-web3

gate-info-web3

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 → Also read info-news-runtime-rules.md for gate-info and gate-news shared rules (tool degradation, report standards, security, routing).
  • 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.
⚠️ 停止操作 — 在继续之前，你必须阅读并严格遵守共享运行时规则。 在未读完所有规则前，请勿选择或调用任何工具。这些规则具有最高优先级。 → 阅读 gate-runtime-rules.md → 同时阅读 info-news-runtime-rules.md 以了解gate-info和gate-news的共享规则（工具降级、报告标准、安全、路由）。
  • 仅调用本Skill中明确列出的MCP工具。即使MCP服务器中存在未在此处记录的工具，也不得调用。

CLI and playbook contract

CLI与剧本约定

  1. Scope naming: Frame answers as Web3 / on-chain / protocol behavior. Do not narrow the narrative to “DeFi-only” unless the user’s question is strictly DeFi/TVL/yield. 
    gate-info-defianalysis
    is a legacy alias for routing only — the canonical skill id is 
    gate-info-web3
    .
  2. Legacy commands MUST exist under 
    gate-cli v0.5.2
    . When 
    shortcuts_enabled
    (
    >= 0.7.6
    ), use playbook 
    shortcut
    / 
    additional_shortcut
    blocks; otherwise legacy 
    commands
    . When preflight 
    route
    is 
    CLI
    , do not invoke Gate MCP tools from this skill.
  3. Always pass 
    --format json
     on data-collection commands.
  4. Separate evidence types in the report: label on-chain / CLI facts vs community or media interpretation (news, web search, UGC). Never present rumor as chain truth.
  5. Required slots (
    address
    +
    chain
    , 
    token
    +
    chain
    , 
    platform
    , 
    exchange
    +
    asset
    , 
    symbol
    , 
    entity_query
    ) must be explicit; if ambiguous, ask — do not guess chain or contract.
  6. Final user-facing reports may use the user’s locale; this 
    SKILL.md
    stays English for discovery (see repository 
    CLAUDE.md
    rule 1).
  1. 范围命名：将回答表述为Web3 / 链上 / 协议行为相关内容。除非用户的问题严格围绕DeFi/TVL/收益，否则不要将叙述范围限定为“仅DeFi”。
    gate-info-defianalysis
    仅作为路由使用的旧版别名——标准Skill ID为
    gate-info-web3
    。
  2. 旧版命令必须兼容**
    gate-cli v0.5.2
    **。当
    shortcuts_enabled
    （版本
    >= 0.7.6
    ）时，使用剧本的
    shortcut
    / 
    additional_shortcut
    块；否则使用旧版
    commands
    。当预检查
    route
    为
    CLI
    时，请勿从此Skill调用Gate MCP工具。
  3. 在数据收集命令中始终添加**
    --format json
    **参数。
  4. 区分证据类型：在报告中标记链上 / CLI事实与社区或媒体解读（新闻、网页搜索、UGC）。绝不能将谣言当作链上事实呈现。
  5. 必填参数（
    address
    +
    chain
    、
    token
    +
    chain
    、
    platform
    、
    exchange
    +
    asset
    、
    symbol
    、
    entity_query
    ）必须明确；若存在歧义，请询问用户——切勿猜测链或合约。
  6. 最终面向用户的报告可使用用户的语言环境；本
    SKILL.md
    保持英文以便检索（参见仓库
    CLAUDE.md
    规则1）。

Step 0 — Preflight

步骤0 — 预检查

Follow skills/_shared/preflight.md verbatim:
  1. Run 
    gate-cli preflight --format json
    ; parse 
    .route
    , 
    .status
    , 
    .user_message
    .
  2. Branch: 
    CLI
    → continue; 
    MCP_FALLBACK
    → emit 
    __FALLBACK__
    and halt; 
    BLOCK
    → echo 
    user_message
    and halt.
  3. When 
    status == "ready_with_migration_warning"
    , Step 3 appends one migrate hint at the end of the report.
  4. Step 0.5: Set 
    cli_version
    and 
    shortcuts_enabled
    per skills/_shared/cli-version-routing.md.
Do NOT run any 
info
/ 
news
data call until 
route == "CLI"
.
<!-- Step 0.5 — Skill update check (OPT-IN, disabled by default). See [skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md). -->
严格遵循 skills/_shared/preflight.md：
  1. 运行
    gate-cli preflight --format json
    ；解析
    .route
    、
    .status
    、
    .user_message
    字段。
  2. 分支处理：
    CLI
    → 继续；
    MCP_FALLBACK
    → 输出
    __FALLBACK__
    并终止；
    BLOCK
    → 回显
    user_message
    并终止。
  3. 当
    status == "ready_with_migration_warning"
    时，步骤3需在报告末尾添加一条迁移提示。
  4. 步骤0.5：根据 skills/_shared/cli-version-routing.md 设置
    cli_version
    和
    shortcuts_enabled
    。
在
route == "CLI"
之前，请勿运行任何
info
/ 
news
数据调用。
<!-- 步骤0.5 — Skill更新检查（可选，默认禁用）。参见 [skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md)。 -->

Step 1 — Intent routing

步骤1 — 意图路由

Map the user query to exactly one playbook id from playbooks/gate-info-web3.yaml.
Playbook idWhen to pickRequired slots
address_tracking
Trace a wallet / “who is this address” / recent on-chain activity (behavior, not safety verdict).
address
, 
chain
token_onchain
Token-level flow / holders / smart-money style signals for a known token + chain.
token
, 
chain
entity_intel
Named desk / fund / entity (e.g. what a named desk is doing).
entity_query
protocol_platform
Protocol TVL, fees, volume, profile, history, or yield on a named platform (e.g. Uniswap, Aave).
platform
exchange_reserves
Exchange reserve / proof-of-reserves style questions for an asset.
exchange
, 
asset
liquidation_heatmap
Perp / futures liquidation density by price (which price levels see liquidations).
symbol
stablecoin_bridge
Stablecoin market / peg / chain distribution, or bridge rankings — not a single-token DEX question.—
token_onchain_social
User wants on-chain data plus news/sentiment/UGC in one pass.
token
, 
chain
将用户查询映射到 playbooks/gate-info-web3.yaml 中恰好一个剧本ID。
剧本ID适用场景必填参数
address_tracking
追踪钱包 / “该地址归属方” / 近期链上活动（行为分析，非安全判定）。
address
, 
chain
token_onchain
已知代币+链的代币级流向 / 持有者 / 聪明资金风格信号分析。
token
, 
chain
entity_intel
知名机构 / 基金 / 实体相关查询（例如某知名机构的动向）。
entity_query
protocol_platform
知名平台（如Uniswap、Aave）的协议TVL、手续费、交易量、概况、历史或收益情况。
platform
exchange_reserves
交易所储备金 / 储备证明类资产相关问题。
exchange
, 
asset
liquidation_heatmap
永续合约 / 期货按价格划分的清算密度（哪些价格区间会出现清算）。
symbol
stablecoin_bridge
稳定币市场 / 锚定情况 / 链上分布，或桥接排名——非单一代币DEX问题。—
token_onchain_social
用户希望一次性获取链上数据 + 新闻/舆情/UGC内容。
token
, 
chain

Slot extraction notes

参数提取说明

  • chain
    : normalize to ids the CLI accepts (
    eth
    , 
    bsc
    , 
    arbitrum
    , 
    base
    , 
    solana
    , ...). If missing, ask.
  • platform
    : accept fuzzy names; if multiple matches are plausible, run 
    gate-cli info platformmetrics search-platforms
    only with flags verified in 
    gate-cli info platformmetrics search-platforms --help
    , pick one slug, then run 
    get-defi-overview
    / 
    get-platform-info
    / 
    get-yield-pools
    as the playbook lists.
  • token
    vs 
    symbol
    : on-chain playbooks use 
    token
    (+ 
    chain
    ); reserves / heatmap often use listed 
    symbol
     (e.g. 
    BTC
    , 
    USDC
    ).
  • chain
    ：标准化为CLI可接受的ID（
    eth
    、
    bsc
    、
    arbitrum
    、
    base
    、
    solana
    等）。若缺失，请询问用户。
  • platform
    ：接受模糊名称；若存在多个合理匹配项，仅使用
    gate-cli info platformmetrics search-platforms --help
    中验证过的标志运行该命令，选择一个slug，然后按照剧本列表运行
    get-defi-overview
    / 
    get-platform-info
    / 
    get-yield-pools
    。
  • token
    vs 
    symbol
    ：链上剧本使用
    token
    （+
    chain
    ）；储备金 / 热力图通常使用上市**
    symbol
    **（如
    BTC
    、
    USDC
    ）。

Cross-skill routing at Step 1

步骤1的跨Skill路由

User signalRoute to
Safety / honeypot / blacklist / compliance verdict (safety-first)
gate-info-risk
(primary)
General research, fundamentals, macro, multi-coin compare without on-chain/protocol framing
gate-info-research
(primary)
Pure “why did it move”, “community narrative”, no on-chain ask
gate-news-intel
(primary)
用户信号路由至
安全 / 蜜罐 / 黑名单 / 合规判定（安全优先）
gate-info-risk
（首选）
通用研究、基本面、宏观、多币种对比，无链上/协议相关框架
gate-info-research
（首选）
单纯询问“为何涨跌”、“社区舆论”，无链上需求
gate-news-intel
（首选）

Step 2 — Data collection

步骤2 — 数据收集

Execute the chosen playbook. Commands in the same 
parallel_group
may run concurrently; wait for the group before the next.
执行选定的剧本。同一
parallel_group
中的命令可并行运行；需等待该组命令完成后再执行下一组。

Shortcut routing (gate-cli >= 0.7.6)

快捷指令路由（gate-cli >= 0.7.6）

When 
shortcuts_enabled
, run playbook 
shortcut
blocks per skills/_shared/cli-version-routing.md:
PlaybookShortcut
address_tracking
info +address-tracker
token_onchain
info +token-onchain
token_onchain_social
+token-onchain
then 
+community-scan
when 
symbol_present
(
coin: {symbol}
); resolve ticker from 
coin_context
when 
token
is 
contract_address
. 
+community-scan
covers UGC/X/sentiment only — 
news_brief
(search-news headlines) runs via 
post_shortcut_optional_ids
. All news ids require 
symbol_present
; skip them if unresolved (do not pass contract to 
--coin
).
Note 
missing_sections
may include 
trace-fund-flow
or 
smart_money
— cite in report.
当
shortcuts_enabled
时，根据 skills/_shared/cli-version-routing.md 运行剧本的
shortcut
块：
剧本快捷指令
address_tracking
info +address-tracker
token_onchain
info +token-onchain
token_onchain_social
当
symbol_present
（
coin: {symbol}
）时，先运行
+token-onchain
再运行
+community-scan
；当
token
为
contract_address
时，从
coin_context
解析代码。
+community-scan
仅覆盖UGC/X/舆情内容——
news_brief
（搜索新闻头条）通过
post_shortcut_optional_ids
运行。所有新闻ID均要求
symbol_present
；若无法解析则跳过（请勿将合约地址传入
--coin
参数）。
注意
missing_sections
可能包含
trace-fund-flow
或
smart_money
——需在报告中注明。

Legacy-only paths

仅旧版路径

  • info onchain trace-fund-flow
     and 
    info onchain get-entity-profile
    : not shipped. Use 
    get-address-info
    + 
    get-address-transactions
     or 
    news feed web-search
    .
  • Below 0.7.6, use legacy 
    commands
    in the playbook YAML (plus optional 
    search-platforms
    pre-check for fuzzy 
    platform
    names).
  • info onchain trace-fund-flow
     和 
    info onchain get-entity-profile
    ：未发布。使用**
    get-address-info
    + 
    get-address-transactions
    ** 或 **
    news feed web-search
    **替代。
  • 版本低于0.7.6时，使用剧本YAML中的旧版
    commands
    （若平台名称模糊，可额外运行
    search-platforms
    预检查）。

Failure policy

失败处理规则

  • Required command fails → abort, surface CLI error, no fabricated section.
  • Optional command fails → mark the matching subsection as no data in Step 3.
  • News/web search may be partial or opinion-heavy — tag those lines as community / media, not as on-chain facts.
  • 必填命令失败 → 终止操作，显示CLI错误，不得编造内容。
  • 可选命令失败 → 在步骤3中标记对应小节为无数据。
  • 新闻/网页搜索结果可能不完整或带有主观倾向——需将这些内容标记为社区 / 媒体内容，而非链上事实。

Step 3 — Synthesis

步骤3 — 内容合成

Produce exactly six sections, in this order (section titles in the final user report may be localized; structure is fixed):
生成恰好六个小节，按以下顺序排列（最终用户报告中的小节标题可本地化，但结构固定）：

Report template

报告模板

markdown
undefined
markdown
undefined

Web3 intel — {subject}

Web3情报 — {subject}

1. Subject and executive takeaways

1. 研究主体与核心结论

  • Objects (address / token / protocol / exchange / entity / theme)
  • 1–3 neutral bullets; separate on-chain verifiable vs needs confirmation
  • 对象（地址 / 代币 / 协议 / 交易所 / 实体 / 主题）
  • 1–3条中立要点；区分链上可验证与需确认内容

2. On-chain activity (core)

2. 链上活动（核心）

  • Recent interaction types, large transfers, label-based identity hints — only from on-chain / 
    info onchain
    commands
  • 近期交互类型、大额转账、基于标签的身份线索 — 仅来自链上 / 
    info onchain
    命令

3. Flows, positioning, smart money, entity read

3. 资金流向、持仓分布、聪明资金与实体分析

  • Flow and holder / positioning structure (
    get-address-transactions
    , 
    get-token-onchain
    )
  • Smart-money or whale-style signals (from token-onchain data)
  • Entity questions: if 
    web-search
    is used, mark as second-hand narrative
  • 资金流向与持有者/持仓结构（来自
    get-address-transactions
    、
    get-token-onchain
    ）
  • 聪明资金或巨鲸风格信号（来自代币链上数据）
  • 实体相关问题：若使用
    web-search
    ，需标记为二手信息

4. Protocol or platform metrics (if relevant)

4. 协议或平台指标（如适用）

  • Scale (TVL, volume, fees), direction of change, pools or assets that matter (
    platformmetrics
    commands)
  • 规模（TVL、交易量、手续费）、变化趋势、关键资金池或资产（来自
    platformmetrics
    命令）

5. Community or news context (if relevant)

5. 社区或新闻背景（如适用）

  • Only when the playbook includes news / web-search: short factual + tone summary; keep separate from sections 2–3
  • 仅当剧本包含新闻/网页搜索时添加：简短事实+语气总结；与第2–3小节分开呈现

6. Risks and watchlist

6. 风险与关注清单

  • Data gaps, follow-up on-chain signals, non-advice watch items
This report is based on public data and tool output; it is not investment advice.
undefined
  • 数据缺口、需跟进的链上信号、非建议性关注项
本报告基于公开数据与工具输出，不构成投资建议。
undefined

Migrate hint (only if Step 0 had 
ready_with_migration_warning
)

迁移提示（仅当步骤0中
status == ready_with_migration_warning
时添加）

Append verbatim the migration blockquote line from skills/_shared/report-style.md (the line starting with 
⚙️
and 
gate-cli migrate --dry-run
), same as other primary skills.
逐字添加 skills/_shared/report-style.md 中的迁移引用块（以
⚙️
和
gate-cli migrate --dry-run
开头的行），与其他主要Skill保持一致。

Cross-skill routing + Safety rules

跨Skill路由 + 安全规则

Routing

路由规则

Follow skills/_shared/routing.md. Web3-specific reminders:
Follow-up intentTarget
“Is it safe / honeypot / sanctioned?”
gate-info-risk
(primary)
“Full research report / worth buying?” (no on-chain focus)
gate-info-research
(primary)
“Why pump/dump / Twitter drama only”
gate-news-intel
(primary)
遵循 skills/_shared/routing.md。Web3相关提醒：
后续意图目标Skill
“是否安全 / 蜜罐 / 被制裁？”
gate-info-risk
（首选）
“完整研究报告 / 是否值得购买？”（无链上聚焦）
gate-info-research
（首选）
“为何涨跌 / 仅推特舆情”
gate-news-intel
（首选）

Safety rules

安全规则

Follow skills/_shared/report-style.md. Web3-specific:
  1. No buy/sell recommendations; no price targets.
  2. Do not treat empty on-chain data as proof of safety — that belongs in risk skill.
  3. When web-search or UGC is used, prefix interpretive lines with media / community so they are not confused with chain state.
遵循 skills/_shared/report-style.md。Web3相关规则：
  1. 不得提供买卖建议；不得给出价格目标。
  2. 不得将空链上数据视为安全证明——此类内容属于风险Skill的范畴。
  3. 当使用网页搜索或UGC内容时，需在解释性内容前添加媒体 / 社区前缀，避免与链上状态混淆。

References

参考资料

FileLoad when...
skills/gate-info-web3/references/scenarios.mdChoosing among address / token / protocol / reserves / heatmap playbooks.
skills/gate-info-web3/references/cli-reference.mdFlag tables and verified 
platformmetrics
/ 
onchain
/ 
news
flags.
skills/gate-info-web3/references/troubleshooting.mdShortcut gaps, 
search-platforms
discovery, optional 
get-transaction
for a pasted tx hash.
skills/_shared/preflight.mdStep 0.
skills/_shared/routing.mdCross-skill matrix.
skills/_shared/report-style.mdShared report rules.
文件适用场景
skills/gate-info-web3/references/scenarios.md在地址 / 代币 / 协议 / 储备金 / 热力图剧本中进行选择时参考。
skills/gate-info-web3/references/cli-reference.md标志表格与已验证的
platformmetrics
/ 
onchain
/ 
news
标志参考。
skills/gate-info-web3/references/troubleshooting.md快捷指令缺口、
search-platforms
发现、针对粘贴交易哈希的可选
get-transaction
命令参考。
skills/_shared/preflight.md步骤0参考。
skills/_shared/routing.md跨Skill矩阵参考。
skills/_shared/report-style.md共享报告规则参考。