Skill: gaixianggeng/gate-news-briefing-staging (version 1.0.1)

--- name: gate-news-briefing version: "2026.4.7-1" updated: "2026-04-07" description: "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." required_credentials: [] required_env_vars: [] required_permissions: [] --- # 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)** - news_events_get_latest_events - news_feed_get_social_sentiment - news_feed_search_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 - `time_range`: Time window (default: 24h; if user says "this week" → 7d) - `topic` (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 | `news_events_get_latest_events` | `time_range={time_range}, limit=10` | 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 | `news_events_get_latest_events` | `coin={coin}, time_range={time_range}, limit=10` | 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. 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 ```markdown ## Crypto Industry News Briefing > Time range: Past {time_range} | Generated: {timestamp} ### 🔴 Major Events {Top 1-3 events by impact, each containing:} **1. {event_title}** - Time: {event_time} - Impact: {Market/industry impact assessment} - Involved: {Related coins/projects/institutions} - Details: {2-3 sentence summary} **2. {event_title}** - ... --- ### 📰 Trending News {Grouped by category, 2-5 items per category:} **Regulation & Policy** 1. {title} — {source} ({time}) {One-sentence summary} 2. ... **Projects & Technology** 1. {title} — {source} ({time}) {One-sentence summary} 2. ... **Market & Trading** 1. {title} — {source} ({time}) {One-sentence summary} 2. ... **DeFi / NFT / GameFi** (if applicable) 1. ... --- ### 💬 Social Sentiment | Metric | Status | |--------|--------| | Overall Sentiment | {Bullish/Bearish/Neutral} | | Discussion Volume | {High/Medium/Low} | | Trending Topics | {topic1}, {topic2}, {topic3} | | KOL Focus | {focus description} | **Top 5 Coins by Discussion Volume** (if data available) | Rank | Coin | Volume Change | Sentiment | |------|------|--------------|-----------| | 1 | {coin} | +{change}% | {Bullish/Bearish} | | 2 | ... | ... | ... | --- ### 📌 Worth Watching {LLM distills 2-3 noteworthy points from news and sentiment:} - {Point 1} - {Point 2} - {Point 3} > The above is a news summary and does not constitute investment advice. ``` ### Coin-Specific Mode Template ```markdown ## {symbol} News Briefing > Time range: Past {time_range} | Generated: {timestamp} ### Recent Key Events 1. {event} — {time} {details} 2. ... ### Related News 1. [{title}]({url}) — {source} ({time}) {summary} 2. ... ### Social Sentiment - Discussion Volume: {High/Medium/Low} (vs 7-day average: {change}%) - Sentiment Bias: {Bullish/Bearish/Neutral} - KOL Views: {Summary of key KOL opinions} ### Summary {1-2 sentence summary of the coin's recent news landscape} ``` --- ## 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 | |------------|----------| | `news_events_get_latest_events` fails | Skip "Major Events" section; show news only | | `news_feed_search_news` 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?" | `gate-news-eventexplain` | | "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. **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

path: references/gate-runtime-rules.md
content: ---
name: gate-news-briefing-runtime-rules
version: "2026.4.7-1"
updated: "2026-04-07"
description: "Packaged runtime rules for gate-news-briefing so every mandatory artifact referenced by SKILL.md is included in the published bundle."
---

# Gate News Briefing Runtime Rules

> Packaged runtime rules for `gate-news-briefing`.
> This file is bundled with the skill so reviewers can audit the required guardrails without depending on files outside this directory.

## 1. Intent and Scope

- Use this skill only for news and headline briefing requests.
- If the user asks for attribution, coin fundamentals, or another dedicated dimension, route to the matching skill instead of stretching this one.

## 2. Tool Scope

- Use only the MCP tools documented in `SKILL.md`.
- Do not call undocumented tools, browser flows, or unrelated system tools.

## 3. Installation and Fallback

- This skill requires the Gate News MCP server.
- If the required MCP tools are unavailable, stop and provide setup guidance or graceful partial output as documented in `SKILL.md`.

## 4. Persistence and Secrets

- This skill is read-only.
- This skill does not install software, write local files, or handle API secrets during normal execution.


