Skill: gate-exchange/gate-news-event-explain (version 1.0.4)

--- name: gate-news-eventexplain version: "2026.4.3-1" updated: "2026-04-03" description: "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." required_credentials: [] required_env_vars: [] required_permissions: [] --- # gate-news-eventexplain ## 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 shared rules (tool degradation, report standards, security, routing, and optional local maintenance when `scripts/` is present). - **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 "Why is it pumping/dumping?" Skill. When the market experiences abnormal volatility and the user asks why, the system traces the event source through multi-step calls, cross-references market data to verify impact magnitude, and delivers a complete "Event → Impact Chain → Market Reaction" analysis report. **Trigger Scenarios**: User expresses curiosity about a market anomaly, e.g., "why did BTC crash", "what just happened", "why did ETH suddenly spike". **Local maintenance (optional, repository copy only):** - If `scripts/update-skill.*` exists in the repository copy, `check` may compare the installed copy with the packaged skill source used by the current install. - Ask the user before `apply`. - `apply` updates files within this skill directory only. --- ## MCP Dependencies ### Required MCP Servers | MCP Server | Status | |------------|--------| | Gate-News | ✅ Required | | Gate-Info | ✅ Required | ### MCP Tools Used **Query Operations (Read-only)** - info_marketsnapshot_get_market_snapshot - info_onchain_get_token_onchain - news_events_get_event_detail - news_events_get_latest_events - 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, Gate-Info (for [REDACTED_SECRET] and `info_onchain_get_token_onchain` in this skill) - 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 | |-------------|----------|--------| | Reason for price move | "why pump" "why dump" "crash" "surge" "what caused" "what happened" | Execute this Skill's full workflow | | General news query | "any recent news" | Route to `gate-news-briefing` | | Comprehensive coin analysis | "analyze BTC for me" | Route to `gate-info-coinanalysis` | | Technical analysis | "BTC technical analysis" | Route to `gate-info-trendanalysis` | | Market overview | "how's the market" | Route to `gate-info-marketoverview` | --- ## 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 the reason behind a price move, proceed with this Skill. - If the query **also** mentions fundamentals, risk check, technicals, comparison, or any other analysis dimension beyond event attribution, 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`: The coin involved (e.g., BTC, ETH; may be empty = overall market) - `direction`: Up or down (aids search) - `time_hint`: Time clue ("just now", "today", "yesterday"; default: past 24h) ### Step 2: Phase 1 — Event Search + Market Verification (Parallel) | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 1a | `news_events_get_latest_events` | `coin={coin}, time_range="24h", limit=10` | Related event list | Yes | | 1b | [REDACTED_SECRET] | `symbol={coin}, timeframe="1d", source="spot"` | Real-time market snapshot (verify volatility magnitude) | Yes | > Both Tools called in parallel. ### Step 3: Decision Branch ``` events response │ ├── Matching event found (event time aligns with volatility onset) │ └── → Step 4a: Get event details │ └── No clear event match └── → Step 4b: Expand news search ``` ### Step 4a: Event Found → Get Details + On-chain Verification | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 2a | `news_events_get_event_detail` | `event_id={matched_event_id}` | Event details (cause, impact, timeline) | Yes | | 2b | `info_onchain_get_token_onchain` | `[REDACTED_SECRET], chain="eth", scope="transfers"` | On-chain anomalies (large transfers, exchange inflows/outflows) | Yes | ### Step 4b: No Event Found → Expand Search | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 2c | `news_feed_search_news` | `coin={coin}, sort_by="time", limit=15` | Latest related news (sorted by time) | Yes | | 2d | `info_onchain_get_token_onchain` | `[REDACTED_SECRET], chain="eth", scope="transfers"` | On-chain anomalies | Yes | ### Step 5: LLM Attribution Reasoning The LLM must complete the following reasoning chain: 1. **Confirm the volatility**: Based on the market snapshot, confirm the timing, magnitude, and volume change 2. **Identify the trigger event**: From events/news, find the event with the closest time alignment 3. **Verify causality**: Did the event precede the price move? Is there corresponding on-chain activity? 4. **Assess the impact chain**: Event → Direct impact → Sentiment transmission → Price reaction 5. **Evaluate follow-on potential**: Based on the event's nature, assess whether the impact is short-term or sustained ### Step 6: Output Structured Report --- ## Report Template ```markdown ## {coin} {Pump/Dump} Attribution Analysis > Analysis time: {timestamp} ### 1. Volatility Summary | Metric | Value | |--------|-------| | Current Price | ${price} | | Move Magnitude | {change}% (within {timeframe}) | | High | ${high} ({time}) | | Low | ${low} ({time}) | | Volume Change | {volume_change}% (vs 24h average) | | Futures Liquidations | ${liquidation} (if available) | ### 2. Core Triggering Event 🔴 **{event_title}** - Event Time: {event_time} - Event Type: {Regulation / Project Development / Market Manipulation / Macro Economic / Technical Failure / Whale Activity} - Details: {2-3 sentence description} - Source: {source} ### 3. Event → Impact Chain ``` {event} │ ├── Direct Impact: {description} │ e.g., SEC lawsuit → Regulatory uncertainty for the token increases │ ├── Sentiment Transmission: {description} │ e.g., Panic spreads → Fear & Greed Index drops from 65 to 35 │ └── Price Reaction: {description} e.g., {coin} dropped from ${high} to ${low} within 2 hours of the event ``` ### 4. On-chain Verification {If on-chain data is available:} | On-chain Metric | Anomaly | |----------------|---------| | Exchange Inflows | {increase/decrease}, {description} | | Large Transfers | {count} transfers exceeding ${threshold} | | Whale Activity | {description} | | Futures Funding Rate | {change description} | {Does the on-chain data corroborate the event narrative?} ### 5. Ripple Effects {Did this event affect other coins/sectors?} - {Related coin 1}: {impact description} - {Related coin 2}: {impact description} - Sector impact: {e.g., L1 sector declined across the market, DeFi sector affected} ### 6. Forward Outlook {Based on the event's nature, assess the follow-on impact:} | Dimension | Assessment | |-----------|------------| | Impact Duration | {One-time shock / Short-term (1-3 days) / Medium-term (1-2 weeks) / Long-term} | | What to Watch Next | {Items to monitor: court ruling, policy details, project response, etc.} | | Historical Precedent | {Similar past events and their outcomes, if any} | ### ⚠️ Important Notes - Market moves may be caused by multiple overlapping factors; the above analysis is based on currently available information - Long-term impact of the event remains uncertain > The above analysis is based on public information and on-chain data. It does not constitute investment advice. ``` ### Template When No Event Can Be Identified ```markdown ## {coin} Volatility Analysis > Analysis time: {timestamp} ### Volatility Summary {Same as above} ### Possible Cause Analysis ⚠️ No single clear triggering event was identified. The following is a composite analysis: **Possible Factor 1: {description}** - Evidence: {related news/data} - Likelihood: {High/Medium/Low} **Possible Factor 2: {description}** - Evidence: ... - Likelihood: ... **On-chain Clues** {Any anomalous on-chain data that could help explain the move?} ### Composite Assessment {LLM's composite analysis, with uncertainty explicitly acknowledged} > Note: No single clear triggering event was found for this move. The above analysis is an informed assessment based on available data. ``` --- ## Reasoning Logic ### Event Matching Logic | Condition | Assessment | |-----------|------------| | Event time < price move start time | ✅ Temporally plausible as a trigger | | Event time > price move start time | ❌ Unlikely to be the trigger (may be follow-up reporting) | | Event impact rating = "High" | Weight +2 | | Event involves the queried coin | Weight +3 | | Event type = "Regulation/Policy" | Typically causes larger moves | | Multiple events simultaneously | Composite analysis — likely multi-factor | ### Volatility Magnitude Assessment | Magnitude | Label | |-----------|-------| | < 3% | Normal volatility — may not require a specific event explanation | | 3% – 10% | Moderate volatility — look for recent news/events | | 10% – 20% | Large volatility — typically has a clear event driver | | > 20% | Extreme volatility — major event or black swan almost certain | ### On-chain Anomaly Assessment | Condition | Assessment | |-----------|------------| | Exchange inflows surge > 3x average | "Large token inflows to exchanges — potential selling pressure" | | Exchange outflows surge > 3x average | "Large token outflows from exchanges — possible accumulation" | | Large transfer count > 5x average | "Abnormally active large transfers" | | Futures liquidations > $100M | "Massive futures liquidation cascade — amplified price volatility" | --- ## Error Handling | Error Type | Handling | |------------|----------| | `news_events_get_latest_events` finds no matching event | Proceed to Step 4b — expand news search | | `news_events_get_event_detail` fails | Generate report based on event list summaries only | | `info_onchain_get_token_onchain` unavailable (P1 phase) | Skip on-chain verification section; note "On-chain data temporarily unavailable" | | [REDACTED_SECRET] fails | Cannot confirm volatility magnitude; degrade to showing event info only | | Both news and events return no results | Honestly inform the user "No clear cause has been identified at this time"; suggest monitoring for updates | | All Tools fail | Return error message; suggest the user try again later | --- ## Cross-Skill Routing | User Follow-up Intent | Route To | |-----------------------|----------| | "Analyze BTC for me" | `gate-info-coinanalysis` | | "Give me a technical analysis" | `gate-info-trendanalysis` | | "How's the overall market?" | `gate-info-marketoverview` | | "Recent news?" | `gate-news-briefing` | | "Any on-chain anomalies?" | `gate-info-tokenonchain` | | "Track this address" | `gate-info-addresstracker` | --- ## Safety Rules 1. **No definitive causal claims**: Use language like "likely caused by", "the most closely related event is" — avoid absolute causal assertions 2. **No follow-on predictions**: Do not output "it will continue to rise/fall" style predictions 3. **No investment advice**: Do not give buy/sell recommendations based on event analysis 4. **Acknowledge uncertainty**: When the causal link between event and move is uncertain, explicitly state it 5. **Source attribution**: Events and news must cite their sources 6. **Flag missing data**: When on-chain data or event details are unavailable, explicitly state it 7. **Avoid amplifying panic**: When describing crashes or black-swan events, maintain objective, neutral language — no sensationalist rhetoric

