Back to Details

gate-info-macroimpact

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

gate-info-macroimpact

gate-info-macroimpact

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.
The Macro-Economic Impact Analysis Skill. When the user asks about the impact of macro data/events on the crypto market, the system calls MCP tools in parallel to fetch economic calendar, macro indicators (or summary), related news, and correlated coin market data, then the LLM produces a structured correlation analysis report.
Trigger Scenarios: User mentions macroeconomic events/indicators and crypto market impact, e.g., "how does non-farm payroll affect BTC", "any macro data today", "Fed meeting impact on the market", "has CPI been released".
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。当用户询问宏观数据/事件对加密货币市场的影响时，系统会并行调用MCP工具获取经济日历、宏观指标（或摘要）、相关新闻以及关联币种的市场数据，随后由LLM生成结构化的关联分析报告。
触发场景：用户提及宏观经济事件/指标及其对加密货币市场的影响，例如“非农就业数据如何影响BTC”“今日有哪些宏观数据”“美联储会议对市场的影响”“CPI数据发布了吗”。
逐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-research
.
Before Trigger update, MCP tool selection, or any legacy Execution Workflow, run a deterministic shell probe:
bash
PRIMARY_SKILL="gate-info-research"
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-research/SKILL.md
    and its playbook contract. Carry over the minimum context: macro topic plus optional 
    symbol
    , 
    indicator
    , or 
    country
    when the user supplied them.
  • __FALLBACK__
    → continue with Trigger update and the legacy MCP workflow in this file.
此遗留Skill是主CLI Skill 
gate-info-research
的兼容别名。
在触发更新、选择MCP工具或执行任何遗留工作流之前，运行确定性shell探测：
bash
PRIMARY_SKILL="gate-info-research"
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-info-research/SKILL.md
    及其剧本约定。仅传递必要上下文：宏观主题，以及用户提供的可选
    symbol
    、
    indicator
    或
    country
    。
  • __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
或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 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-info-macroimpact/scripts/update-skill.sh" check "gate-info-macroimpact"
PowerShell:
powershell
$env:GATE_SKILL_CHECK_STRICT = '1'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" check "gate-info-macroimpact"
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-info-macroimpact/scripts/update-skill.sh" check "gate-info-macroimpact"
PowerShell：
powershell
$env:GATE_SKILL_CHECK_STRICT = '1'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" check "gate-info-macroimpact"
结果语义：
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
 → 检查脚本无阻塞，可继续执行。

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
or 
revoke-pending
.
If 
update_available
:
  1. STOP — do NOT proceed to Execution yet.
  2. Inform the user (e.g. newer version available; summarize if helpful).
  3. 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-macroimpact/scripts/update-skill.sh" apply "gate-info-macroimpact"
bash
bash "$HOME/.cursor/skills/gate-info-macroimpact/scripts/update-skill.sh" revoke-pending "gate-info-macroimpact"
powershell
$env:GATE_SKILL_CONFIRM_TOKEN = '<paste from check stdout>'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" apply "gate-info-macroimpact"
powershell
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" revoke-pending "gate-info-macroimpact"
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
：
  1. 停止操作 — 暂不执行后续流程。
  2. 告知用户（例如：有新版本可用；如有帮助可简要说明更新内容）。
  3. 等待用户回复 — 阻塞步骤。
    硬性规则（Cursor/Agent）：当
    check
    返回**
    update_available
    、
    BLOCK_UNTIL_USER_CONFIRMS_UPDATE
    或严格的
    exit 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-info-macroimpact/scripts/update-skill.sh" apply "gate-info-macroimpact"
bash
bash "$HOME/.cursor/skills/gate-info-macroimpact/scripts/update-skill.sh" revoke-pending "gate-info-macroimpact"
powershell
$env:GATE_SKILL_CONFIRM_TOKEN = '<粘贴check标准输出中的内容>'
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" apply "gate-info-macroimpact"
powershell
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.cursor\skills\gate-info-macroimpact\scripts\update-skill.ps1" revoke-pending "gate-info-macroimpact"
若步骤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
    为本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
    （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

MCP依赖

Legacy path only — this section applies when Step 0 emitted 
__FALLBACK__
.
仅适用于遗留路径 — 当步骤0输出
__FALLBACK__
时，本节生效。

Required MCP Servers

必需的MCP服务器

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

