skills/gate-info-defianalysis/SKILL.md
DeFi ecosystem analysis via Gate-Info MCP. Use this skill whenever the user wants TVL rankings, protocol metrics, yield/APY, stablecoins, bridges, exchange reserves, or liquidation heatmaps. Trigger phrases include Uniswap TVL, DeFi ranking, USDC yield, bridge volume, exchange BTC reserves, liquidation density. Route coin-only fundamentals to gate-info-coinanalysis. Sub-scenario tools: info_platformmetrics_* family and info_coin_get_coin_info (exact tool names per scenario in SKILL.md).
npx skillsauth add gate/gate-skills gate-info-defianalysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
⚠️ 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-specific rules (tool degradation, report standards, security, routing degradation, and per-skill version checks when scripts/ is present).
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.
Per-skill updates: This skill may include scripts/update-skill.sh and, in full source trees, scripts/update-skill.ps1 for optional maintenance checks against the official Gate Skills repository. The shared policy is defined in info-news-runtime-rules.md.
Maintenance flow:
check only when you need to compare the installed skill with the official repo.check never rewrites files.update_available, ask the user before apply.apply rewrites only this skill's local directory under the active skills root.| MCP Server | Status | |------------|--------| | Gate-Info | ✅ Required |
Query Operations (Read-only) — use by sub-scenario; do not call tools outside the active scenario.
gate-mcp-cursor-installergate-mcp-codex-installergate-mcp-claude-installergate-mcp-openclaw-installer| User Intent | Keywords | Action |
|-------------|----------|--------|
| DeFi overview / TVL ranking | "DeFi overview" "TVL ranking" "top DeFi protocols" | Execute Sub-scenario A: Overview |
| Single platform deep-dive | "Uniswap TVL" "Aave metrics" "Compound info" | Execute Sub-scenario B: Platform Detail |
| Yield / APY query | "best yield" "USDC APY" "lending rates" "where to earn" | Execute Sub-scenario C: Yield Pools |
| Stablecoin analysis | "USDT market cap" "stablecoin ranking" "USDC circulation" | Execute Sub-scenario D: Stablecoins |
| Cross-chain bridge | "bridge volume" "top bridges" "cross-chain TVL" | Execute Sub-scenario E: Bridges |
| Exchange reserves | "Binance BTC reserves" "exchange reserves" "proof of reserves" | Execute Sub-scenario F: Exchange Reserves |
| Liquidation analysis | "BTC liquidation heatmap" "where are liquidations" "liquidation density" | Execute Sub-scenario G: Liquidation Heatmap |
| Coin fundamentals (no DeFi focus) | "analyze SOL" "how is BTC" | Route to gate-info-coinanalysis |
| Market overview | "how's the market" | Route to gate-info-marketoverview |
gate-info-research (if available).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 | MCP Tool | Parameters | Retrieved Data | Parallel |
|------|----------|------------|----------------|----------|
| 1a | info_platformmetrics_get_defi_overview | category="all" | Total TVL, volume, fees across DeFi/CEX/DEX | Yes |
| 1b | info_platformmetrics_search_platforms | sort_by="tvl", limit=10 | Top 10 platforms by TVL | Yes |
| Step | MCP Tool | Parameters | Retrieved Data | Parallel |
|------|----------|------------|----------------|----------|
| 1a | info_platformmetrics_get_platform_info | platform_name={name}, scope="full" | Full platform metrics (TVL, volume, fees, chains) | Yes |
| 1b | info_platformmetrics_get_platform_history | platform_name={name}, metrics=["tvl","volume"] | Historical trend | Yes |
| 1c | info_coin_get_coin_info | query={token_symbol} | Platform's native token info | Yes |
| Step | MCP Tool | Parameters | Retrieved Data |
|------|----------|------------|----------------|
| 1 | info_platformmetrics_get_yield_pools | project={name}, chain={chain}, symbol={symbol}, sort_by="apy", limit=20 | Yield pool rankings with APY, TVL |
| Step | MCP Tool | Parameters | Retrieved Data |
|------|----------|------------|----------------|
| 1 | info_platformmetrics_get_stablecoin_info | symbol={symbol}, chain={chain}, limit=10 | Stablecoin ranking or single coin detail with chain distribution |
| Step | MCP Tool | Parameters | Retrieved Data |
|------|----------|------------|----------------|
| 1 | info_platformmetrics_get_bridge_metrics | bridge_name={name}, chain={chain} | Bridge ranking or single bridge chain breakdown |
| Step | MCP Tool | Parameters | Retrieved Data |
|------|----------|------------|----------------|
| 1 | info_platformmetrics_get_exchange_reserves | exchange={exchange}, asset={asset} | Exchange on-chain reserves (BTC, ETH, etc.) |
| Step | MCP Tool | Parameters | Retrieved Data |
|------|----------|------------|----------------|
| 1 | info_platformmetrics_get_liquidation_heatmap | symbol={symbol}, exchange={exchange} | Liquidation density by price range |
Generate sub-scenario-specific analysis. For overview, provide market context; for detail, provide competitive positioning; for yield, highlight risk/reward.
For Bridges and Stablecoins, use a list-first, detail-on-demand pattern:
bridge_name / narrow symbol): ranking list — summary without full chain breakdown.bridge_name or symbol — full chain-level details.## 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.
## {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.
| Condition | Assessment / next step | |-----------|-------------------------| | Generic DeFi market, TVL leaderboard, or “top protocols” | Sub-scenario A (Overview) | | User names a specific protocol (Uniswap, Aave, ...) | Sub-scenario B (Platform detail) | | Yield, APY, lending, “where to earn” | Sub-scenario C (Yield pools) | | Stablecoins, peg, circulation, ranking | Sub-scenario D; use progressive loading per Step 4 | | Bridges, cross-chain TVL, bridge volume | Sub-scenario E; list-first, detail on follow-up | | Exchange reserves, PoR, “exchange BTC holdings” | Sub-scenario F | | Liquidations, heatmap, density by price | Sub-scenario G | | Ambiguous intent | Ask one clarifying question or default to A |
| Error Type | Handling |
|------------|----------|
| Platform name not found | Suggest similar platform names; ask user to verify |
| Single Tool fails | Skip that section; note "Data temporarily unavailable" |
| All Tools fail | Return error; suggest user try again later |
| No yield pools match criteria | Broaden search (remove chain/symbol filter); inform user |
| Exchange not supported | List supported exchanges; ask user to choose another |
| Symbol not recognized | Try matching via info_coin_get_coin_info; ask user if unclear |
| User Follow-up Intent | Route To |
|-----------------------|----------|
| "Analyze the token" | gate-info-coinanalysis |
| "Technical analysis of the token" | gate-info-trendanalysis |
| "Is this protocol safe?" | gate-info-riskcheck |
| "On-chain data for the token" | gate-info-tokenonchain |
| "Any news about this protocol?" | gate-news-briefing |
| "How does macro affect DeFi?" | gate-info-macroimpact |
| "How's the market overall?" | gate-info-marketoverview |
info-news-runtime-rules.md), this skill does not invoke additional third-party data services.tools
Exchange listing tracker. Use this skill whenever the user asks about exchange listing, delisting, or maintenance announcements. Trigger phrases include: any new coins listed recently, what did Binance list, new listings, delisted. MCP tools: news_feed_get_exchange_announcements, info_coin_get_coin_info, info_marketsnapshot_get_market_snapshot.
testing
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.
tools
Community sentiment via Gate-News MCP, X/Twitter-first. Use for social discussion, KOL takes, or opinion on a coin or topic. Triggers: what does the community think about ETH, Twitter or X sentiment, what are people saying, KOL opinions. Reddit, Discord, Telegram when search_ugc is available; until then label output as X/Twitter-only. Tools: news_feed_search_x, news_feed_get_social_sentiment.
testing
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.