path: CHANGELOG.md
content: # Changelog

**Note:** Changes are consolidated as one initial entry for now; versioned entries will be used after official release.

---

## [2026.4.3-1] - 2026-04-03

### Changed

- Added `.clawhubignore` to exclude local update scripts from published ClawHub bundles.
- Clarified in `SKILL.md` that local maintenance scripts are repository-only helpers and are not required for the published skill bundle.
- No MCP workflow or business logic changes.

## [2026.4.1-2] - 2026-04-01

### Fixed

- **SKILL.md — MCP Dependencies**: **Gate-Info** added to **Required MCP Servers** and **Installation Check** alongside Gate-News. The skill already calls `info_marketsnapshot_get_market_snapshot` and `info_onchain_get_token_onchain` (Gate-Info); the document previously listed only Gate-News, which misstated install/runtime dependencies. Resolves QC daily validation item: MCP declaration must match tools in **MCP Tools Used**.

---

## [2026.4.1-1] - 2026-04-01

### Changed

- **info-news-runtime-rules.md**: Align version-check UX — do not surface technical failure details to end users; forbid auto-download of `update-skill.sh` / `update-skill.ps1` (manual copy from gate/gate-skills allowed); success paths (`update_available` / strict exit 3) still require per-skill confirmation before `apply`.
- **SKILL.md — Trigger update**: Document ClawHub packages may omit `update-skill.ps1`; agent rules for Bash vs PowerShell vs WSL/Git Bash vs silent skip; use the same shell family for Steps 1–2; do not run `apply` / `revoke-pending` when Step 1 is skipped; dual-arg `DEST` / `name` order with script auto-swap when only one path contains `SKILL.md`.
- **scripts/update-skill.sh**, **scripts/update-skill.ps1**: Strict `check` (`GATE_SKILL_CHECK_STRICT=1`, exit 3, `GATE_SKILL_CONFIRM_TOKEN`, `revoke-pending`); expanded default install-root resolution (Cursor, Codex, OpenClaw, `.agents`, Antigravity).