MCP Tools Used

使用的MCP工具

Query Operations (Read-only)
  • info_macro_get_economic_calendar
  • info_macro_get_macro_indicator
  • info_macro_get_macro_summary (use when no specific indicator is named)
  • news_feed_search_news
  • info_marketsnapshot_get_market_snapshot
查询操作（只读）
  • info_macro_get_economic_calendar
  • info_macro_get_macro_indicator
  • info_macro_get_macro_summary（未指定具体指标时使用）
  • news_feed_search_news
  • info_marketsnapshot_get_market_snapshot

Authentication

认证信息

  • API Key Required: No
  • Credentials Source: None; this skill uses read-only Gate Info / Gate News MCP access only.
  • 是否需要API密钥：否
  • 凭证来源：无；本Skill仅使用只读的Gate Info / Gate News MCP访问权限。

Installation Check

安装检查

  • Required: Gate-Info, 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-Info、Gate-News
  • 安装方式：继续前请使用当前主机IDE的本地Gate MCP安装流程完成安装。
  • 仅当当前环境中存在必需的Gate MCP服务器时，才可继续执行。

Routing Rules

路由规则

Legacy path only — when Step 0 emitted 
__ROUTE_CLI__
, routing is delegated to 
gate-info-research
.
User IntentKeywordsAction
Macro event impact on crypto"non-farm payroll BTC" "CPI crypto impact" "Fed decision market"Execute this Skill's full workflow
Upcoming economic calendar"any macro data today" "economic calendar this week"Execute this Skill (calendar-focused mode)
Specific macro indicator query"what's the current CPI" "latest GDP data"Execute this Skill (indicator-focused mode)
Pure coin analysis without macro angle"analyze SOL" "how is BTC"Route to 
gate-info-coinanalysis
Market overview"how's the market"Route to 
gate-info-marketoverview
News only"any crypto news"Route to 
gate-news-briefing
Why price moved"why did BTC crash"Route to 
gate-news-eventexplain
仅适用于遗留路径 — 当步骤0输出
__ROUTE_CLI__
时，路由委托给
gate-info-research
。
用户意图关键词操作
宏观事件对加密货币的影响"non-farm payroll BTC" "CPI crypto impact" "Fed decision market"执行本Skill的完整工作流
即将到来的经济日历"any macro data today" "economic calendar this week"执行本Skill（日历聚焦模式）
特定宏观指标查询"what's the current CPI" "latest GDP data"执行本Skill（指标聚焦模式）
无宏观角度的纯币种分析"analyze SOL" "how is BTC"路由至
gate-info-coinanalysis
市场概览"how's the market"路由至
gate-info-marketoverview
仅新闻查询"any crypto news"路由至
gate-news-briefing
价格波动原因"why did BTC crash"路由至
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：多维度意图检查

  • If the query is about macro-economic impact on crypto, proceed with this Skill.
  • If the query also mentions coin-specific fundamentals, risk check, or on-chain data beyond the macro angle, route to 
    gate-info-research
    (if available).
  • 若查询涉及宏观经济对加密货币的影响，则继续执行本Skill。
  • 若查询同时提及币种特定基本面、风险检查或链上数据等非宏观角度内容，则路由至
    gate-info-research
    （若可用）。

Step 1: Intent Recognition & Parameter Extraction

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

Extract from user input:
  • event_keyword
    : Macro event/indicator name (e.g., "CPI", "non-farm payroll", "Fed meeting", "interest rate")
  • coin
    (optional): Related coin (default: BTC if not specified)
  • time_range
    : Time window for calendar/news (default: 7d for calendar, 24h for news)
If the macro event cannot be identified, ask the user to clarify — do not guess.
从用户输入中提取：
  • event_keyword
    ：宏观事件/指标名称（例如"CPI"、"非农就业数据"、"美联储会议"、"利率"）
  • coin
    （可选）：相关币种（默认：未指定时为BTC）
  • time_range
    ：日历/新闻的时间范围（默认：日历为7天，新闻为24小时）
若无法识别宏观事件，请询问用户澄清 — 请勿猜测。

Step 2: Call MCP Tools in Parallel

步骤2：并行调用MCP工具

