Skill: gaixianggeng/gate-info-liveroomlocation-staging (version 1.0.0)

--- name: gate-info-liveroomlocation version: "2026.4.8-1" updated: "2026-04-08" description: "Gate live stream and replay listing skill. Use when the user asks to find live rooms or replays by tag, coin, or sort. Triggers on 'live room list', '最热直播', 'replay list', 'SOL live stream'." required_credentials: [] required_env_vars: [] required_permissions: [] --- # Gate Info Liveroom Location — Live & Replay 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, 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. --- ## MCP Dependencies ### Required MCP Servers | MCP Server | Status | |------------|--------| | Gate-Info | ✅ Required | ### 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. ## MCP Mode **Read and strictly follow** [`references/mcp.md`](./references/mcp.md), then execute this skill's live/replay listing workflow. - `SKILL.md` keeps intent mapping, product behavior, and response semantics. - `references/mcp.md` is the authoritative MCP execution layer for parameter extraction, single-endpoint calls, and degradation handling. ## Workflow When the user asks about live rooms or replays (by business type, coin, hottest/newest, or count), execute the following steps. ### Step 1: Parse intent and map parameters From natural language, extract and map to API parameters: - **tag**: Market Analysis | Hot Topics | Blockchain | Others | empty (all). Default: empty. - **coin**: Coin symbol (e.g. BTC, SOL) or empty (all). Default: empty. - **sort**: `hot` (hottest) | `new` (newest). Default: `hot`. - **limit**: Integer 1–10. Default: 10. Key mapping rules: | User phrase (examples) | Param | Value | |------------------------|--------|--------| | 行情分析, 市场分析, Market Analysis | tag | Market Analysis | | 热门话题, Hot Topics | tag | Hot Topics | | 区块链, Blockchain | tag | Blockchain | | 其他, Others | tag | Others | | Not mentioned | tag | empty | | Bitcoin, BTC, SOL, ETH, 比特币 | coin | BTC, SOL, etc. | | Not mentioned | coin | empty | | 最热, 热门, 按热度, hottest | sort | hot | | 最新, 最近, newest | sort | new | | Not mentioned | sort | hot | | 前5条, 给我3个, 10个 | limit | 5, 3, 10 | | Not mentioned | limit | 10 | **Do not** ask the user "how many?" or "which coin?" when they did not specify; apply defaults. ### Step 2: Call the API Call `GET /live/gate_ai/tag_coin_live_replay` with query parameters: - `tag`: string (optional) - `coin`: string (optional) - `sort`: `hot` | `new` (optional, default hot) - `limit`: integer (optional, default 10, max 10) Key data to extract from response: - `data.list`: array of items, each with `content_type` (`"streaming"` or `"video"`), and either `live` (with `id`, `name`) or `video` (with `id`, `title`). **Pre-filter**: If the user is in a restricted region (US, Canada, Japan, or other Gate-restricted regions), do **not** call the API; reply that the feature is not available in their region. ### Step 3: Build list output For each item in `data.list`: - **Title**: `live.name` when `content_type === "streaming"`, else `video.title` when `content_type === "video"`. - **Link**: - `content_type === "streaming"`: `https://www.gate.io/live/video/{live.id}?type=live` - `content_type === "video"`: `https://www.gate.io/live/video/{video.id}` Output a list of lines: each line = **title** + **link**. Optionally label "Live" or "Replay". Do not add extra fields (e.g. likes, duration) unless required by product. ## Judgment Logic Summary | Condition | Signal | Meaning | |-----------|--------|---------| | User in restricted region | Block | Do not call API; reply that the feature is not available in their region | | tag / coin / sort / limit not mentioned | Use default | tag=empty, coin=empty, sort=hot, limit=10 | | content_type === "streaming" | Live | Use live.name; link with `?type=live` | | content_type === "video" | Replay | Use video.title; link without type | | Empty list or API error | No list | Reply with a short message; do not fabricate a list | ## Report Template - **List format**: One line per item: `[Live/Replay] Title — <link>`. - **Disclaimer** (if needed): Gate live and replay content is provided by creators; it does not constitute investment or viewing advice; the platform only provides display and filtering. ## Single API only Use only `GET /live/gate_ai/tag_coin_live_replay`. Do not combine or mention other live or video APIs.

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

# Gate Info Liveroom Location Runtime Rules

> Packaged runtime rules for `gate-info-liveroomlocation`.
> 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 live-stream and replay listing requests.
- If the user asks for analysis, trading, or other non-listing workflows, route to the matching skill instead of stretching this one.

## 2. Tool Scope

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

## 3. Installation and Fallback

- This skill requires the Gate Info MCP server.
- If the required MCP tools are 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-info-liveroomlocation-info-news-runtime-rules
version: "2026.4.8-1"
updated: "2026-04-08"
description: "Packaged info/news common runtime rules for gate-info-liveroomlocation."
---

# 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 data returned by the documented MCP tools.


path: references/mcp.md
content: ---
name: gate-info-liveroomlocation-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for Gate live/replay listing by tag, coin, sort, and count."
---

# Gate Live Room Location MCP Specification

## 1. Scope and Trigger Boundaries

In scope:
- Live/replay list retrieval with tag/coin/sort/limit filters
- Standardized list output with clickable links

Out of scope:
- Trading advice, order execution, or unrelated content discovery

Misroute examples:
- If user asks for market analysis itself, route to analysis skills rather than stream listing.

## 2. MCP Detection and Fallback

Detection:
1. Verify live/replay endpoint availability.
2. Validate filter parameters before request.

Fallback:
- If endpoint fails or returns empty list, return no-result guidance and avoid fabricated entries.

## 3. Authentication

- No API key required in standard public runtime.
- If runtime policy restricts access, return login/availability guidance.

## 4. MCP Resources

No mandatory MCP resources.

## 5. Tool Calling Specification

Single endpoint policy:
- `GET /live/gate_ai/tag_coin_live_replay`

Parameter rules:
- `tag`: optional, default empty
- `coin`: optional, default empty
- `sort`: `hot` or `new`, default `hot`
- `limit`: 1-10, default 10

## 6. Execution SOP (Non-Skippable)

1. Parse intent and map filters.
2. Apply default values for missing filters.
3. Perform single-endpoint query.
4. Map each item by `content_type` to title + URL.
5. Return ordered list and no-result message when needed.

## 7. Output Templates

```markdown
## Live/Replay List
- [Live] {title} - {url}
- [Replay] {title} - {url}
```

## 8. Safety and Degradation Rules

1. Never fabricate live/replay entries.
2. Respect restricted-region block policy when applicable.
3. Keep scope to listing only; no investment claims.
4. Preserve `live` vs `video` link format rules.


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