gate-news-intel

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gate-news-intel

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.

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与剧本约定

Primary boundary: news, events, announcements, and social/UGC intelligence. Optional info
calls appear only in playbooks that explicitly add market or coin background (
```
intel_plus_market
```
,
```
market_wide_intel
```
).
Legacy commands MUST exist under gate-cli v0.5.2
. When
```
shortcuts_enabled
```
(
```
>= 0.7.6
```
), prefer playbook
```
shortcut
```
/
```
info_shortcut
```
blocks; fall back to legacy
```
commands
```
on failure or older CLI. When preflight
```
route
```
is
```
CLI
```
, do not use Gate MCP from this skill.
Always pass --format json
on data-collection commands.
Separate fact from opinion: label facts (dated events, official announcements, news wires) vs community / UGC / X / social (always cite source type: UGC, X, Reddit, YouTube, sentiment index).
Synthesis order (PRD 5.6.7):
- “Why did it drop / crash?” → causal event chain first (Section 2), then optionally market/coin background (Section 4).
- “How does the community see ...?” → Section 3 (community / UGC / X / sentiment) before broad market overview (Section 4).
Final user-facing reports may use the user’s locale; this
```
SKILL.md
```
stays English for discovery (repository
```
CLAUDE.md
```
rule 1).

核心边界：新闻、事件、公告及社交/UGC情报。仅在明确添加市场或币种背景的剧本（
```
intel_plus_market
```
、
```
market_wide_intel
```
）中，才可选调用
```
info
```
工具。
旧版命令必须兼容 gate-cli v0.5.2
。当
```
shortcuts_enabled
```
（版本
```
>= 0.7.6
```
）时，优先使用剧本的
```
shortcut
```
/
```
info_shortcut
```
模块；若失败或使用旧版CLI，则回退到旧版
```
commands
```
。当预检查
```
route
```
为
```
CLI
```
时，请勿从此Skill调用Gate MCP。
数据收集命令必须始终传递 --format json
参数。
区分事实与观点：标注事实（带日期的事件、官方公告、新闻专线内容）与社区/UGC/X/社交内容（必须注明来源类型：UGC、X、Reddit、YouTube、情绪指数）。
合成顺序（PRD 5.6.7）：
- “为何下跌/暴跌？” → 先呈现因果事件链（第2节），再可选添加市场/币种背景（第4节）。
- “社区如何看待……？” → 先呈现第3节（社区/UGC/X/情绪），再呈现广泛市场概况（第4节）。
最终面向用户的报告可使用用户所在地区的语言；本
```
SKILL.md
```
保持英文以便于检索（仓库
```
CLAUDE.md
```
规则1）。

Step 0 — Preflight

步骤0 — 预检查

Follow skills/_shared/preflight.md verbatim:

Run

gate-cli preflight --format json

; parse

.route

.status

.user_message

Branch:
```
CLI
```
→ continue;
```
MCP_FALLBACK
```
→ emit
```
__FALLBACK__
```
and halt (legacy MCP fallback is outside this repo’s primary skills);
```
BLOCK
```
→ echo
```
user_message
```
and halt.
When
```
status == "ready_with_migration_warning"
```
, remember it — Step 3 appends one migrate hint at the end of the report.
Step 0.5 — Version gate: From
```
PREFLIGHT_JSON.cli_version
```
, set
```
shortcuts_enabled
```
per skills/_shared/cli-version-routing.md. Store
```
cli_version
```
for Step 1 (
```
market_move_explain
```
needs
```
>= 0.7.2
```
for
```
explain-market-move
```
).

Do NOT run

news

info

data collection until

route == "CLI"

严格遵循 skills/_shared/preflight.md：

运行

gate-cli preflight --format json

；解析

.route

、

.status

、

.user_message

字段。