StepMCP ToolParametersRetrieved DataParallel
1a
info_macro_get_economic_calendar
start_date={today}, end_date={today+14d}
Upcoming economic eventsYes
1b
info_macro_get_macro_indicator
mode="latest", indicator={event_keyword}
Latest value of the specific macro indicatorYes
1c
news_feed_search_news
query={event_keyword}, limit=5, sort_by="importance"
Related news articlesYes
1d
info_marketsnapshot_get_market_snapshot
symbol={coin}, timeframe="1d"
Current market data for the correlated coinYes
Note: If a specific indicator is not mentioned, use 
info_macro_get_macro_summary
instead of 
info_macro_get_macro_indicator
for Step 1b.
All four primary tools run in parallel when applicable.
步骤MCP工具参数获取数据是否并行
1a
info_macro_get_economic_calendar
start_date={today}, end_date={today+14d}
即将到来的经济事件是
1b
info_macro_get_macro_indicator
mode="latest", indicator={event_keyword}
特定宏观指标的最新值是
1c
news_feed_search_news
query={event_keyword}, limit=5, sort_by="importance"
相关新闻文章是
1d
info_marketsnapshot_get_market_snapshot
symbol={coin}, timeframe="1d"
关联币种的当前市场数据是
注意：若未提及具体指标，则步骤1b使用
info_macro_get_macro_summary
替代
info_macro_get_macro_indicator
。
适用时，四个主工具会并行运行。

Step 3: LLM Aggregation

步骤3：LLM聚合

The LLM must:
  • Match the user's query to relevant economic calendar events
  • Compare actual vs forecast vs previous values (surprise factor)
  • Correlate macro data with crypto price action
  • Reference historical patterns where appropriate
  • Combine with latest news for context
LLM必须完成以下操作：
  • 将用户查询与相关经济日历事件匹配
  • 对比实际值、预测值与历史值（意外因素）
  • 将宏观数据与加密货币价格走势关联
  • 酌情参考历史模式
  • 结合最新新闻提供上下文

Report Template

报告模板

Legacy path only — this section applies when Step 0 emitted 
__FALLBACK__
.
markdown
undefined
仅适用于遗留路径 — 当步骤0输出
__FALLBACK__
时，本节生效。
markdown
undefined

Macro-Economic Impact Analysis

宏观经济影响分析

Generated: {timestamp} | Related Asset: {coin}
生成时间：{timestamp} | 相关资产：{coin}

Economic Calendar

经济日历

DateEventPreviousForecastActualImpact
{date}{event_name}{previous}{forecast}{actual or "Pending"}{High/Medium/Low}
日期事件历史值预测值实际值影响程度
{date}{event_name}{previous}{forecast}{actual 或 "待发布"}{高/中/低}

Key Indicator: {indicator_name}

关键指标：{indicator_name}

MetricValue
Latest Value{value}
Previous Value{previous}
Change{change} ({direction})
Interpretation: {LLM analysis}
指标数值
最新值{value}
历史值{previous}
变化{change} ({方向})
解读：{LLM分析内容}

Crypto Market Correlation

加密货币市场关联

MetricValueContext
{coin} Price${price}—
24h Change{change_24h}%—
Historical Pattern: {LLM analysis}
指标数值上下文
{coin} 价格${price}—
24小时涨跌幅{change_24h}%—
历史模式：{LLM分析内容}

Related News

相关新闻

  1. {title} — {time}
  1. {title} — {time}

Impact Assessment

影响评估

{LLM: 3–5 sentences on surprise factor, risk-on/risk-off, levels to watch, upcoming events}
{LLM生成3-5句话，涵盖意外因素、风险偏好、关注价位、即将到来的事件}

Risk Factors

风险因素

{Data-driven risk alerts}
Macroeconomic impacts on crypto are complex and non-deterministic. This does not constitute investment advice.

---
{基于数据的风险预警}
宏观经济对加密货币的影响复杂且具有不确定性。本报告不构成投资建议。

---

Decision Logic

决策逻辑