---

## [2026.3.25-1] - 2026-03-25

### Added

- **Runtime rules**: SKILL.md references shared `info-news-runtime-rules.md` with `gate-runtime-rules.md`; **Trigger update** (check / confirm / apply) and **Routing Rules** aligned to the gate-info / gate-news rollout.
- **Update scripts**: `scripts/update-skill.sh`, `scripts/update-skill.ps1` (same pilot implementation as sibling Info/News skills).

---

## [2026.3.12-1] - 2026-03-12

### Added

- Skill: Event attribution and explanation. Trigger: why did X pump/dump, what caused this move. Tools: news_events_get_latest_events, info_marketsnapshot_get_market_snapshot, news_events_get_event_detail, info_onchain_get_token_onchain, news_feed_search_news. Multi-step workflow with event-found vs expand-news branch.
- SKILL.md: Workflow (Phase 1 parallel, Step 4a/4b branch), Report Template (attribution + no-event template), Reasoning Logic, Error Handling, Cross-Skill, Safety. Synced from docs/pd-vs-skills/skills/gate-news-eventexplain; tool names in underscore form.
- README.md, references/scenarios.md.

### Audit

- Read-only; no trading or order execution. No definitive causal claims; no follow-on price predictions.


path: README.md
content: # gate-news-eventexplain

