Skill: gate-exchange/gate-news-listing (version 1.0.5)

--- name: gate-news-listing version: "2026.4.6-1" updated: "2026-04-06" description: "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." required_credentials: [] required_env_vars: [] required_permissions: [] --- # gate-news-listing ## 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, routing, and graceful fallback behavior). - **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. > Listing radar Skill. The user queries exchange listing/delisting/maintenance announcements, the system first calls the exchange announcements Tool, then supplements high-interest coins with fundamentals and market data. The LLM aggregates everything into a structured exchange activity report. **Trigger Scenarios**: User mentions an exchange name + listing/delisting keywords, or asks "any new coins listed recently" or "any new projects". ## MCP Dependencies ### Required MCP Servers | MCP Server | Status | |------------|--------| | Gate-News | ✅ Required | ### MCP Tools Used **Query Operations (Read-only)** - info_coin_get_coin_info - info_coin_get_coin_rankings - info_marketsnapshot_get_market_snapshot - news_feed_get_exchange_announcements ### 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/Pattern | Action | |-------------|-----------------|--------| | Query exchange listings | "what did Binance list" "any new coins on Gate" "recent new listings" | Execute this Skill's full workflow | | Query specific coin listing info | "where is SOL listed" "when was PEPE listed on Binance" | Execute this Skill (filter by coin) | | Query delistings/maintenance | "any coins getting delisted" "exchange maintenance announcements" | Execute this Skill (filter by announcement type) | | News briefing | "what happened recently" | Route to `gate-news-briefing` | | Coin analysis | "how is this new coin doing" | Route to `gate-info-coinanalysis` | | Contract security check | "is this new coin safe" | Route to `gate-info-riskcheck` | --- ## Execution Workflow ### Step 1: Intent Recognition & Parameter Extraction Extract from user input: - `exchange` (optional): Exchange name (e.g., Binance, Gate, OKX, Bybit, Coinbase) - `coin` (optional): Specific coin symbol - `announcement_type` (optional): Announcement type (listing / delisting / maintenance) - `limit`: Number of results, default 10 **Default Logic**: - If no exchange specified, query all exchanges - If no announcement type specified, default to listing - If user mentions "delisting" or "maintenance", set the corresponding `announcement_type` ### Step 2: Call Exchange Announcements Tool | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 1 | [REDACTED_SECRET] | `exchange={exchange}, coin={coin}, announcement_type={announcement_type}, limit={limit}` | Announcement list: exchange, coin, type, time, details | — | ### Step 3: Supplement Key Coins with Data (Parallel) From Step 2 results, extract the top 3-5 newly listed coins and supplement in parallel: | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 2a | `info_coin_get_coin_info` | `query={coin_symbol}` | Project fundamentals: sector, funding, description | Yes | | 2b | [REDACTED_SECRET] | `symbol={coin_symbol}, timeframe="1d", source="spot"` | Market data: price, change, market cap, volume | Yes | > Only supplement data for listing-type announcements. Delisting/maintenance announcements do not need market data. ### Step 4: LLM Aggregation — Generate Report Pass announcement data and supplementary info to the LLM to generate the exchange activity report using the template below. --- ## Report Template ```markdown ## Exchange Activity Report > Data range: {start_time} — {end_time} | Exchange: {exchange / "All"} | Type: {type / "Listings"} ### 1. Latest Listing Announcements | # | Exchange | Coin | Type | Listing Time | Trading Pairs | |---|---------|------|------|-------------|---------------| | 1 | {exchange_1} | {coin_1} | Listed | {time_1} | {pairs_1} | | 2 | {exchange_2} | {coin_2} | Listed | {time_2} | {pairs_2} | | ... | ... | ... | ... | ... | ... | ### 2. Featured New Coins {Quick analysis of the top 3-5 newly listed coins} #### {coin_1} | Metric | Value | |--------|-------| | Project Description | {description} | | Sector | {category} | | Funding Background | {funding} | | Current Price | ${price} | | Post-Listing Change | {change}% | | 24h Volume | ${volume} | | Market Cap | ${market_cap} | {LLM one-liner: highlights and risks to watch for this project} #### {coin_2} ... ### 3. Delisting / Maintenance Notices (if any) | # | Exchange | Coin | Type | Effective Date | Notes | |---|---------|------|------|---------------|-------| | 1 | ... | ... | Delisted | ... | ... | ### 4. Activity Summary {LLM generates a 2-3 sentence summary based on all announcement data:} - Most active exchange for new listings recently - Trending listing sectors (Meme / AI / DePIN / L2, etc.) - Notable projects and why they stand out - Delisting/maintenance reminders (if any) ### ⚠️ Risk Warnings - Newly listed coins experience extreme volatility — the price discovery phase carries very high risk - Some newly listed tokens may have insufficient liquidity — watch for slippage on large trades - It is recommended to use the "Risk Assessment" feature to check contract security before trading > The above information is compiled from public announcements and on-chain data and does not constitute investment advice. ``` --- ## Decision Logic | Condition | Assessment | |-----------|------------| | New coin 24h change > +100% post-listing | Flag "Abnormal surge — chasing the pump carries extreme risk" | | New coin 24h change < -50% post-listing | Flag "Listed at a loss — buying now requires caution" | | 24h volume < $100K | Flag "Extremely low volume — severe liquidity shortage" | | Multiple exchanges list the same coin simultaneously | Flag "Multi-exchange simultaneous listing — high market attention" | | Announcement type is delisting | Flag "Upcoming delisting — please handle positions promptly" | | Announcement type is maintenance | Flag "Deposit/withdrawal maintenance in progress — transfers temporarily unavailable" | | Coin fundamentals show no funding info | Flag "No funding information found — additional due diligence required" | | Announcements return empty | Inform "No relevant announcements for this time period" | | A supplementary Tool returns empty/error | Skip detailed analysis for that coin; mark "Data unavailable" | --- ## Error Handling | Error Type | Handling | |------------|----------| | Misspelled exchange name | Attempt fuzzy match, e.g., "Binance" → Binance, "OKX" → OKX | | No matching announcements | Inform "No {type} announcements for this exchange/time period." Suggest broadening the time range or switching exchanges | | news_feed_get_exchange_announcements timeout | Return error message; suggest trying again later | | Coin supplementary info (coin_info / market_snapshot) fails | Skip detailed analysis for that coin; display announcement info only | | User asks when a coin will be listed (future) | Inform "Currently only published announcements can be queried — future listing plans cannot be predicted" | | Too many results | Default to showing the most recent 10; inform the user they can specify an exchange or time range to narrow results | --- ## Cross-Skill Routing | User Follow-up Intent | Route To | |-----------------------|----------| | "Analyze this new coin for me" | `gate-info-coinanalysis` | | "Is this new coin's contract safe?" | `gate-info-riskcheck` | | "Compare a few of these new listings" | `gate-info-coincompare` | | "Why did this coin get listed on the exchange?" | `gate-news-eventexplain` | | "How is the overall market right now?" | `gate-info-marketoverview` | | "On-chain data for this new coin" | `gate-info-tokenonchain` | --- ## Available Tools & Degradation Notes | PRD-Defined Tool | Actually Available Tool | Status | Degradation Strategy | |-----------------|----------------------|--------|---------------------| | [REDACTED_SECRET] | [REDACTED_SECRET] | ✅ Ready | — | | `info_coin_get_coin_rankings` | — | ❌ Not ready | Cannot list recent listings by ranking — extract coins from announcements and query individually instead | | `info_coin_get_coin_info` | `info_coin_get_coin_info` | ✅ Ready | — | | [REDACTED_SECRET] | [REDACTED_SECRET] | ✅ Ready | — | --- ## Safety Rules 1. **No investment advice**: Announcement analysis is based on public information and must include a "not investment advice" disclaimer 2. **No listing predictions**: Do not predict whether a coin will be listed on a specific exchange 3. **New coin risk reminder**: All reports on newly listed coins must include the "extreme volatility during initial listing" risk warning 4. **Data transparency**: Label announcement source and update time 5. **Flag missing data**: When any dimension has no data, explicitly inform the user — never fabricate data 6. **Delisting urgency**: For delisting announcements, prominently remind users to manage their positions

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