path: references/info-news-runtime-rules.md
content: ---
name: gate-news-briefing-info-news-runtime-rules
version: "2026.4.7-1"
updated: "2026-04-07"
description: "Packaged info/news common runtime rules for gate-news-briefing."
---

# Info & News Common Runtime Rules

> Packaged common rules for `gate-info-*` and `gate-news-*` review.

## 1. MCP Availability

- Before using MCP-dependent capabilities, confirm the required Gate Info or Gate News tools are available.
- If a required tool is missing, explain the limitation and degrade gracefully instead of fabricating data.

## 2. Tool Degradation

- A single MCP tool failure must not block the entire skill.
- Skip the unavailable dimension, label it clearly in the report, and continue with the remaining data.
- If all required tools fail, return a concise failure summary and suggest checking MCP availability.

## 3. Output Standards

- Use markdown output.
- Match the user's language.
- Use a neutral, data-driven tone and avoid explicit buy/sell advice.

## 4. Security and Privacy

- Do not expose credentials or secrets in chat.
- Use only publicly available on-chain, market, and news data returned by the documented MCP tools.


path: references/mcp.md
content: ---
name: gate-news-briefing-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for Gate news briefing: parallel news/event/sentiment retrieval, deduplication, ranking, and degradation-safe reporting."
---

# Gate News Briefing MCP Specification

> Authoritative MCP execution document for `gate-news-briefing`.

## 1. Scope and Trigger Boundaries

In scope:
- Recent market news briefing
- Coin-specific headline and event updates
- Social sentiment snapshot integrated with event/news feeds

Out of scope:
- Event causality deep-dive -> `gate-news-eventexplain`
- Listing/delisting tracking -> `gate-news-listing`
- Multi-dimension analysis (news + technical/fundamental/risk) -> `gate-info-research`

## 2. MCP Detection and Fallback

Detection:
1. Verify Gate-News MCP availability.
2. Probe one read tool (`news_feed_search_news`).

Fallback:
- MCP unavailable: return setup guidance and no-fabrication fallback.
- Partial tool failure: continue with available sources and mark missing sections as degraded.

## 3. Authentication

- API key not required.
- If service auth/rate-limit errors occur, return transparent message and fallback summary.

## 4. MCP Resources

No MCP Resources required.

## 5. Tool Calling Specification

| Tool | Required inputs | Key return fields | Common errors |
|---|---|---|---|
| `news_events_get_latest_events` | optional `coin`, `time_range`, `limit` | event title/time/impact/source | empty recent events |
| `news_feed_search_news` | optional `coin/topic`, sort, limit | news list, source, timestamp, importance | query too general |
| `news_feed_get_social_sentiment` | optional `coin` | sentiment polarity, volume trend, social focus | sentiment unavailable |

## 6. Execution SOP (Non-Skippable)

### 6.1 Intent gate
1. If user asks only for briefing/headlines, continue.
2. If mixed with technical/fundamental/risk requests, route to `gate-info-research`.

### 6.2 Parallel retrieval
Run these in parallel (coin-specific or global mode):
- `news_events_get_latest_events`
- `news_feed_search_news`
- `news_feed_get_social_sentiment`

### 6.3 Aggregation and dedup
1. Deduplicate by title/time/source similarity.
2. Prioritize by impact + freshness.
3. Group into categories (regulation, macro, project, exchange, ecosystem).
4. Merge sentiment as context, not as factual replacement.

### 6.4 Degradation handling
- If one source fails, keep briefing with remaining sources.
- Explicitly label degraded sections.

## 7. Output Templates

```markdown
## News Briefing ({time_range})
- Generated At: {timestamp}
- Coverage: {global_or_coin}

### Major Events
1. {event_1}
2. {event_2}

### Trending Headlines
1. {headline_1}
2. {headline_2}

### Social Sentiment
- Bias: {bullish_bearish_neutral}
- Heat: {high_medium_low}
- Notes: {key_social_signal}

### Watchlist
- {watch_item_1}
- {watch_item_2}
```

## 8. Safety and Degradation Rules

1. Distinguish factual event/news items from model summaries.
2. Do not fabricate missing headlines/events when feeds are empty or degraded.
3. Keep time range explicit (default 24h unless user requests otherwise).
4. If sentiment conflicts with news flow, report both and mark uncertainty.
5. Preserve source attribution fields whenever available.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)