gate-news-communityscan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gate-news-communityscan

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.

Community Sentiment Scan Skill (X/Twitter focused). Parallel calls fetch X/Twitter discussion analysis and quantitative social sentiment; LLM aggregates into a community insights report.

Trigger Scenarios: Community opinions, Twitter/X discussions, KOL views, social sentiment, 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/

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

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

社区情绪扫描技能（重点关注X/Twitter）。通过并行调用获取X/Twitter讨论分析和量化社交情绪；LLM将数据聚合为社区洞察报告。

触发场景：社区观点、Twitter/X讨论、KOL看法、社交情绪等。

技能专属更新：本目录包含

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-news-intel

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

bash

PRIMARY_SKILL="gate-news-intel"
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-news-intel/SKILL.md
```
and its playbook contract. Carry over the minimum context:
```
symbol
```
and optional
```
time_range
```
.
```
__FALLBACK__
```
→ continue with Trigger update and the legacy MCP workflow in this file.

本旧版技能是主CLI技能

gate-news-intel

的兼容别名。

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

bash

PRIMARY_SKILL="gate-news-intel"
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

结果解读：

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

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
.

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

check

，且不设置**

GATE_SKILL_UPDATE_MODE=auto

。脚本仅对比本地与远程版本；如果

Result=update_available

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

apply

、

run

或技能执行前，询问用户是否更新。在沙箱环境（如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 1 — Check

步骤1 — 检查

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-news-communityscan/scripts/update-skill.sh" check "gate-news-communityscan"

PowerShell:

powershell

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

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

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-news-communityscan/scripts/update-skill.sh" check "gate-news-communityscan"

PowerShell：

powershell

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

结果语义：

skipped

= 无操作。

update_available

= 远程版本更新；在阻塞模式下，需获得用户同意后再执行apply。

check_failed

= 无法完成版本对比 — 根据info-news-runtime-rules.md使用当前版本继续执行；不得向用户显示技术检查失败的细节。

Agent解析（标准输出）：

GATE_SKILL_UPDATE_AGENT_ACTION=…

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

Step 2 — Confirm or Reject (blocking)

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

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-news-communityscan/scripts/update-skill.sh" apply "gate-news-communityscan"

bash

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

powershell

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

powershell

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

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.

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

apply

或

revoke-pending

。

如果返回
update_available
：

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

两步验证（严格
check
模式）：apply
/run
（未设置

GATE_SKILL_UPDATE_MODE=auto

）会失败，直到**

GATE_SKILL_CONFIRM_TOKEN

与

.gate-skill-apply-token

匹配。用户拒绝时需运行

revoke-pending

**。

bash

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

bash

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

powershell

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

powershell

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

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

GATE_SKILL_CONFIRM_TOKEN

运行

apply

**。

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

Optional —

GATE_SKILL_UPDATE_MODE=auto

可选 —

GATE_SKILL_UPDATE_MODE=auto

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.

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

check

时设置

GATE_SKILL_UPDATE_MODE=auto

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

check

中使用

auto

**模式。

Parameters

参数说明

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.

name：上方前置元数据中的
```
name
```
；必须与gate-skills上的
```
skills/<name>/
```
路径匹配。
调用方式：使用**
```
$SKILL_ROOT/scripts/update-skill.sh
```
（或
.ps1
），其中
```
$SKILL_ROOT/SKILL.md
```
是本技能的文件 — 例如
```
~/.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
```
（技能根目录）在前**，然后是**
```
name
```
；当只有一个标准化路径包含
SKILL.md
时，
```
update-skill.sh
```
/
```
update-skill.ps1
```
会自动交换参数顺序**（例如Agent传递
```
name
```
后传递路径）。
ClawHub与完整源码树：缺少
```
update-skill.ps1
```
的安装可从gate/gate-skills的
```
skills/<name>/scripts/
```
目录手动复制该文件；Agent不得自动下载。

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

check

返回退出码3**（严格模式）时，需先解决步骤2的确认问题，再执行技能。当**

check_failed

或

apply

失败**时，仍需根据运行时规则在合适情况下继续执行技能。

Known Limitations

已知限制

UGC platforms: Reddit, Discord, and Telegram depend on
```
search_ugc
```
availability. Until that API is online, label reports as X/Twitter-only.
Historical sentiment trend may degrade to a single-point snapshot depending on upstream API coverage.

UGC平台：Reddit、Discord和Telegram的支持依赖于
```
search_ugc
```
功能的可用性。在该API上线前，报告需标注为「仅X/Twitter数据」。
历史情绪趋势可能因上游API覆盖范围限制，退化为单点快照数据。

MCP Dependencies

MCP依赖

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

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

__FALLBACK__

时，本节生效。

Required MCP Servers

必需的MCP服务器

MCP Server	Status
Gate-News	✅ Required

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

MCP Tools Used

使用的MCP工具

Query Operations (Read-only)

news_feed_search_x (X/Twitter discussion — e.g., Grok-backed analysis per upstream)
news_feed_get_social_sentiment

查询操作（只读）

news_feed_search_x（X/Twitter讨论分析 — 例如基于上游Grok的分析）
news_feed_get_social_sentiment

Authentication

认证信息

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

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

Installation Check

安装检查

Required: Gate-News
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.

必需组件：Gate-News
安装方式：继续操作前，使用当前主机IDE的本地Gate MCP安装流程完成部署。
仅当当前环境中已部署必需的Gate MCP服务器时，才可继续执行。

Routing Rules

路由规则

Legacy path only — when Step 0 emitted

__ROUTE_CLI__

, routing is delegated to

gate-news-intel

User Intent	Keywords	Action
Community opinion on a coin	"what does community think about ETH"	Execute with `coin`
X/Twitter discussion	"Twitter discussion" "KOL views"	Execute (X-focused)
General social sentiment	"overall market sentiment"	Execute (no specific coin)
Reddit/Discord specific	"Reddit discussion"	Inform: X now; UGC coming
News only	"any crypto news"	Route to `gate-news-briefing`
Coin analysis	"analyze SOL"	Route to `gate-info-coinanalysis`
Why price moved	"why did BTC pump"	Route to `gate-news-eventexplain`

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

__ROUTE_CLI__

时，路由委托给

gate-news-intel

。

用户意图	关键词	操作
加密货币社区观点	"what does community think about ETH"	携带 `coin` 参数执行
X/Twitter讨论分析	"Twitter discussion" "KOL views"	执行（聚焦X平台）
通用社交情绪分析	"overall market sentiment"	执行（无特定加密货币）
特定Reddit/Discord需求	"Reddit discussion"	告知：当前仅支持X平台；UGC功能即将上线
仅新闻需求	"any crypto news"	路由至 `gate-news-briefing`
加密货币分析	"analyze SOL"	路由至 `gate-info-coinanalysis`
价格波动原因	"why did BTC pump"	路由至 `gate-news-eventexplain`

Execution Workflow

执行工作流

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

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

__FALLBACK__

时，本节生效。

Step 0: Multi-Dimension Intent Check

步骤0：多维度意图检查

Community/social sentiment → this Skill.
Coin fundamentals + technicals + macro together →
```
gate-info-research
```
(if available).

社区/社交情绪分析 → 使用本技能。
加密货币基本面+技术面+宏观分析结合 → 使用
```
gate-info-research
```
（若可用）。

Step 1: Intent Recognition & Parameter Extraction

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

```
coin
```
(optional)
```
topic
```
(optional): e.g., ETF, regulation, Layer 2
```
query
```
: constructed from coin + topic for X search; if neither, general market social scan

```
coin
```
（可选）
```
topic
```
（可选）：例如ETF、监管政策、Layer 2
```
query
```
：由coin+topic组合生成X平台搜索词；若两者均无，则进行通用市场社交扫描

Step 2: Call MCP Tools in Parallel

步骤2：并行调用MCP工具

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	`news_feed_search_x`	`query={coin or topic}`	X discussion / narratives / KOL angles	Yes
1b	`news_feed_get_social_sentiment`	`coin={coin}` if specified	Sentiment score, ratios, mention volume	Yes

步骤	MCP工具	参数	获取的数据	是否并行
1a	`news_feed_search_x`	`query={coin或topic}`	X平台讨论内容/主流叙事/KOL观点角度	是
1b	`news_feed_get_social_sentiment`	若指定则 `coin={coin}`	情绪得分、比例、提及量	是

Step 3: LLM Aggregation

步骤3：LLM聚合

Synthesize qualitative X discussion with quantitative sentiment
Dominant narratives and KOL themes
Sentiment vs price alignment or divergence

将X平台定性讨论内容与定量情绪数据进行整合
提炼主流叙事和KOL核心观点
分析情绪与价格的一致性或背离情况

Report Template

报告模板

Legacy path only — this section applies when Step 0 emitted

__FALLBACK__

markdown

undefined

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

__FALLBACK__

时，本节生效。

markdown

undefined

Community Sentiment Scan: {coin or topic}

社区情绪扫描报告：{coin或topic}

Generated: {timestamp} | Platforms: X/Twitter only Note: Reddit/Discord/Telegram not yet supported.

生成时间：{timestamp} | 数据平台：仅X/Twitter 备注：暂不支持Reddit/Discord/Telegram平台。

X/Twitter Discussion

X/Twitter讨论分析

{Summary from news_feed_search_x}

Key Narratives: ... Notable KOL Views: ...

{news_feed_search_x返回的摘要}

核心叙事：... 知名KOL观点：...

Sentiment Metrics

情绪指标

Metric	Value	Assessment
Sentiment Score	{score}	{Bullish/Bearish/Neutral}

指标	数值	评估
情绪得分	{score}	{看涨/看跌/中性}

Sentiment vs Price

情绪与价格对比

Dimension	Current
Social Sentiment	...
Price Trend (24h)	...
Alignment	{Aligned / Divergent}

维度	当前状态
社交情绪	...
24小时价格趋势	...
一致性	{一致 / 背离}

Key Takeaways

关键洞察

{2–3 insights}

Community sentiment is not a reliable price predictor. This does not constitute investment advice.

---

{2–3条核心结论}

社区情绪并非可靠的价格预测指标。本报告不构成投资建议。

---

Decision Logic

决策逻辑

Condition	Assessment
Sentiment score > 70	Strongly bullish — contrarian caution
Sentiment score < 30	Strongly bearish — possible capitulation or opportunity
Positive ratio > 80%	Strong positive consensus — watch for reversal
Discussion volume > 2x 7d average	Unusual activity — possible catalyst
KOL opinions divided	Broken consensus — uncertainty
Sentiment bullish but price falling	Divergence — sentiment may lag
Sentiment bearish but price rising	Divergence — market defying expectations

条件	评估
情绪得分>70	强烈看涨 — 需警惕逆向行情
情绪得分<30	强烈看跌 — 可能出现 capitulation（抛售潮）或投资机会
正面观点占比>80%	强烈共识看涨 — 需关注反转信号
讨论量>7日均值的2倍	异常活跃 — 可能存在催化剂事件
KOL观点分歧较大	共识破裂 — 市场不确定性高
情绪看涨但价格下跌	背离 — 情绪可能滞后于价格
情绪看跌但价格上涨	背离 — 市场走势超出预期

Error Handling

错误处理

Error Type	Handling
`news_feed_search_x` fails	Sentiment metrics only; note X discussion unavailable
`news_feed_get_social_sentiment` fails	X discussion only; skip metrics
Both Tools fail	Return error; suggest retry
No X discussions for query	Broaden query; note limited data
User asks for Reddit/Discord	State UGC not available; X-only for now

错误类型	处理方式
`news_feed_search_x` 调用失败	仅展示情绪指标；备注X平台讨论内容不可用
`news_feed_get_social_sentiment` 调用失败	仅展示X平台讨论内容；跳过情绪指标部分
两个工具均调用失败	返回错误提示；建议重试
查询无X平台讨论内容	扩大查询范围；备注数据有限
用户询问Reddit/Discord相关内容	说明UGC功能暂不可用；当前仅支持X平台

Cross-Skill Routing

跨技能路由

User Follow-up Intent	Route To
"Analyze this coin"	`gate-info-coinanalysis`
"Any news about this?"	`gate-news-briefing`
"Why is it pumping/dumping?"	`gate-news-eventexplain`
"Technical analysis?"	`gate-info-trendanalysis`
"On-chain data?"	`gate-info-tokenonchain`
"How's the overall market?"	`gate-info-marketoverview`

用户后续意图	路由至
"分析该加密货币"	`gate-info-coinanalysis`
"有相关新闻吗？"	`gate-news-briefing`
"为什么暴涨/暴跌？"	`gate-news-eventexplain`
"技术分析？"	`gate-info-trendanalysis`
"链上数据？"	`gate-info-tokenonchain`
"整体市场情况如何？"	`gate-info-marketoverview`

Safety Rules

安全规则

No fabricated opinions: Only report what data supports; do not invent KOL quotes.
Source attribution: Attribute generically to KOL/community unless public figure is clearly named in data.
Neutral presentation: Show bullish and bearish views.
Sentiment ≠ prediction: State limitations clearly.
Platform transparency: Label X/Twitter-only coverage.
Misinformation: Prefer "unverified claims circulating" over stating rumors as fact.
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-News MCP tools listed above. The LLM synthesizes from tool results. This skill does not invoke additional third-party data services.

禁止编造观点：仅报告数据支持的内容；不得虚构KOL言论。
来源归因：除非数据中明确提及公众人物，否则统一归因为KOL/社区。
中立呈现：同时展示看涨和看跌观点。
情绪≠预测：明确说明报告局限性。
平台透明度：标注数据仅来自X/Twitter平台。
虚假信息处理：对于谣言，优先使用“存在未经证实的传言”表述，而非直接陈述为事实。
年龄与资格：仅面向年满18周岁且在所在司法辖区具备完全民事行为能力的用户。
数据流说明：主机Agent处理用户提示；本技能仅调用上述列出的只读 Gate-News MCP工具。LLM基于工具返回结果进行整合。本技能不会调用额外第三方数据服务。