# Gate News Listing Runtime Rules

> Packaged runtime rules for `gate-news-listing`.
> 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 exchange listing, delisting, and maintenance announcements.
- If the user asks for deeper coin analysis or contract risk checks, route to the matching skill after handling the announcement scope.

## 2. Tool Scope

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

## 3. Installation and Fallback

- This skill requires Gate News and may supplement with documented Gate Info read-only tools.
- If the required announcement tool is 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-listing-info-news-runtime-rules
version: "2026.4.6-1"
updated: "2026-04-06"
description: "Packaged info/news common runtime rules for gate-news-listing."
---

# 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-listing-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for exchange listing radar: announcements retrieval, market/fundamental enrichment, and listing-focused reporting."
---

# Gate News Listing MCP Specification

## 1. Scope and Trigger Boundaries

In scope:
- Exchange listing/delisting/maintenance announcement tracking
- Enrichment with market snapshot and token fundamentals

Out of scope:
- Generic news briefing -> `gate-news-briefing`
- Event causality deep explanation -> `gate-news-eventexplain`

## 2. MCP Detection and Fallback

Detection:
1. Verify Gate-News and supporting Info tools are available.
2. Probe `news_feed_get_exchange_announcements`.

Fallback:
- If announcement tool fails, stop and report no listing feed.
- If enrichment tools fail, return announcement-only report with degraded markers.