分支处理：
```
CLI
```
→ 继续；
```
MCP_FALLBACK
```
→ 输出
```
__FALLBACK__
```
并终止（旧版MCP fallback不在本仓库核心Skill范围内）；
```
BLOCK
```
→ 回显
```
user_message
```
并终止。
若
```
status == "ready_with_migration_warning"
```
，需记录该状态 — 步骤3将在报告末尾添加一条迁移提示。
步骤0.5 — 版本校验：根据
```
PREFLIGHT_JSON.cli_version
```
，参考skills/_shared/cli-version-routing.md设置
```
shortcuts_enabled
```
。保存
```
cli_version
```
供步骤1使用（
```
market_move_explain
```
需要版本
```
>= 0.7.2
```
以支持
```
explain-market-move
```
）。

在

route == "CLI"

之前，请勿运行

news

info

数据收集命令。

Step 1 — Intent routing

步骤1 — 意图路由

Map the user query to exactly one playbook id from playbooks/gate-news-intel.yaml.

Playbook id	When to pick	Required slots
`news_brief`	Headlines / “what happened recently” with a named asset	`symbol`
`event_explain`	Pure event timeline / detail lookup without price-move attribution	`symbol`
`market_move_explain`	“Why did X move / crash / pump / dump”, price-move attribution, market move reason	`symbol` , `query`
`exchange_listings`	Listings, delistings, maintenance, announcements	—
`community_intel`	“Community take”, Reddit, YouTube, X, social / sentiment (social-first)	`symbol`
`intel_plus_market`	User wants news + market or coin background	`symbol`
`market_wide_intel`	Broad “what is happening in crypto” without a ticker	—

将用户查询映射到playbooks/gate-news-intel.yaml中唯一的剧本ID。

剧本ID	适用场景	必填参数
`news_brief`	头条新闻 / “近期发生了什么”（指定资产）	`symbol`
`event_explain`	纯事件时间线/详情查询（无价格波动归因需求）	`symbol`
`market_move_explain`	“为何X价格波动/暴跌/暴涨”、价格波动归因、市场波动原因	`symbol` , `query`
`exchange_listings`	上线、下线、维护、公告类查询	—
`community_intel`	“社区观点”、Reddit、YouTube、X、社交/情绪分析（优先社交内容）	`symbol`
`intel_plus_market`	用户需要新闻 + 市场或币种背景	`symbol`
`market_wide_intel`	宽泛的“加密市场现状”查询（无交易对）	—

Version-dependent routing

版本相关路由规则

market_move_explain

requires

gate-cli

v0.7.2+ (the earliest version that ships

explain-market-move

). The playbook's

cli_baseline

field documents this. All other playbooks remain compatible with v0.5.2.

If routed to
market_move_explain
but
cli_version
< 0.7.2: fall back to

event_explain

and include this notice in the report footer:

explain-market-move requires gate-cli v0.7.2+. Falling back to event_explain with manual news/event stitching. Upgrade gate-cli for server-side Tavily-powered attribution with AI summary.

market_move_explain

需要

gate-cli

v0.7.2+（最早支持

explain-market-move

的版本）。剧本的

cli_baseline

字段记录了此要求。其他所有剧本均兼容v0.5.2版本。

若路由到
market_move_explain
但
cli_version
< 0.7.2：回退到

event_explain

，并在报告页脚添加以下提示：

explain-market-move需要gate-cli v0.7.2+。将回退到event_explain并手动拼接新闻/事件内容。升级gate-cli可获取由Tavily驱动的服务器端归因及AI摘要功能。

Slot extraction

参数提取

```
symbol
```
: ticker (
```
BTC
```
,
```
ETH
```
, ...). Ask if missing when the playbook requires it.
```
query
```
: user's original natural-language question, e.g. "Why did BTC surge?". Required for
```
market_move_explain
```
; extracted verbatim from the user's input.

time_range

: default

24h

7d

30d

for legacy leaves; news shortcuts (

+brief

+event-explain

+community-scan

) accept only

1h

24h

7d

— clamp against playbook shortcut

arg_enums