## Overview

An AI Agent skill that **explains why a coin pumped or dumped** by tracing triggering events, cross-referencing market data and on-chain anomalies, and delivering an event-impact-chain report. Use when the user asks why a price moved (e.g. "why did BTC crash", "what just happened"). **Phase 1**: parallel `news_events_get_latest_events` + `info_marketsnapshot_get_market_snapshot`. **Branch**: if event found → `news_events_get_event_detail` + `info_onchain_get_token_onchain`; else → `news_feed_search_news` + `info_onchain_get_token_onchain`. Read-only.

### Core Capabilities

| Capability | Description | Example |
|------------|-------------|---------|
| **Event attribution** | Match volatility to triggering event; event → impact chain → market reaction | "Why did BTC crash" / "Why did ETH pump" |
| **Multi-step workflow** | Event search + market verification → event detail or expanded news + on-chain | Per SKILL.md Execution Workflow |
| **Structured report** | Volatility Summary, Core Triggering Event, Event→Impact Chain, On-chain Verification, Ripple Effects, Forward Outlook; or "No event identified" template | Per SKILL.md Report Template |

### Routing

| User intent | Action |
|-------------|--------|
| Reason for price move | Execute this skill |
| General news | Route to `gate-news-briefing` |
| Full coin analysis | Route to `gate-info-coinanalysis` |
| Technical analysis | Route to `gate-info-trendanalysis` |
| Market overview | Route to `gate-info-marketoverview` |

### Architecture

- **Input**: User message with coin (optional) and time hint (default past 24h).
- **Tools**: Phase 1 — `news_events_get_latest_events`, [REDACTED_SECRET]. Phase 2a — `news_events_get_event_detail`, `info_onchain_get_token_onchain`. Phase 2b — `news_feed_search_news`, `info_onchain_get_token_onchain`. See SKILL.md for params.
- **Output**: Attribution report or "No clear event" composite analysis. **Reasoning Logic** (event matching, volatility magnitude, on-chain anomaly), **Error Handling**, **Safety** (no causal certainty, no predictions) — see SKILL.md.

## Source

