gate-info-defianalysis

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 DeFi Ecosystem Analysis Skill. Routes to different sub-scenarios based on user intent (overview / single platform / yield / stablecoins / bridges / reserves / liquidation), each calling one or more MCP tools.

Trigger Scenarios: User asks about DeFi protocols, TVL, yield rates, stablecoins, cross-chain bridges, exchange reserves, liquidation distribution, etc.

MCP Dependencies

Required MCP Servers

MCP Tools Used

Query Operations (Read-only) — use by sub-scenario; do not call tools outside the active scenario.

• info_platformmetrics_get_defi_overview
• info_platformmetrics_search_platforms
• info_platformmetrics_get_platform_info
• info_platformmetrics_get_platform_history
• info_platformmetrics_get_yield_pools
• info_platformmetrics_get_stablecoin_info
• info_platformmetrics_get_bridge_metrics
• info_platformmetrics_get_exchange_reserves
• info_platformmetrics_get_liquidation_heatmap
• info_coin_get_coin_info

Authentication

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

Installation Check

• Required: Gate-Info
• 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

Execution Workflow

Step 0: Multi-Dimension Intent Check

• If the query is about DeFi/platform metrics, proceed with this Skill.
• If the query also involves coin fundamentals, technicals, or news beyond DeFi scope, route to gate-info-research (if available).

Step 1: Intent Recognition & Parameter Extraction

Extract from user input:

• platform_name (optional): Protocol name (e.g., Uniswap, Aave, Lido)
• symbol (optional): Token/stablecoin symbol (e.g., USDC, USDT, ETH)
• chain (optional): Blockchain filter (e.g., Ethereum, Arbitrum)
• exchange (optional): Exchange name (e.g., Binance, OKX)

Step 2: Call MCP Tools by Sub-scenario

Sub-scenario A: DeFi Overview

Sub-scenario B: Platform Detail

Sub-scenario C: Yield Pools

Sub-scenario D: Stablecoins

Sub-scenario E: Bridges

Sub-scenario F: Exchange Reserves

Sub-scenario G: Liquidation Heatmap

Step 3: LLM Aggregation

Generate sub-scenario-specific analysis. For overview, provide market context; for detail, provide competitive positioning; for yield, highlight risk/reward.

Step 4: Progressive Loading (Bridges & Stablecoins)

For Bridges and Stablecoins, use a list-first, detail-on-demand pattern:

1. First call (no bridge_name / narrow symbol): ranking list — summary without full chain breakdown.
2. Second call (user follow-up): specific bridge_name or symbol — full chain-level details.

Report Template

Template A: DeFi Overview

## DeFi Ecosystem Overview

> Generated: {timestamp}

### Market Summary

| Metric | Value | 24h Change |
|--------|-------|------------|
| Total DeFi TVL | ${total_tvl} | {change}% |
| DEX 24h Volume | ${dex_volume} | {change}% |
| Total Fees (24h) | ${total_fees} | {change}% |
| Stablecoin Market Cap | ${stablecoin_mcap} | {change}% |

### Top 10 Protocols by TVL

| Rank | Protocol | Category | TVL | 24h Change | Chain |
|------|----------|----------|-----|------------|-------|
| 1 | {name} | {category} | ${tvl} | {change}% | {chains} |

### Analysis

{LLM assessment: DeFi market trend, capital flows, notable shifts}

> Data sourced from Gate Info MCP. Does not constitute investment advice.

Template B: Platform Detail

## {platform_name} Deep Dive

> Generated: {timestamp}

### Key Metrics

| Metric | Value | Rank |
|--------|-------|------|
| TVL | ${tvl} | #{rank} |
| 24h Volume | ${volume} | — |
| 24h Fees | ${fees} | — |

### TVL Trend

{Describe trend from historical data}

### Token Info ({symbol})

| Metric | Value |
|--------|-------|
| Price | ${price} |
| Market Cap | ${market_cap} |
| FDV | ${fdv} |

### Analysis

{LLM competitive analysis}

> Data sourced from Gate Info MCP. Does not constitute investment advice.

Templates C–G (Yield / Stablecoin / Bridge / Reserve / Liquidation)

• Summary metrics at top
• Ranked table of data
• 2–3 sentence LLM analysis
• Standard disclaimer

Decision Logic

Error Handling

Cross-Skill Routing

Safety Rules

1. No yield guarantees: APY/yield data is historical and subject to change; state clearly that past rates do not guarantee future returns.
2. Smart contract risk: When showing yield pools or protocols, note that DeFi carries smart contract risk.
3. No endorsement: Listing a protocol does not constitute an endorsement; maintain neutrality.
4. Reserve disclaimers: Exchange reserve data is on-chain observable but may not reflect total assets.
5. Liquidation data: Liquidation heatmaps show estimated levels, not guaranteed triggers.
6. Data transparency: Label data source, update frequency, and known limitations.
7. Age & eligibility: Intended for users aged 18 or above with full civil capacity in their jurisdiction.
8. Data flow: The host agent processes user prompts; this skill directs read-only Gate-Info MCP tools listed above. The LLM formats answers from tool results. Aside from those MCP calls and the documented skill-update flow (GitHub URLs in General Rules and info-news-runtime-rules.md), this skill does not invoke additional third-party data services.