ConditionAssessment
Actual > Forecast (inflation metrics like CPI)Hotter-than-expected — may delay rate cuts, bearish for risk assets
Actual < Forecast (inflation metrics)Cooler-than-expected — supports rate cut narrative, bullish for risk assets
Actual > Forecast (employment data)Stronger labor market — mixed (growth positive but rate cut delay)
Actual < Forecast (employment data)Weakening labor market — supports cuts but signals slowdown
Event status = PendingUpcoming — markets may position ahead of release
BTC 24h change > 5% coinciding with macro eventSignificant move correlating with macro release
No related news foundLimited market commentary — event may not yet be widely covered
条件评估
实际值 > 预测值（CPI等通胀指标）强于预期 — 可能推迟降息，对风险资产利空
实际值 < 预测值（通胀指标）弱于预期 — 支持降息预期，对风险资产利好
实际值 > 预测值（就业数据）劳动力市场强劲 — 影响复杂（增长利好但降息推迟）
实际值 < 预测值（就业数据）劳动力市场疲软 — 支持降息但预示经济放缓
事件状态 = 待发布即将到来 — 市场可能提前布局
BTC 24小时涨跌幅 >5%且与宏观事件同步宏观数据发布引发显著波动
未找到相关新闻市场评论有限 — 事件可能尚未被广泛报道

Error Handling

错误处理

Error TypeHandling
info_macro_get_economic_calendar
fails		Skip calendar section; focus on indicator + news
info_macro_get_macro_indicator
fails		Skip indicator detail; use calendar data if available
news_feed_search_news
fails		Skip news section
info_marketsnapshot_get_market_snapshot
fails		Skip market correlation section
All Tools failReturn error; suggest user try again later
Indicator not foundSuggest similar indicators; ask user to clarify
No upcoming macro eventsInform user; show recent past events if available
错误类型处理方式
info_macro_get_economic_calendar
执行失败		跳过日历部分；聚焦指标+新闻
info_macro_get_macro_indicator
执行失败		跳过指标详情；若可用则使用日历数据
news_feed_search_news
执行失败		跳过新闻部分
info_marketsnapshot_get_market_snapshot
执行失败		跳过市场关联部分
所有工具执行失败返回错误；建议用户稍后重试
未找到指标推荐类似指标；询问用户澄清
无即将到来的宏观事件告知用户；若可用则显示近期已发生事件

Cross-Skill Routing

跨Skill路由

User Follow-up IntentRoute To
"Analyze BTC for me"
gate-info-coinanalysis
"What's the technical outlook?"
gate-info-trendanalysis
"How's the overall market?"
gate-info-marketoverview
"Why did BTC crash?"
gate-news-eventexplain
"What about DeFi impact?"
gate-info-defianalysis
"Any crypto news?"
gate-news-briefing
用户后续意图路由至
"帮我分析BTC"
gate-info-coinanalysis
"技术面展望如何？"
gate-info-trendanalysis
"整体市场情况如何？"
gate-info-marketoverview
"BTC为何暴跌？"
gate-news-eventexplain
"对DeFi的影响如何？"
gate-info-defianalysis
"有哪些加密货币新闻？"
gate-news-briefing

Safety Rules

安全规则

  1. No price predictions: Describe potential impacts and historical patterns, not specific price targets.
  2. Correlation ≠ causation: State that macro–crypto links are probabilistic.
  3. Data transparency: Label source, time, and reference period for each data point.
  4. No trading advice: Do not recommend specific trades based on macro data.
  5. Flag uncertainty: When data is pending, label forecast vs actual clearly.
  6. Historical patterns disclaimer: Past performance does not guarantee future results.
  7. Age & eligibility: Intended for users aged 18 or above with full civil capacity in their jurisdiction.
  8. Data flow: The host agent processes user prompts; this skill directs read-only Gate-Info and Gate-News MCP tools listed above. The LLM synthesizes from tool results. This skill does not invoke additional third-party data services.
  1. 禁止价格预测：描述潜在影响和历史模式，不得给出具体价格目标。
  2. 相关性≠因果性：说明宏观与加密货币的关联具有概率性。
  3. 数据透明：为每个数据点标注来源、时间和参考周期。
  4. 禁止交易建议：不得基于宏观数据推荐具体交易操作。
  5. 标注不确定性：当数据待发布时，明确区分预测值与实际值。
  6. 历史模式免责声明：过往表现不代表未来结果。
  7. 年龄与资格：仅面向18周岁及以上且在所在司法辖区具备完全民事行为能力的用户。
  8. 数据流：主机Agent处理用户提示；本Skill仅调用上述列出的只读 Gate-Info和Gate-News MCP工具。LLM基于工具结果进行合成。本Skill不会调用额外第三方数据服务。