before calling (see

_shared/cli-version-routing.md

market_move_explain

30m

1h

2h

4h

24h

(default

2h

```
event_id
```
: only when the user references a concrete event for
```
get-event-detail
```
.
```
topic_query
```
: for
```
market_wide_intel
```
web search.

```
symbol
```
：交易对代码（
```
BTC
```
、
```
ETH
```
等）。若剧本要求该参数但缺失，需向用户询问。
```
query
```
：用户原始自然语言问题，例如“Why did BTC surge?”。
```
market_move_explain
```
必填；直接从用户输入中提取原文。
```
time_range
```
：旧版默认值为
```
24h
```
/
```
7d
```
/
```
30d
```
；新闻快捷指令（
```
+brief
```
、
```
+event-explain
```
、
```
+community-scan
```
）仅接受
```
1h
```
/
```
24h
```
/
```
7d
```
— 调用前需根据剧本快捷指令的
```
arg_enums
```
进行限制（参考
```
_shared/cli-version-routing.md
```
）。
```
market_move_explain
```
：
```
30m
```
/
```
1h
```
/
```
2h
```
/
```
4h
```
/
```
24h
```
（默认
```
2h
```
）。
```
event_id
```
：仅当用户引用具体事件并需要
```
get-event-detail
```
时使用。
```
topic_query
```
：用于
```
market_wide_intel
```
的网页搜索。

Coin fallback rules (market_move_explain)

币种回退规则（market_move_explain）

When the user triggers

market_move_explain

but no coin is explicitly named:

Explicit coin in query: extract and use it (e.g. "ETH why crash" -> ETH).
Context coin: if the conversation has a unique coin, use it.
Broad-market, no coin: default to
```
BTC
```
and append a notice: "No coin specified; defaulting to BTC as the broad-market representative asset."
Vague reference ("this coin", "that altcoin"): ask the user which specific coin.
Event impact, no coin: ask the user which coin to analyze.
Traditional finance (e.g. "US stocks", "China A-shares", "S&P 500"): pass through as the
```
coin
```
value.
Non-crypto, ambiguous: ask the user or route to the appropriate domain skill.

When coin defaults to BTC, the notice MUST be visible in the final report (Section 1 of the market move template).

当用户触发

market_move_explain

但未明确指定币种时：

查询中明确提及币种：提取并使用该币种（例如“ETH why crash” → ETH）。
上下文币种：若对话中存在唯一币种，使用该币种。
宽泛市场、无指定币种：默认使用
```
BTC
```
并添加提示：“未指定币种；默认使用BTC作为宽泛市场代表资产。”
模糊指代（“这个币种”、“那个山寨币”）：询问用户具体币种。
事件影响、无指定币种：询问用户要分析的币种。
传统金融（例如“美股”、“A股”、“S&P 500”）：直接作为
```
coin
```
值传递。
非加密领域、模糊需求：询问用户或路由到对应领域的Skill。

当默认使用BTC时，提示必须在最终报告中可见（市场波动模板的第1节）。

Cross-skill routing at Step 1

步骤1的跨Skill路由

User signal	Route to
“Is it safe / honeypot / blacklist”	`gate-info-risk` (primary)
“Trace this address / on-chain / TVL / reserves”	`gate-info-web3` (primary)
“Analyze this coin / fundamentals / technicals / macro” (research-first)	`gate-info-research` (primary)

用户信号	路由至
“是否安全/蜜罐/黑名单”	`gate-info-risk` （优先）
“追踪地址/链上数据/TVL/储备金”	`gate-info-web3` （优先）
“分析币种/基本面/技术面/宏观”（优先调研类）	`gate-info-research` （优先）

Step 2 — Data collection

步骤2 — 数据收集

Execute the chosen playbook. Same

parallel_group

→ concurrent; wait between groups.

执行选定的剧本。同一

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:

Playbook	Shortcut
`news_brief`	`news +brief`
`event_explain`	`news +event-explain` with `--event-id` when `when: event_id_present` ; else `--coin` . Legacy `social_sentiment` still runs (not replaced). Map `market_interpretation` → X, not sentiment index.
`market_wide_intel`	`info +market-overview` replaces legacy `market_overview` only; `open_web` always runs
`community_intel`	`news +community-scan`
`intel_plus_market`	`news +brief` then `info +coin-overview` ( `shortcut` → `info_shortcut` ; see playbook `shortcut_block_order` )

market_move_explain

has no

+market-move-explain

shortcut in v0.7.6 — keep the

gate-cli news events explain-market-move

multi-step path.

exchange_listings
: base invocation uses

limit

format

only; if the user supplied

symbol

, add

--coin {symbol}

when the CLI supports it (

get-exchange-announcements --help

event_explain
: when

shortcuts_enabled

and

event_id

is set, pass

--event-id

via shortcut

args_when

— do not also run legacy

get-event-detail

. When shortcuts are disabled and

event_id

is known, run legacy

get-event-detail

only. For price-move attribution, route to

market_move_explain

market_move_explain
: Execute in two groups (use the full CLI paths below —

explain-market-move

lives under

news events

, NOT

news feed

Group A (parallel, core data):
```
gate-cli news events explain-market-move
```
(Tavily-based news/event evidence with AI summary) +
```
gate-cli info marketsnapshot get-market-snapshot
```
(current price, change%, volume) +
```
gate-cli info marketdetail get-orderbook
```
(bid/ask wall, depth imbalance).
Group B (after Group A completes, parallel):
```
gate-cli info markettrend get-technical-analysis
```
(TA signals across timeframes) +
```
gate-cli info coin get-coin-info
```
(fundamentals) + community commands (
```
gate-cli news feed search-x
```
+
```
gate-cli news feed get-social-sentiment
```
) only when
```
symbol != BTC
```
. For BTC, skip community — Tavily already captures macro/geopolitical signals.

After data collection, the agent MUST perform its own final attribution synthesis using ALL collected data. Do not treat any single tool output as the authoritative conclusion. Prioritize events with higher

relevance_score

as primary drivers, cross-referencing with price/volume data from the snapshot and orderbook.

Info failures: In

intel_plus_market

and

market_move_explain

, info/community commands are optional — if they fail, mark that section as unavailable and still deliver the report.

当

shortcuts_enabled

时，参考skills/_shared/cli-version-routing.md运行剧本的

shortcut

模块：

剧本	快捷指令
`news_brief`	`news +brief`
`event_explain`	当 `when: event_id_present` 时，使用 `news +event-explain` 并传递 `--event-id` ；否则使用 `--coin` 。旧版 `social_sentiment` 仍需运行（未被替代）。将 `market_interpretation` 映射到X平台，而非情绪指数。
`market_wide_intel`	`info +market-overview` 仅替代旧版 `market_overview` ； `open_web` 始终需运行
`community_intel`	`news +community-scan`
`intel_plus_market`	先运行 `news +brief` ，再运行 `info +coin-overview` （ `shortcut` → `info_shortcut` ；参考剧本的 `shortcut_block_order` ）

market_move_explain

在v0.7.6中无

+market-move-explain

快捷指令 — 需保留

gate-cli news events explain-market-move

多步骤流程。

exchange_listings
：基础调用仅使用

limit

format

参数；若用户提供

symbol

，且CLI支持（查看

get-exchange-announcements --help

），则添加

--coin {symbol}

参数。

event_explain
：当

shortcuts_enabled

且已设置

event_id

时，通过快捷指令的

args_when

传递

--event-id

— 请勿同时运行旧版

get-event-detail

。当快捷指令禁用且已知

event_id

时，仅运行旧版

get-event-detail

。若需价格波动归因，路由至

market_move_explain

。

market_move_explain
：分两组执行（使用以下完整CLI路径 —

explain-market-move

位于

news events

下，而非

news feed

）：

A组（并行执行，核心数据）：
```
gate-cli news events explain-market-move
```
（基于Tavily的新闻/事件证据及AI摘要） +
```
gate-cli info marketsnapshot get-market-snapshot
```
（当前价格、涨跌幅、成交量） +
```
gate-cli info marketdetail get-orderbook
```
（买卖盘墙、深度失衡）。
B组（A组完成后并行执行）：
```
gate-cli info markettrend get-technical-analysis
```
（多时间周期技术指标信号） +
```
gate-cli info coin get-coin-info
```
（基本面） + 社区命令（
```
gate-cli news feed search-x
```
+
```
gate-cli news feed get-social-sentiment
```
）（仅当
```
symbol != BTC
```
时运行）。对于BTC，跳过社区数据 — Tavily已涵盖宏观/地缘政治信号。

数据收集完成后，Agent必须使用所有收集到的数据自行完成最终归因合成。请勿将任何单一工具输出视为权威结论。优先将

relevance_score

较高的事件作为主要驱动因素，并结合快照及订单簿中的价格/成交量数据进行交叉验证。

Info工具调用失败：在

intel_plus_market

和

market_move_explain

中，info/社区命令为可选 — 若调用失败，标记该部分数据不可用并仍需交付报告。

Step 3 — Synthesis

步骤3 — 合成

Choose the report template based on the playbook:

market_move_explain
: use the 6-section Market move analysis template below.
All other playbooks: use the 5-section Intel briefing template below.

根据剧本选择对应的报告模板：

market_move_explain
：使用下方的6节市场波动分析模板。
其他所有剧本：使用下方的5节情报简报模板。

Intel briefing template (all playbooks except market_move_explain)

情报简报模板（除market_move_explain外的所有剧本）

Produce five sections, in this order:

markdown

undefined

生成5节内容，顺序如下：

markdown

undefined

Intel briefing -- {subject}

情报简报 -- {主题}

1. Event / news takeaway

1. 事件/新闻要点

3-5 bullets; separate verified facts from unconfirmed items

3-5条要点；区分已验证事实与未确认信息

2. Key facts and timeline

2. 关键事实与时间线

Time-ordered, verifiable items from
```
search-news
```
/
```
get-latest-events
```
/
```
get-event-detail
```
where used

按时间排序的可验证信息，来自
```
search-news
```
/
```
get-latest-events
```
/
```
get-event-detail
```
（若使用）

3. Community / UGC / X / Reddit / YouTube

3. 社区/UGC/X/Reddit/YouTube

Must cover, when the playbook includes them: UGC (
```
search-ugc
```
), X (
```
search-x
```
), and sentiment where applicable (
```
get-social-sentiment
```
)
Label every bullet with source type (e.g. UGC / X / sentiment index) -- do not state opinion as on-chain fact

当剧本包含相关命令时，必须涵盖：UGC（
```
search-ugc
```
）、X（
```
search-x
```
）及适用的情绪分析（
```
get-social-sentiment
```
）
每条要点必须标注来源类型（例如UGC/X/情绪指数） — 请勿将观点表述为链上事实

4. Market or coin background (if any)

4. 市场或币种背景（若有）

Only when the playbook includes
```
info
```
or
```
get-market-overview
```
in
```
market_wide_intel
```
; if not used, state no extra market context

仅当剧本包含
```
info
```
或
```
market_wide_intel
```
中的
```
get-market-overview
```
时添加；若未使用，标注无额外市场背景信息

5. Conclusion and what to watch

5. 结论与关注重点

Not investment advice; list follow-up items

This report is based on public data and tool output; it is not investment advice.

undefined

不提供投资建议；列出后续需关注的事项

本报告基于公开数据及工具输出，不构成投资建议。

undefined

Market move analysis template (market_move_explain only)

市场波动分析模板（仅market_move_explain）

Produce six sections, in this order:

markdown

undefined

生成6节内容，顺序如下：

markdown

undefined

Market move analysis -- {coin} ({time_range})

市场波动分析 -- {币种} ({时间范围})

[If coin was defaulted to BTC, append: "No coin specified; defaulting to BTC as the broad-market representative asset."]

[若默认使用BTC，添加：“未指定币种；默认使用BTC作为宽泛市场代表资产。”]

1. Summary

1. 摘要

[One concise attribution sentence. Synthesize: explain-market-move outer summary, supporting_events summaries, market snapshot change%, and TA signals. Prefer events with higher relevance_score as primary drivers. Do NOT copy-paste the entire Tavily summary verbatim -- distill the key narrative.]

[一句简洁的归因语句。整合：explain-market-move的外层摘要、supporting_events摘要、市场快照涨跌幅及技术指标信号。优先将relevance_score较高的事件作为主要驱动因素。请勿直接复制粘贴Tavily的完整摘要 — 提炼核心叙事。]

2. Primary drivers

2. 主要驱动因素

[2-4 latest_news items from explain-market-move. For each: title, how it likely drove the move (from its summary field), source URL, relevance_score. Sort by relevance_score descending. If relevance_score < 0.5, note it as weak signal. The outer summary in explain-market-move is a concatenation of these items' Tavily AI answers; cross-reference with individual item summaries for accuracy.]

[来自explain-market-move的2-4条latest_news条目。每条包含：标题、对价格波动的影响逻辑（来自其summary字段）、来源URL、relevance_score。按relevance_score降序排列。若relevance_score < 0.5，标注为弱信号。explain-market-move的外层摘要是这些条目Tavily AI回答的拼接结果；需结合单个条目摘要交叉验证准确性。]

3. Supporting context

3. 辅助背景

[1-2 supporting_events from the internal event pool, with first_seen_time. Pay special attention to supporting_events[].summary -- these come from the internal event pool and are NOT included in the outer summary, making them independent evidence. Market snapshot: current price, change%, volume. Order book: notable bid/ask walls or depth imbalances that explain the move magnitude.]

[来自内部事件池的1-2条supporting_events，包含first_seen_time。需特别关注supporting_events[].summary字段 — 这些来自内部事件池，未包含在外层摘要中，属于独立证据。市场快照：当前价格、涨跌幅、成交量。订单簿：影响波动幅度的显著买卖盘墙或深度失衡情况。]

4. Technical signals

4. 技术信号

[Key TA indicators from get-technical-analysis. Trend direction, support/resistance levels, RSI/MACD crossovers if available. Coin fundamentals from get-coin-info (market cap rank, supply, sector).]

[来自get-technical-analysis的关键技术指标。趋势方向、支撑/阻力位、RSI/MACD交叉信号（若有）。来自get-coin-info的币种基本面（市值排名、供应量、赛道）。]

5. Community perspective

5. 社区观点

[Non-BTC only. X highlights from search-x, sentiment score from get-social-sentiment. Label each item with source type (X / sentiment index). If BTC, state: "Community data omitted for BTC; macro/geopolitical signals are captured in Sections 2 and 3."]

[仅非BTC币种。来自search-x的X平台要点、来自get-social-sentiment的情绪得分。每条标注来源类型（X/情绪指数）。若为BTC，标注：“BTC社区数据已省略；宏观/地缘政治信号已涵盖在第2节和第3节中。”]

6. What to watch

6. 关注重点

[Follow-up catalysts, key price levels, upcoming events that could confirm or reverse the current move.]

[If data_status.is_partial: append "Partial data notice: {note if available}. Missing sources: {missing_sources if listed}."]

This report is based on public data and tool output; it is not investment advice.

undefined

[后续催化剂、关键价格水平、可能确认或逆转当前波动的 upcoming 事件。]

[若data_status.is_partial：添加“部分数据提示：{可用提示信息}。缺失来源：{列出的缺失来源}。”]

本报告基于公开数据及工具输出，不构成投资建议。

undefined

Synthesis rules for market_move_explain

market_move_explain合成规则

The agent MUST perform its own final attribution -- do not treat any single tool output as authoritative.
Cross-reference: the outer
```
summary
```
in explain-market-move is a concatenation of Tavily AI answers.
```
supporting_events[].summary
```
fields are independent evidence from the internal event pool. Both should inform the agent's attribution.
```
latest_news
```
items carry
```
relevance_score
```
(0-1). Prefer items above 0.5 as primary drivers; note weaker items as background context.
Validate news-driven narratives against market snapshot price/volume data -- a large move without matching event evidence should be acknowledged as unexplained.

Agent必须自行完成最终归因 — 请勿将任何单一工具输出视为权威结论。
交叉验证：explain-market-move的外层摘要是Tavily AI回答的拼接结果。
```
supporting_events[].summary
```
字段来自内部事件池的独立证据。两者均需作为Agent归因的依据。
```
latest_news
```
条目带有
```
relevance_score
```
（0-1）。优先将分数高于0.5的条目作为主要驱动因素；分数较低的条目标注为背景信息。
需结合市场快照的价格/成交量数据验证新闻驱动的叙事逻辑 — 若出现大幅波动但无匹配事件证据，需注明波动原因未明。

Migrate hint

迁移提示

If Step 0 had

ready_with_migration_warning

, append verbatim the migration blockquote line from skills/_shared/report-style.md (line starting with

⚙️

若步骤0中出现

ready_with_migration_warning

，需准确添加skills/_shared/report-style.md中的迁移引用行（以

⚙️

开头的行）。

Cross-skill routing + Safety rules

跨Skill路由 + 安全规则

Routing

路由

Follow skills/_shared/routing.md. Do not absorb research / web3 / risk primary intents into this skill. News-intel-specific follow-ups (after the briefing is delivered and the user asks a follow-up):

Follow-up intent	Target
"deeper research on this coin" / "is it worth attention" / "fundamentals / technicals / macro"	`gate-info-research`
"address from the event" / "what is on-chain" / "protocol TVL / reserves / smart money"	`gate-info-web3`
"is this token safe" / "honeypot" / "blacklist" / "compliance"	`gate-info-risk`
User changes `symbol` or time window and wants the same class of intel	Re-enter the same playbook with the new slots

遵循skills/_shared/routing.md。请勿将调研/链上/安全类核心意图并入本Skill。新闻情报相关的后续问题（简报交付后用户提出的跟进请求）：

后续意图	目标Skill
“对此币种进行深度调研” / “是否值得关注” / “基本面/技术面/宏观分析”	`gate-info-research`
“事件相关地址” / “链上情况” / “协议TVL/储备金/聪明资金”	`gate-info-web3`
“此代币是否安全” / “蜜罐” / “黑名单” / “合规性”	`gate-info-risk`
用户更改 `symbol` 或时间范围并需要同类情报	使用新参数重新进入同一剧本

Safety rules

安全规则

Follow skills/_shared/report-style.md. News-intel-specific:

No buy/sell advice; no price targets.
Community and UGC are first-class in Section 3 (not footnotes) when
```
community_intel
```
or relevant commands in other playbooks fire.
Never fabricate events or quotes — if empty, mark no data.

遵循skills/_shared/report-style.md。新闻情报专属规则：

不提供买卖建议；不给出价格目标。
社区及UGC内容为核心内容：当触发
```
community_intel
```
或其他剧本中的相关命令时，需在第3节中呈现（而非脚注）。
不得编造事件或引用 — 若无数据，标注无可用数据。

References

参考文档

File	Load when...
skills/gate-news-intel/references/scenarios.md	Picking among brief / event / community / listings / market-wide.
skills/gate-news-intel/references/cli-reference.md	Flag tables for `news` and optional `info` commands.
skills/gate-news-intel/references/troubleshooting.md	Optional flags, `get-exchange-announcements` filters, empty `event_id` .
skills/_shared/preflight.md	Step 0.
skills/_shared/routing.md	Cross-skill matrix.
skills/_shared/report-style.md	Shared report rules.

文件	适用场景
skills/gate-news-intel/references/scenarios.md	在简报/事件/社区/上线/全市场剧本中选择时参考。
skills/gate-news-intel/references/cli-reference.md	`news` 及可选 `info` 命令的参数表参考。
skills/gate-news-intel/references/troubleshooting.md	可选参数、 `get-exchange-announcements` 过滤器、空 `event_id` 问题排查参考。
skills/_shared/preflight.md	步骤0参考。
skills/_shared/routing.md	跨Skill路由矩阵参考。
skills/_shared/report-style.md	共享报告规则参考。