gate-news-briefing

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 ./references/gate-runtime-rules.md
→ Also read ./references/info-news-runtime-rules.md for gate-info / gate-news shared rules (tool degradation, report standards, security, and output standards).

• - 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.

The crypto industry "morning briefing" Skill. The user asks what's been happening; the system calls 3 MCP Tools in parallel to fetch major events + trending news + social sentiment, then the LLM aggregates into a layered news briefing.

Trigger Scenarios: User asks about recent/today's news, headlines, or what's been happening.

---

MCP Dependencies

Required MCP Servers

MCP Server	Status
Gate-News	✅ Required

MCP Tools Used

Query Operations (Read-only)

• - newseventsgetlatestevents
• newsfeedgetsocialsentiment
• newsfeedsearch_news

Authentication

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

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.

Routing Rules

User Intent	Keywords	Action
General news briefing	"what happened recently" "today's headlines" "crypto news" "any new updates"	Execute this Skill's full workflow
Coin-specific news

"any SOL news" "what's happening with BTC" | Execute this Skill with coin parameter set to that coin | | Reason for a move | "why did BTC crash" "what just happened" | Route to gate-news-eventexplain | | Overall market conditions | "how's the market" | Route to gate-info-marketoverview | | Exchange announcements | "any new listings on Binance" "new coins lately" | Route to gate-news-listing |

---

Execution Workflow

Step 0: Multi-Dimension Intent Check

Before executing this Skill, check if the user's query involves multiple analysis dimensions:

• - If the query is exclusively about recent news or headlines, proceed with this Skill.
• If the query also mentions coin analysis, risk check, technicals, fundamentals, or any other analysis dimension beyond news, route to gate-info-research — it handles multi-dimension queries with unified tool deduplication and coherent report aggregation.

Step 1: Intent Recognition & Parameter Extraction

Extract from user input:

• - coin (optional): Whether a specific coin is targeted, e.g., "SOL news" → coin=SOL
• INLINECODE8: Time window (default: 24h; if user says "this week" → 7d)
• INLINECODE9 (optional): Whether focused on a specific topic (e.g., "regulation", "ETF", "DeFi")

Step 2: Call 3 MCP Tools in Parallel

General Briefing Mode (no specific coin):

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	INLINECODE10	INLINECODE11	Major event list (with impact rating)	Yes
1b

news_feed_search_news | sort_by="importance", limit=10, lang="en" | Top news ranked by importance | Yes |
| 1c | news_feed_get_social_sentiment | (no specific coin) | Market-wide social sentiment overview | Yes |

Coin-Specific Mode (user specified a coin):

Step	MCP Tool	Parameters	Retrieved Data	Parallel
1a	INLINECODE15	INLINECODE16	Events related to that coin	Yes
1b

news_feed_search_news | coin={coin}, sort_by="importance", limit=10 | News related to that coin | Yes |
| 1c | news_feed_get_social_sentiment | coin={coin} | Social sentiment for that coin | Yes |

Step 3: LLM Aggregation

The LLM must:

1. 1. De-duplicate events and news (the same event may appear in both feeds)
2. Rank by impact/importance
3. Categorize (Regulation, Projects, Market, Technology, etc.)
4. Combine with social sentiment to identify market focus areas

Step 4: Output Structured Briefing

---

Report Template

CODEBLOCK0

Coin-Specific Mode Template

CODEBLOCK1

---

De-duplication & Ranking Logic

Rule	Description
Event-News de-duplication	If an event title closely matches a news headline (similarity > 80%), merge into one entry — events take priority
Importance ranking

Events ranked by impact rating; news ranked by importance field |
| Time ordering | At equal importance, reverse chronological (newest first) |
| Categorization | News auto-categorized: Regulation & Policy / Projects & Technology / Market & Trading / DeFi / Other |

---

Error Handling

Error Type	Handling
INLINECODE22 fails	Skip "Major Events" section; show news only
INLINECODE23 fails

Show events only; note "News feed temporarily unavailable" |
| news_feed_get_social_sentiment fails | Skip "Social Sentiment" section |
| All Tools fail | Return error message; suggest the user try again later |
| Too few news items (< 3) | Expand time range (e.g., 24h → 48h) and note the change |

---

Cross-Skill Routing

User Follow-up Intent	Route To
"Why did XX pump/dump?"	INLINECODE25
"Analyze XX for me"

gate-info-coinanalysis |
| "How's the overall market?" | gate-info-marketoverview |
| "Any new listings on Binance?" | gate-news-listing |
| "Tell me more about ETF" | Deep search via news_feed_search_news(query="ETF") |

---

Safety Rules

1. 1. Source attribution: Every news item must include the source (media name) and time
2. No interpretive speculation: News summaries must remain objective — no subjective extrapolation
3. No fabricated news: If data is insufficient, reduce the number of items rather than fabricate content
4. Neutral handling of sensitive topics: Maintain neutral tone when covering regulation, politics, or other sensitive subjects
5. Timeliness labeling: Clearly label the time range covered by the data