skills/gate-info-macroimpact/SKILL.md
Macro-driven crypto via Gate-Info and Gate-News MCP. Use this skill whenever macro (CPI, NFP, Fed, rates, payrolls) ties to crypto, calendar, or indicator-price links. Trigger phrases include CPI and BTC, macro today, Fed, NFP, rates. Route: price/technicals → gate-info-coinanalysis or gate-info-trendanalysis; headlines → gate-news-briefing; attribution → gate-news-eventexplain. Tools: info_macro_* (calendar, indicator, summary), news_feed_search_news, info_marketsnapshot_get_market_snapshot.
npx skillsauth add gate/gate-skills gate-info-macroimpactInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
⚠️ 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, and per-skill version checks when scripts/ is present).
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 skill may include scripts/update-skill.sh and, in full source trees, scripts/update-skill.ps1 for optional maintenance checks against the official Gate Skills repository. The shared policy is defined in info-news-runtime-rules.md.
Maintenance flow:
check only when you need to compare the installed skill with the official repo.check never rewrites files.update_available, ask the user before apply.apply rewrites only this skill's local directory under the active skills root.| MCP Server | Status | |------------|--------| | Gate-Info | ✅ Required | | Gate-News | ✅ Required |
Query Operations (Read-only)
gate-mcp-cursor-installergate-mcp-codex-installergate-mcp-claude-installergate-mcp-openclaw-installer| User Intent | Keywords | Action |
|-------------|----------|--------|
| 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 |
gate-info-research (if available).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.
| Step | MCP Tool | Parameters | Retrieved Data | Parallel |
|------|----------|------------|----------------|----------|
| 1a | info_macro_get_economic_calendar | start_date={today}, end_date={today+14d} | Upcoming economic events | Yes |
| 1b | info_macro_get_macro_indicator | mode="latest", indicator={event_keyword} | Latest value of the specific macro indicator | Yes |
| 1c | news_feed_search_news | query={event_keyword}, limit=5, sort_by="importance" | Related news articles | Yes |
| 1d | info_marketsnapshot_get_market_snapshot | symbol={coin}, timeframe="1d" | Current market data for the correlated coin | Yes |
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.
The LLM must:
## Macro-Economic Impact Analysis
> Generated: {timestamp} | Related Asset: {coin}
### Economic Calendar
| Date | Event | Previous | Forecast | Actual | Impact |
|------|-------|----------|----------|--------|--------|
| {date} | {event_name} | {previous} | {forecast} | {actual or "Pending"} | {High/Medium/Low} |
### Key Indicator: {indicator_name}
| Metric | Value |
|--------|-------|
| Latest Value | {value} |
| Previous Value | {previous} |
| Change | {change} ({direction}) |
**Interpretation**: {LLM analysis}
### Crypto Market Correlation
| Metric | Value | Context |
|--------|-------|---------|
| {coin} Price | ${price} | — |
| 24h Change | {change_24h}% | — |
**Historical Pattern**: {LLM analysis}
### Related News
1. [{title}]({source}) — {time}
### Impact Assessment
{LLM: 3–5 sentences on surprise factor, risk-on/risk-off, levels to watch, upcoming events}
### Risk Factors
{Data-driven risk alerts}
> Macroeconomic impacts on crypto are complex and non-deterministic. This does not constitute investment advice.
| Condition | Assessment | |-----------|------------| | 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 = Pending | Upcoming — markets may position ahead of release | | BTC 24h change > 5% coinciding with macro event | Significant move correlating with macro release | | No related news found | Limited market commentary — event may not yet be widely covered |
| Error Type | Handling |
|------------|----------|
| 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 fail | Return error; suggest user try again later |
| Indicator not found | Suggest similar indicators; ask user to clarify |
| No upcoming macro events | Inform user; show recent past events if available |
| User Follow-up Intent | Route 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 |
info-news-runtime-rules.md), this skill does not invoke additional third-party data services.tools
Exchange listing tracker. Use this skill whenever the user asks about exchange listing, delisting, or maintenance announcements. Trigger phrases include: any new coins listed recently, what did Binance list, new listings, delisted. MCP tools: news_feed_get_exchange_announcements, info_coin_get_coin_info, info_marketsnapshot_get_market_snapshot.
testing
Event attribution and explanation. Use this skill ONLY when the user's query is exclusively about the reason behind a price move with no other analysis dimensions. Trigger phrases: why did X crash, what just happened, why is it pumping, what caused. If the query ALSO mentions fundamentals, risk check, technicals, or any other analysis dimension, use gate-info-research instead — it handles multi-dimension queries in a single unified report.
tools
Community sentiment via Gate-News MCP, X/Twitter-first. Use for social discussion, KOL takes, or opinion on a coin or topic. Triggers: what does the community think about ETH, Twitter or X sentiment, what are people saying, KOL opinions. Reddit, Discord, Telegram when search_ugc is available; until then label output as X/Twitter-only. Tools: news_feed_search_x, news_feed_get_social_sentiment.
testing
News briefing. Use this skill ONLY when the user's query is exclusively about recent news or headlines with no other analysis dimensions. Trigger phrases: what happened recently, today's highlights, crypto news, any new updates. If the query ALSO mentions coin analysis, risk check, technicals, or any other analysis dimension, use gate-info-research instead — it handles multi-dimension queries in a single unified report.