Loading...
Loading...
Event attribution and explanation. Use this skill whenever the user asks for the reason behind a price move. Trigger phrases include: why did X crash, what just happened, why is it pumping, what caused. MCP 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.
npx skill4agent add gate/gate-skills gate-news-eventexplainThe "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.
| 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 |
| Comprehensive coin analysis | "analyze BTC for me" | Route to |
| Technical analysis | "BTC technical analysis" | Route to |
| Market overview | "how's the market" | Route to |
coindirectiontime_hint| Step | MCP Tool | Parameters | Retrieved Data | Parallel |
|---|---|---|---|---|
| 1a | | | Related event list | Yes |
| 1b | | | Real-time market snapshot (verify volatility magnitude) | Yes |
Both Tools called in parallel.
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 | MCP Tool | Parameters | Retrieved Data | Parallel |
|---|---|---|---|---|
| 2a | | | Event details (cause, impact, timeline) | Yes |
| 2b | | | On-chain anomalies (large transfers, exchange inflows/outflows) | Yes |
| Step | MCP Tool | Parameters | Retrieved Data | Parallel |
|---|---|---|---|---|
| 2c | | | Latest related news (sorted by time) | Yes |
| 2d | | | On-chain anomalies | Yes |
## {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
### 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 broadly, 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.## {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.| 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 |
| 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 |
| 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 Type | Handling |
|---|---|
| Proceed to Step 4b — expand news search |
| Generate report based on event list summaries only |
| Skip on-chain verification section; note "On-chain data temporarily unavailable" |
| 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 |
| User Follow-up Intent | Route To |
|---|---|
| "Analyze BTC for me" | |
| "Give me a technical analysis" | |
| "How's the overall market?" | |
| "Recent news?" | |
| "Any on-chain anomalies?" | |
| "Track this address" | |