## 3. Authentication

- API key not required.

## 4. MCP Resources

No mandatory MCP resources.

## 5. Tool Calling Specification

| Tool | Role |
|---|---|
| `news_feed_get_exchange_announcements` | primary listing/delisting source |
| `info_marketsnapshot_get_market_snapshot` | market move context for listed coins |
| `info_coin_get_coin_info` | project/fundamental enrichment |
| `info_coin_get_coin_rankings` | optional ranking context |

## 6. Execution SOP (Non-Skippable)

1. Parse exchange/time scope and announcement type filters.
2. Retrieve exchange announcements first.
3. Extract high-interest symbols and run enrichment calls.
4. Deduplicate and classify announcements (listing/delisting/maintenance).
5. Output listing-focused report with clear evidence source.

## 7. Output Templates

```markdown
## Listing Radar
- Exchange Scope: {exchange_or_all}
- Time Window: {time_range}
- New Listings: {count}
- Delistings/Maintenance: {count}

### Key Items
1. {announcement_item}
2. {announcement_item}

### Coin Enrichment
- {symbol}: {brief_fundamental_and_market_context}
```

## 8. Safety and Degradation Rules

1. Treat exchange announcement feed as source of truth for listing status.
2. Do not infer "listed" from price moves alone.
3. Clearly distinguish confirmed listing vs rumor/speculation.
4. If enrichment is missing, keep announcement facts and mark missing context.
5. Preserve announcement timestamps/exchange names exactly.


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

## Scenario 1: Recent new listings (English)

**Context**: User asks what new coins have been listed recently.

**Prompt Examples**:
- "Any new coins listed recently"
- "What did Binance list this week"
- "Recent new listings on Gate"

**Expected Behavior**:
1. Call [REDACTED_SECRET](exchange optional, announcement_type=listing, limit=10). Extract top 3-5 newly listed coins.
2. For each selected coin, call in parallel `info_coin_get_coin_info` and `info_marketsnapshot_get_market_snapshot`(timeframe=1d, source=spot).
3. Output **Exchange Activity Report**: Latest Listing Announcements table, Featured New Coins (description, sector, funding, price, post-listing change, volume, market cap + one-liner), Delisting/Maintenance if any, Activity Summary. Include risk warnings (extreme volatility, liquidity, recommend risk check).

## Scenario 2: Specific exchange (Chinese)

**Context**: User asks about a specific exchange's new listings.

**Prompt Examples**:
- "What did Binance list"
- "What did Gate list recently"

**Expected Behavior**:
1. Extract exchange (e.g. Binance, Gate). Call `news_feed_get_exchange_announcements`(exchange=Binance, announcement_type=listing).
2. Supplement top new coins with coin_info and market_snapshot; output same 4-section report. Fuzzy-match exchange name if needed.

## Scenario 3: Delisting or maintenance

**Context**: User asks about delistings or maintenance.

**Prompt Examples**:
- "Any coins getting delisted"
- "Exchange maintenance announcements"

**Expected Behavior**:
1. Set announcement_type to delisting or maintenance. Call `news_feed_get_exchange_announcements` with that type. Do not supplement with market data for non-listing types.
2. Include Delisting/Maintenance Notices in report; prominently remind users to manage positions for delistings.

## Scenario 4: No announcements / tool failure

**Context**: No results or supplementary tool fails for a coin.

**Prompt Examples**:
- "New listings on XYZ exchange" (no data)

**Expected Behavior**:
1. If announcements return empty: inform "No relevant announcements for this time period" and suggest broadening time or exchange.
2. If coin_info or market_snapshot fails for a coin: skip detailed analysis for that coin; mark "Data unavailable"; still show announcement row.


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