- **Repository**: [github.com/gate/gate-skills](https://github.com/gate/gate-skills)
- **Publisher**: [Gate.com](https://www.gate.com)


path: references/mcp.md
content: ---
name: gate-news-eventexplain-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for event-causality explanation: event detail, related headlines, market snapshot and on-chain context synthesis."
---

# Gate News EventExplain MCP Specification

## 1. Scope and Trigger Boundaries

In scope:
- Explain why price/event happened
- Build causal chain from events + market + on-chain context

Out of scope:
- Generic daily briefing -> `gate-news-briefing`
- Listing tracker -> `gate-news-listing`

## 2. MCP Detection and Fallback

Detection:
1. Verify Gate-News and Gate-Info tool availability in current environment.
2. Probe one news tool and one market/info tool.

Fallback:
- If one domain unavailable, keep partial explanation and mark uncertainty explicitly.

## 3. Authentication

- API key not required.

## 4. MCP Resources

No mandatory MCP resources.

## 5. Tool Calling Specification

| Tool | Role |
|---|---|
| `news_events_get_event_detail` | primary event fact source |
| `news_events_get_latest_events` | adjacent/related events timeline |
| `news_feed_search_news` | narrative/source corroboration |
| `info_marketsnapshot_get_market_snapshot` | price/volume/volatility context |
| `info_onchain_get_token_onchain` | on-chain participation/liquidity context |

## 6. Execution SOP (Non-Skippable)

1. Normalize target event/asset/time window.
2. Pull event detail first, then parallel fetch supporting context.
3. Build causality chain: trigger -> market reaction -> on-chain reaction -> second-order effects.
4. Mark confidence per causal link (high/medium/low).

## 7. Output Templates

```markdown
## Event Explanation
- Event: {event_title}
- Time: {event_time}
- Immediate Impact: {price_volume_change}
- Causal Chain:
  1. {cause_1}
  2. {cause_2}
  3. {cause_3}
- Confidence: {confidence_level}
- Watchpoints: {followup_risks}
```

## 8. Safety and Degradation Rules

1. Distinguish confirmed facts vs inferred causality.
2. If key data source is missing, reduce confidence and disclose missing source.
3. Do not claim single-cause certainty for complex market moves.
4. Preserve source attribution when available.
5. Avoid trading recommendations; stay explanatory.


path: references/scenarios.md
content: # gate-news-eventexplain — Scenarios & Prompt Examples

## Scenario 1: Why did a coin dump (English)

**Context**: User asks why BTC or another coin crashed.

**Prompt Examples**:
- "Why did BTC crash"
- "What caused the ETH drop"
- "Why is SOL dumping"

**Expected Behavior**:
1. Extract coin (e.g. BTC), direction (down), time_hint (default 24h). Call in parallel: `news_events_get_latest_events`(coin=BTC, time_range=24h), `info_marketsnapshot_get_market_snapshot`(symbol=BTC, scope=full).
2. If a matching event is found (event time before move), call `news_events_get_event_detail` and `info_onchain_get_token_onchain` in parallel; else call `news_feed_search_news` and `info_onchain_get_token_onchain`.
3. Output **attribution report**: Volatility Summary, Core Triggering Event, Event→Impact Chain, On-chain Verification, Ripple Effects, Forward Outlook. Use "likely caused by" language; no definitive causal claims.

## Scenario 2: Why did a coin pump (Chinese)

**Context**: User asks why a coin surged.

**Prompt Examples**:
- "Why did ETH pump"
- "Why is SOL pumping"

**Expected Behavior**:
1. Extract coin, direction (up). Same two-phase workflow as Scenario 1.
2. Return structured attribution analysis; if no clear event, use "No event identified" template with possible factors and composite assessment.

## Scenario 3: No clear event found

**Context**: Events and news do not yield a single clear trigger.

**Prompt Examples**:
- "Why did PEPE move so much today"

**Expected Behavior**:
1. After Phase 1 and Step 4b, if no event aligns temporally, LLM produces **Possible Cause Analysis** with multiple factors and likelihoods, plus On-chain Clues and Composite Assessment.
2. Explicitly state "No single clear triggering event was found"; do not fabricate a cause.

## Scenario 4: General news (route away)

**Context**: User asks for recent news without asking why a move happened.

**Prompt Examples**:
- "Any recent news"
- "What happened in crypto today"

**Expected Behavior**:
1. Route to **gate-news-briefing**; do not run event-attribution workflow.
2. Do not call eventexplain tools.


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