gate-info-tokenonchain

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gate-info-tokenonchain

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 / gate-news-specific rules (tool degradation, report standards, security, routing degradation, per-skill version checks when

scripts/

is present, and legacy wrapper 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.
Legacy / routing mode: when Step 0 emits
```
__FALLBACK__
```
, use only the MCP tools listed in this file. When Step 0 emits
```
__ROUTE_CLI__
```
, do not call those MCP tools; delegate to the mapped primary skill per Step 0.

Token On-Chain Analysis Skill (current version: no Smart Money). For token-level holder distribution, activity, and large transfers, call on-chain + basic coin info tools in parallel, then aggregate into a structured report.

Trigger Scenarios: User asks about token on-chain data, holder distribution, on-chain activity, large transfers, on-chain chip analysis, etc.

Per-skill updates: This directory includes

scripts/update-skill.sh

and may include

scripts/update-skill.ps1

. ClawHub packages uploaded to the marketplace often omit

update-skill.ps1

(upload-page restriction); GitHub / Bitbucket source trees keep both. Policy: info-news-runtime-rules.md §1. The Trigger update steps below apply in addition to gate-runtime-rules.md; when scripts are present, use this flow for version checks before execution.

Update check — user visibility: Technical failures during version check (missing script, sandbox, network, non-zero exit, no parseable

Result=

line) must not be explained to the user; continue with Execution per info-news-runtime-rules.md. Only successful

check

apply

outcomes may be summarized (including update_available
/ strict exit 3, which is still a success path that requires user confirmation before

apply

). Do not auto-download

update-skill.*

from the network. Static reference if

.ps1

is missing: canonical scripts live in gate/gate-skills under

skills/<name>/scripts/

(same

<name>

as frontmatter).

⚠️ 停止操作——在继续之前，您必须阅读并严格遵守共享的运行时规则。不要选择或调用任何工具，直到所有规则都已阅读。这些规则具有最高优先级。 → 阅读gate-runtime-rules.md → 同时阅读info-news-runtime-rules.md中针对gate-info / gate-news的特定规则（工具降级、报告标准、安全、路由降级、当存在

scripts/

时的逐Skill版本检查，以及旧版包装器路由）。

仅调用本Skill中明确列出的MCP工具。即使MCP服务器中存在未在此处记录的工具，也不得调用。
旧版/路由模式：当步骤0输出
```
__FALLBACK__
```
时，仅使用本文档中列出的MCP工具。当步骤0输出
```
__ROUTE_CLI__
```
时，请勿调用这些MCP工具；根据步骤0将任务委托给映射的主Skill。

代币链上分析Skill（当前版本：无Smart Money功能）。如需代币级别的持有者分布、活动和大额转账分析，请并行调用链上工具+基础代币信息工具，然后将结果汇总为结构化报告。

触发场景：用户询问代币链上数据、持有者分布、链上活动、大额转账、链上筹码分析等内容。

逐Skill更新：本目录包含

scripts/update-skill.sh

，可能还包含

scripts/update-skill.ps1

。上传至市场的ClawHub包通常会省略

update-skill.ps1

（上传页面限制）；GitHub / Bitbucket源码树会保留这两个文件。相关政策：info-news-runtime-rules.md §1。以下触发更新步骤是对gate-runtime-rules.md的补充；当存在脚本时，在执行前使用此流程进行版本检查。

更新检查——用户可见性：版本检查期间的技术故障（缺少脚本、沙箱问题、网络问题、非零退出码、无可解析的

Result=

行）不得向用户解释；请根据info-news-runtime-rules.md继续执行。仅可向用户总结成功的

check

apply

结果（包括**

update_available

** / 严格的退出码3，这仍属于需要用户确认后才能执行

apply

的成功路径）。请勿从网络自动下载

update-skill.*

文件。静态参考：如果缺少

.ps1

文件，标准脚本位于gate/gate-skills的

skills/<name>/scripts/

目录下（

<name>

与前置元数据中的名称一致）。

Step 0 — Wrapper routing probe

步骤0 — 包装器路由探测

This legacy skill is a compatibility alias for the primary CLI skill

gate-info-web3

Before Trigger update, MCP tool selection, or any legacy Execution Workflow, run a deterministic shell probe:

bash

PRIMARY_SKILL="gate-info-web3"
HAS_PRIMARY=0
for root in \
  "$HOME/.cursor/skills" \
  "$HOME/.codex/skills" \
  "$HOME/.openclaw/skills" \
  "$HOME/.agents/skills" \
  "$HOME/.gemini/antigravity/skills"
do
  if [ -f "$root/$PRIMARY_SKILL/SKILL.md" ]; then
    HAS_PRIMARY=1
    break
  fi
done

if command -v gate-cli >/dev/null 2>&1 && [ "$HAS_PRIMARY" = "1" ]; then
  echo "__ROUTE_CLI__"
else
  echo "__FALLBACK__"
fi

Interpretation:

```
__ROUTE_CLI__
```
→ stop here. Do not run Trigger update or the legacy MCP sections below. Follow
```
https://github.com/gate/gate-skills/blob/master/skills/gate-info-web3/SKILL.md
```
and its playbook contract. Carry over the minimum context:
```
token
```
and
```
chain
```
.
```
__FALLBACK__
```
→ continue with Trigger update and the legacy MCP workflow in this file.

此旧版Skill是主CLI Skill

gate-info-web3

的兼容别名。

在执行触发更新、选择MCP工具或任何旧版执行工作流之前，运行确定性shell探测：

bash

PRIMARY_SKILL="gate-info-web3"
HAS_PRIMARY=0
for root in \
  "$HOME/.cursor/skills" \
  "$HOME/.codex/skills" \
  "$HOME/.openclaw/skills" \
  "$HOME/.agents/skills" \
  "$HOME/.gemini/antigravity/skills"
do
  if [ -f "$root/$PRIMARY_SKILL/SKILL.md" ]; then
    HAS_PRIMARY=1
    break
  fi
done

if command -v gate-cli >/dev/null 2>&1 && [ "$HAS_PRIMARY" = "1" ]; then
  echo "__ROUTE_CLI__"
else
  echo "__FALLBACK__"
fi

Trigger update (with Execution)

解释：

Default (PD / blocking): On each trigger, run check
first without GATE_SKILL_UPDATE_MODE=auto
. The script only compares local vs remote; if

Result=update_available

, it does not overwrite files. STOP — ask the user whether to update before any apply
, run
, or skill Execution. In sandboxes (e.g. Cursor), use full / all permissions when later running apply
. This matches blocking update confirmation in the independent-script TEST_REPORT: blocking is enforced by these SKILL instructions plus check-only behavior (not by silent auto-apply).

Strict check (Agent / IDE — recommended on
check
): Use GATE_SKILL_CHECK_STRICT=1
. When

Result=update_available

, check
exits 3 and prints GATE_SKILL_CHECK_EXIT=3
— it stops only that shell step. Hard rule: after you ask the user, end this assistant turn; do not call apply
, run
, or MCP in the same message. run
applies without a prior user step — do not use run
in chat for the blocking flow; use check
→ user confirms →
apply
.

```
__ROUTE_CLI__
```
→ 在此处停止。不要运行触发更新或以下的旧版MCP部分。遵循
```
https://github.com/gate/gate-skills/blob/master/skills/gate-info-web3/SKILL.md
```
及其手册约定。仅传递必要上下文：
```
token
```
和
```
chain
```
。
```
__FALLBACK__
```
→ 继续执行触发更新以及本文档中的旧版MCP工作流。

Step 1 — Check

触发更新（含执行）

Install root:

check

apply

read $DEST/SKILL.md
. Typical $SKILL_ROOT
: $HOME/.cursor/skills/<name>/
, $HOME/.codex/skills/<name>/
, $HOME/.openclaw/skills/<name>/
, $HOME/.agents/skills/<name>/
, $HOME/.gemini/antigravity/skills/<name>/
. Single-arg: the script resolves DEST
in that order when SKILL.md
exists; otherwise DEST
is

scripts/../

. Workspace-only trees need two-arg check
/ apply
with explicit DEST
.

Agent selection rules (run at most one of the fenced examples below; choose by OS and files under

$SKILL_ROOT/scripts/

macOS / Linux / WSL / Git Bash: If
```
update-skill.sh
```
exists → use only the Bash example.
Windows (native PowerShell): If
```
update-skill.ps1
```
exists → use only the PowerShell example.
Windows without
.ps1
(typical ClawHub install): If only
```
update-skill.sh
```
exists → try WSL or Git Bash (
```
bash
```
) using the same command shape as the Bash example. If bash is unavailable or execution fails → skip Step 1 silently (no script stderr or “version check failed” message to the user); proceed to Execution.
Neither script exists: Skip Step 1 silently; proceed to Execution. Do not invent
```
GATE_SKILL_CONFIRM_TOKEN
```
or run
```
apply
```
/
```
revoke-pending
```
.

Bash (blocking — no auto; example Cursor):

bash

GATE_SKILL_CHECK_STRICT=1 bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" check "gate-info-tokenonchain"

PowerShell:

powershell

$env:GATE_SKILL_CHECK_STRICT = '1'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" check "gate-info-tokenonchain"

Result semantics:

skipped

= no action.

update_available

= remote newer; with blocking flow, do not apply until the user agrees.

check_failed

= could not compare — proceed with current version per info-news-runtime-rules.md; do not surface technical check failure details to the user.

Agent parse (stdout):

GATE_SKILL_UPDATE_AGENT_ACTION=…

. BLOCK_UNTIL_USER_CONFIRMS_UPDATE
→ Step 2 before Execution. CONTINUE_SKILL_EXECUTION
→ no block from the check script.

默认（产品开发/阻塞模式）：每次触发时，先运行**

check

，且不设置**

GATE_SKILL_UPDATE_MODE=auto

。脚本仅比较本地版本与远程版本；如果返回

Result=update_available

，则不会覆盖文件。停止操作——在执行任何**

apply

、

run

或Skill执行之前，询问用户是否要更新。在沙箱环境（如Cursor）中，后续运行

apply

时需使用完全/所有权限**。这与独立脚本TEST_REPORT中的阻塞更新确认一致：阻塞由这些SKILL指令加上仅检查行为强制执行（而非静默自动应用）。

严格检查（Agent/IDE——推荐在
check
时使用）：设置**

GATE_SKILL_CHECK_STRICT=1

。当返回
Result=update_available
时，

check

会以退出码3终止，并打印

GATE_SKILL_CHECK_EXIT=3

——仅终止该shell步骤。硬性规则：询问用户后，结束本次助手对话轮次；请勿在同一条消息中调用

apply

、

run

或MCP工具。

run

会在无用户前置步骤的情况下应用更新——在阻塞流程的聊天场景中请勿使用

run

；请使用

check

→ 用户确认 →

apply

**的流程。

Step 2 — Confirm or Reject (blocking)

步骤1 — 检查

Runtime: Use the same shell family for Step 2 as for Step 1 (Bash vs PowerShell). If Step 1 was skipped, do not run

apply

revoke-pending

If
update_available
:

STOP — do NOT proceed to Execution yet.
Inform the user (e.g. newer version available; summarize if helpful).
Wait for the user’s reply — blocking step.
Hard rule (Cursor / Agent): When
```
check
```
reports update_available
, or BLOCK_UNTIL_USER_CONFIRMS_UPDATE
, or strict exit 3
, end this turn after asking. Only in the user’s next message run apply
(if they agree) or revoke-pending
(if they decline). Do not chain apply
in the same turn as check
for this flow.
- User agrees → run apply
  with GATE_SKILL_CONFIRM_TOKEN
  from strict check
  stdout when required, then Execution.
- User declines → revoke-pending
  , then Execution on the current install.

Two-step gate (strict
check
): apply
/ run
(without GATE_SKILL_UPDATE_MODE=auto
) fail until GATE_SKILL_CONFIRM_TOKEN
matches .gate-skill-apply-token
. User decline → revoke-pending
.

bash

GATE_SKILL_CONFIRM_TOKEN="<paste from check stdout>" bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" apply "gate-info-tokenonchain"

bash

bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" revoke-pending "gate-info-tokenonchain"

powershell

$env:GATE_SKILL_CONFIRM_TOKEN = '<paste from check stdout>'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" apply "gate-info-tokenonchain"

powershell

powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" revoke-pending "gate-info-tokenonchain"

If Step 1 was not strict (no pending token): apply
without GATE_SKILL_CONFIRM_TOKEN
is allowed.

If
skipped
or
check_failed
: no update step; proceed to Execution.

安装根目录：

check

apply

会读取**

$DEST/SKILL.md

。典型的

$SKILL_ROOT

包括：

$HOME/.cursor/skills/<name>/

、

$HOME/.codex/skills/<name>/

、

$HOME/.openclaw/skills/<name>/

、

$HOME/.agents/skills/<name>/

、

$HOME/.gemini/antigravity/skills/<name>/

。单参数模式：当

SKILL.md

存在时，脚本会按上述顺序解析

DEST

；否则

DEST

为
scripts/../
。仅工作区的目录树需要使用双参数的

check

** / apply
，并指定明确的**

DEST

**。

Agent选择规则（最多运行以下 fenced 示例中的一个；根据操作系统和

$SKILL_ROOT/scripts/

下的文件选择）：

macOS / Linux / WSL / Git Bash：如果存在
```
update-skill.sh
```
→ 仅使用Bash示例。
Windows（原生PowerShell）：如果存在
```
update-skill.ps1
```
→ 仅使用PowerShell示例。
Windows无
.ps1
文件（典型ClawHub安装）：如果仅存在
```
update-skill.sh
```
→ 尝试使用WSL或Git Bash（
```
bash
```
）执行，命令格式与Bash示例相同。如果bash不可用或执行失败 → 静默跳过步骤1（不向用户显示脚本错误信息或“版本检查失败”提示）；继续执行后续流程。
两种脚本都不存在：静默跳过步骤1；继续执行后续流程。请勿自行生成
```
GATE_SKILL_CONFIRM_TOKEN
```
或运行
```
apply
```
/
```
revoke-pending
```
。

Bash（阻塞模式——无自动更新；Cursor示例）：

bash

GATE_SKILL_CHECK_STRICT=1 bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" check "gate-info-tokenonchain"

PowerShell：

powershell

$env:GATE_SKILL_CHECK_STRICT = '1'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" check "gate-info-tokenonchain"

结果语义：

skipped

= 无操作。

update_available

= 远程版本更新；在阻塞模式下，需等待用户同意后再应用更新。

check_failed

= 无法完成版本比较——根据info-news-runtime-rules.md使用当前版本继续执行；请勿向用户透露技术检查失败的细节。

Agent解析（标准输出）：

GATE_SKILL_UPDATE_AGENT_ACTION=…

。BLOCK_UNTIL_USER_CONFIRMS_UPDATE
→ 执行前先完成步骤2。CONTINUE_SKILL_EXECUTION
→ 检查脚本无阻塞，可继续执行Skill。

Optional —

GATE_SKILL_UPDATE_MODE=auto

步骤2 — 确认或拒绝（阻塞模式）

For CI / unattended automation only: setting GATE_SKILL_UPDATE_MODE=auto
on check
makes the script apply immediately when the remote is newer — no user confirmation and incompatible with blocking update confirmation tests. Do not use auto
on check
when reproducing the blocking PD flow.

运行时：步骤2使用与步骤1相同的shell类型（Bash或PowerShell）。如果步骤1被跳过，请勿运行

apply

或

revoke-pending

。

如果返回
update_available
：

停止操作——暂不执行后续流程。
告知用户（例如：检测到更新版本；如有帮助可简要说明更新内容）。
等待用户回复——阻塞步骤。
硬性规则（Cursor/Agent）：当
```
check
```
返回**
```
update_available
```
、
```
BLOCK_UNTIL_USER_CONFIRMS_UPDATE
```
或严格的
```
exit 3
```
时，询问用户后结束本次对话轮次**。仅在用户的下一条消息中运行**
```
apply
```
（如果用户同意）或
```
revoke-pending
```
（如果用户拒绝）。在阻塞流程中，请勿在同一次对话中将
```
apply
```
与
```
check
```
**链式执行。
- 用户同意 → 运行**
```
apply
```
  ，必要时使用严格
  check
  标准输出中的
```
GATE_SKILL_CONFIRM_TOKEN
```
  **，然后执行后续流程。
- 用户拒绝 → 运行**
```
revoke-pending
```
  **，然后使用当前安装版本执行后续流程。

两步验证（严格
check
）：在**

GATE_SKILL_CONFIRM_TOKEN

与

.gate-skill-apply-token

匹配之前，

apply

** / run
（未设置**

GATE_SKILL_UPDATE_MODE=auto

）会执行失败。用户拒绝时 → 运行

revoke-pending

**。

bash

GATE_SKILL_CONFIRM_TOKEN="<粘贴check标准输出中的内容>" bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" apply "gate-info-tokenonchain"

bash

bash "$HOME/.cursor/skills/gate-info-tokenonchain/scripts/update-skill.sh" revoke-pending "gate-info-tokenonchain"

powershell

$env:GATE_SKILL_CONFIRM_TOKEN = '<粘贴check标准输出中的内容>'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" apply "gate-info-tokenonchain"

powershell

powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-tokenonchain\scripts\update-skill.ps1" revoke-pending "gate-info-tokenonchain"

如果步骤1未使用严格模式（无待处理令牌）：允许不携带**

GATE_SKILL_CONFIRM_TOKEN

运行

apply

**。

如果返回
skipped
或
check_failed
：无需执行更新步骤；继续执行后续流程。

Parameters

可选——

GATE_SKILL_UPDATE_MODE=auto

name: Frontmatter
```
name
```
above; must match
```
skills/<name>/
```
on gate-skills.
Invoke: Use $SKILL_ROOT/scripts/update-skill.sh
(or
```
.ps1
```
) where $SKILL_ROOT/SKILL.md
is this skill — e.g. ~/.cursor/skills/<name>
, ~/.codex/skills/<name>
, ~/.openclaw/skills/<name>
, ~/.agents/skills/<name>
, ~/.gemini/antigravity/skills/<name>
; do not treat ~/.cursor
(or any host root without skills/<name>/SKILL.md
) as the install. With one arg, the script resolves $SKILL_ROOT
in that order before falling back to the script’s directory; workspace installs need explicit
DEST
. Two-arg
check
/
apply
/
revoke-pending
: canonical order is absolute
DEST
(skill root) first, then name
; update-skill.sh
/
update-skill.ps1
auto-swap when only one normalized path contains
```
SKILL.md
```
(e.g. agent passes
```
name
```
then path).
ClawHub vs full tree: Installs without
```
update-skill.ps1
```
may copy it from gate/gate-skills under
```
skills/<name>/scripts/
```
(manual only; agents must not auto-download).

Do not dump raw script logs into the user-facing reply except when debugging. On check
exit 3 (strict), do not run Execution until Step 2 is resolved. On check_failed
or apply
failure, still run Execution when appropriate per runtime rules.

仅适用于CI/无人值守自动化：在**

check

时设置

GATE_SKILL_UPDATE_MODE=auto

，当远程版本更新时，脚本会立即应用更新**——无需用户确认，且与阻塞更新确认测试不兼容。在复现阻塞产品开发流程时，请勿在**

check

时使用

auto

**模式。

Known Limitations

参数

Smart Money:
```
info_onchain_get_smart_money
```
and
```
scope=smart_money
```
for
```
info_onchain_get_token_onchain
```
are not available in this version. Inform users and use holders / activity / transfers only.
Entity profiling:
```
info_onchain_get_entity_profile
```
— whale entity profiling not supported until tool is available.
On-chain data coverage depends on upstream chain support (e.g., BlockInfo).

name：前置元数据中的
```
name
```
；必须与gate-skills上的
```
skills/<name>/
```
路径匹配。
调用方式：使用**
```
$SKILL_ROOT/scripts/update-skill.sh
```
（或
.ps1
），其中
```
$SKILL_ROOT/SKILL.md
```
为本Skill的文档——例如
```
~/.cursor/skills/<name>
```
、
```
~/.codex/skills/<name>
```
、
```
~/.openclaw/skills/<name>
```
、
```
~/.agents/skills/<name>
```
、
```
~/.gemini/antigravity/skills/<name>
```
；请勿将
```
~/.cursor
```
（或任何不包含
```
skills/<name>/SKILL.md
```
的宿主根目录）视为安装目录。单参数模式下，脚本会按上述顺序解析
```
$SKILL_ROOT
```
，若未找到则回退到脚本所在目录；工作区安装需要使用双参数的
check
/
apply
/
revoke-pending
，并指定明确的
```
DEST
```
。双参数
check
/
apply
/
revoke-pending
：标准顺序为绝对路径
```
DEST
```
（Skill根目录）在前**，然后是**
```
name
```
；当只有一个标准化路径包含
SKILL.md
时，
```
update-skill.sh
```
/
```
update-skill.ps1
```
会自动交换参数顺序**（例如Agent传递
```
name
```
然后是路径）。
ClawHub vs 完整目录树：无
```
update-skill.ps1
```
的安装可从gate/gate-skills的
```
skills/<name>/scripts/
```
目录手动复制该文件（仅手动操作；Agent不得自动下载）。

请勿将原始脚本日志直接输出到用户可见的回复中，调试场景除外。当**

check

返回退出码3**（严格模式）时，在步骤2完成前请勿执行后续流程。当**

check_failed

或

apply

失败**时，仍需根据运行时规则在适当情况下执行后续流程。

MCP Dependencies

已知限制

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

Smart Money：当前版本不支持
```
info_onchain_get_smart_money
```
以及
```
info_onchain_get_token_onchain
```
的
```
scope=smart_money
```
参数。请告知用户，仅使用持有者/活动/转账相关功能。
实体画像：
```
info_onchain_get_entity_profile
```
——巨鲸实体画像功能需等待工具上线后支持。
链上数据覆盖范围取决于上游链的支持情况（如BlockInfo）。

Required MCP Servers

MCP依赖

MCP Server	Status
Gate-Info	✅ Required

仅适用于旧版路径——当步骤0输出

__FALLBACK__

时，本节内容生效。

MCP Tools Used

必需的MCP服务器

Query Operations (Read-only)

info_onchain_get_token_onchain
info_coin_get_coin_info

MCP服务器	状态
Gate-Info	✅ 必需

Authentication

使用的MCP工具

API Key Required: No
Credentials Source: None; this skill uses read-only Gate Info / Gate News MCP access only.

查询操作（只读）

info_onchain_get_token_onchain
info_coin_get_coin_info

Installation Check

认证

Required: Gate-Info
Install: Use the local Gate MCP installation flow for the current host IDE before continuing.
Continue only after the required Gate MCP server is available in the current environment.

是否需要API密钥：否
凭证来源：无；本Skill仅使用只读的Gate Info / Gate News MCP访问权限。

Routing Rules

安装检查

Legacy path only — when Step 0 emitted

__ROUTE_CLI__

, routing is delegated to

gate-info-web3

User Intent	Keywords	Action
Token holder distribution	"ETH holders" "BTC holding distribution" "top holders"	Execute with `scope=holders`
On-chain activity	"on-chain activity" "active addresses" "transaction count"	Execute with `scope=activity`
Large transfers	"large transfers" "whale movements" "unusual transfers"	Execute with `scope=transfers`
Full on-chain overview	"on-chain analysis for SOL" "ETH on-chain data"	Execute with `holders,activity,transfers`
Smart Money (not yet supported)	"smart money buying"	Inform user; run available scopes only
Specific address query	"track this address 0x..."	Route to `gate-info-addresstracker`
Coin fundamentals	"analyze SOL"	Route to `gate-info-coinanalysis`
Whale entity tracking	"what is Jump Trading doing"	Route to `gate-info-whaletracker` if available, else inform

必需组件：Gate-Info
安装：在继续之前，使用当前宿主IDE的本地Gate MCP安装流程完成安装。
仅当当前环境中已安装必需的Gate MCP服务器时，才可继续执行。

Execution Workflow

路由规则

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

仅适用于旧版路径——当步骤0输出

__ROUTE_CLI__

时，路由由

gate-info-web3

负责。

用户意图	关键词	操作
代币持有者分布	"ETH持有者" "BTC持仓分布" "顶级持有者"	使用 `scope=holders` 执行
链上活动	"链上活动" "活跃地址" "交易数量"	使用 `scope=activity` 执行
大额转账	"大额转账" "巨鲸动向" "异常转账"	使用 `scope=transfers` 执行
完整链上概览	"SOL链上分析" "ETH链上数据"	使用 `holders,activity,transfers` 执行
Smart Money（暂不支持）	"smart money买入"	告知用户；仅运行可用范围的分析
特定地址查询	"追踪此地址0x..."	路由至 `gate-info-addresstracker`
代币基本面	"分析SOL"	路由至 `gate-info-coinanalysis`
巨鲸实体追踪	"Jump Trading在做什么"	若 `gate-info-whaletracker` 可用则路由至该Skill，否则告知用户

Step 0: Multi-Dimension Intent Check

执行工作流

Token-level on-chain → this Skill.
Specific address (not token) →
```
gate-info-addresstracker
```
.
Fundamentals + technicals + news together →
```
gate-info-research
```
(if available).

仅适用于旧版路径——当步骤0输出

__FALLBACK__

时，本节内容生效。

Step 1: Intent Recognition & Parameter Extraction

步骤0：多维度意图检查

```
symbol
```
(required): Token ticker (e.g., BTC, ETH, SOL)
```
chain
```
(optional): e.g., eth, sol, bsc

scope

: one or more of

holders

activity

transfers

(

smart_money

— not available)

```
time_range
```
(optional): default 24h for transfers/activity

代币级链上分析 → 使用本Skill。
特定地址（非代币） → 使用
```
gate-info-addresstracker
```
。
基本面+技术面+新闻综合分析 → 使用
```
gate-info-research
```
（若可用）。

Step 2: Call MCP Tools in Parallel

步骤1：意图识别与参数提取

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	`info_onchain_get_token_onchain`	`symbol, chain, scope, time_range`	Holder / activity / transfer data per scope	Yes
1b	`info_coin_get_coin_info`	`query={symbol}, scope="basic"`	Basic coin context	Yes

```
symbol
```
（必填）：代币代码（如BTC、ETH、SOL）
```
chain
```
（可选）：如eth、sol、bsc
```
scope
```
：
```
holders
```
、
```
activity
```
、
```
transfers
```
中的一个或多个（
```
smart_money
```
——暂不可用）
```
time_range
```
（可选）：转账/活动默认时间范围为24小时

Step 3: LLM Aggregation

步骤2：并行调用MCP工具

Contextualize on-chain data with coin info
Identify patterns and anomalies
Avoid speculative price predictions

步骤	MCP工具	参数	获取的数据	是否并行
1a	`info_onchain_get_token_onchain`	`symbol, chain, scope, time_range`	对应范围的持有者/活动/转账数据	是
1b	`info_coin_get_coin_info`	`query={symbol}, scope="basic"`	基础代币上下文信息	是

Report Template

步骤3：LLM聚合

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

markdown

undefined

将链上数据与代币信息进行关联分析
识别模式与异常
避免投机性价格预测

{symbol} On-Chain Analysis

报告模板

Generated: {timestamp} | Chain: {chain or "All supported chains"} Note: Smart Money analysis not yet available in this version.

仅适用于旧版路径——当步骤0输出

__FALLBACK__

时，本节内容生效。

markdown

undefined

Token Overview

{symbol}链上分析

Metric	Value
Token	{symbol} ({name})
Market Cap	${market_cap}
Circulating Supply	{circulating_supply}

生成时间：{timestamp} | 链：{chain或"所有支持的链"} 注意：当前版本暂不支持Smart Money分析。

Holder Distribution (if scope includes holders)

代币概述

{Tables + LLM concentration assessment}

指标	数值
代币	{symbol} ({name})
市值	${market_cap}
流通供应量	{circulating_supply}

On-Chain Activity (if scope includes activity)

持有者分布（若范围包含holders）

{Metrics + LLM trend assessment}

{表格 + LLM集中度评估}

Large Transfers (if scope includes transfers)

链上活动（若范围包含activity）

{Table + LLM flow assessment}

{指标 + LLM趋势评估}

On-Chain Health Score

大额转账（若范围包含transfers）

{Dimensions scored /10 + overall}

{表格 + LLM资金流向评估}

Key Insights

链上健康评分

{2–3 data-driven bullets}

On-chain data does not predict future prices. This does not constitute investment advice.

---

{各维度评分/10 + 总分}

Decision Logic

关键洞察

Condition	Assessment
Top 10 holder concentration > 70%	High concentration risk
Top 10 holder concentration < 30%	Well-distributed holder base
Active addresses declining > 20% WoW	Declining network activity
Active addresses growing > 30% WoW	Strong activity growth
Large transfers to exchange addresses	Potential sell pressure
Large transfers from exchange addresses	Potential accumulation
User asks about Smart Money	State not available; offer holders/activity/transfers

{2–3条基于数据的要点}

链上数据不代表未来价格走势。本报告不构成投资建议。

---

Error Handling

决策逻辑

Error Type	Handling
Token not found on-chain	Check via `info_coin_get_coin_info` ; suggest symbol/chain
`info_onchain_get_token_onchain` fails	Show coin info only; note on-chain unavailable
`info_coin_get_coin_info` fails	Show on-chain data without market context
Scope returns empty	Skip section; note no data for scope
Chain not supported	List supported chains; ask user
Both Tools fail	Return error; suggest retry later
User requests `smart_money`	Inform not available; offer other scopes

条件	评估
前10大持有者集中度>70%	集中度风险高
前10大持有者集中度<30%	持有者基础分布良好
活跃地址数量周环比下降>20%	网络活跃度下降
活跃地址数量周环比增长>30%	活跃度增长强劲
大额转账至交易所地址	潜在抛售压力
大额转账从交易所地址转出	潜在积累信号
用户询问Smart Money	说明暂不可用；提供持有者/活动/转账分析选项

Cross-Skill Routing

错误处理

User Follow-up Intent	Route To
"Analyze this coin"	`gate-info-coinanalysis`
"Track this address"	`gate-info-addresstracker`
"Is this token safe?"	`gate-info-riskcheck`
"Technical analysis?"	`gate-info-trendanalysis`
"Any news?"	`gate-news-briefing`
"What does the community think?"	`gate-news-communityscan`
"DeFi data for this?"	`gate-info-defianalysis`

错误类型	处理方式
链上未找到代币	通过 `info_coin_get_coin_info` 检查；建议用户确认代币代码/链
`info_onchain_get_token_onchain` 调用失败	仅展示代币信息；说明链上数据不可用
`info_coin_get_coin_info` 调用失败	展示链上数据，但不包含市场上下文信息
对应范围返回空数据	跳过该部分；说明该范围无可用数据
链不被支持	列出支持的链；询问用户
两个工具均调用失败	返回错误信息；建议稍后重试
用户请求 `smart_money`	说明暂不可用；提供其他范围的分析选项

Safety Rules

跨Skill路由

No fabricated on-chain data: Only report MCP-returned data.
Address privacy: Shorten addresses (e.g.,
```
0x1234...abcd
```
); do not doxx.
No trading signals: Informational only; not buy/sell advice.
Exchange labels: Best-effort; may be mislabeled.
Data lag: Note indexing delays where relevant.
Smart Money: Clearly state unavailability rather than approximating.
Age & eligibility: Intended for users aged 18 or above with full civil capacity in their jurisdiction.
Data flow: The host agent processes user prompts; this skill directs read-only Gate-Info MCP tools listed above. The LLM summarizes tool output. This skill does not invoke additional third-party data services.

用户后续意图	路由至
"分析这个代币"	`gate-info-coinanalysis`
"追踪这个地址"	`gate-info-addresstracker`
"这个代币安全吗？"	`gate-info-riskcheck`
"技术分析？"	`gate-info-trendanalysis`
"有相关新闻吗？"	`gate-news-briefing`
"社区看法如何？"	`gate-news-communityscan`
"这个代币的DeFi数据？"	`gate-info-defianalysis`

—

安全规则

—

不得伪造链上数据：仅报告MCP返回的数据。
地址隐私保护：缩短地址（如
```
0x1234...abcd
```
）；不得泄露完整地址。
不得提供交易信号：仅提供信息；不构成买卖建议。
交易所标签：尽最大努力标注；可能存在误标情况。
数据延迟：相关情况下需说明索引延迟。
Smart Money：明确说明暂不可用，不得近似替代。
年龄与资格：仅面向18周岁及以上且在所在司法辖区具备完全民事行为能力的用户。
数据流：宿主Agent处理用户提示；本Skill仅调用上述列出的只读 Gate-Info MCP工具。LLM负责汇总工具输出。本Skill不会调用额外的第三方数据服务。

gate-info-tokenonchain

Original

Translation

gate-info-tokenonchain

gate-info-tokenonchain

General Rules

通用规则

Step 0 — Wrapper routing probe

步骤0 — 包装器路由探测

Trigger update (with Execution)

解释：

Step 1 — Check

触发更新（含执行）

Step 2 — Confirm or Reject (blocking)

步骤1 — 检查

Optional — GATE_SKILL_UPDATE_MODE=auto

步骤2 — 确认或拒绝（阻塞模式）

Parameters

可选——GATE_SKILL_UPDATE_MODE=auto

Known Limitations

参数

MCP Dependencies

已知限制

Required MCP Servers

MCP依赖

MCP Tools Used

必需的MCP服务器

Authentication

使用的MCP工具

Installation Check

认证

Routing Rules

安装检查

Execution Workflow

路由规则

Step 0: Multi-Dimension Intent Check

执行工作流

Step 1: Intent Recognition & Parameter Extraction

步骤0：多维度意图检查

Step 2: Call MCP Tools in Parallel

步骤1：意图识别与参数提取

Step 3: LLM Aggregation

步骤2：并行调用MCP工具

Report Template

步骤3：LLM聚合

{symbol} On-Chain Analysis

报告模板

Token Overview

{symbol}链上分析

Holder Distribution (if scope includes holders)

代币概述

On-Chain Activity (if scope includes activity)

持有者分布（若范围包含holders）

Large Transfers (if scope includes transfers)

链上活动（若范围包含activity）

On-Chain Health Score

大额转账（若范围包含transfers）

Key Insights

链上健康评分

Decision Logic

关键洞察

Error Handling

决策逻辑

Cross-Skill Routing

错误处理

Safety Rules

跨Skill路由

安全规则

Optional —
`GATE_SKILL_UPDATE_MODE=auto`

可选——
`GATE_SKILL_UPDATE_MODE=auto`