Skill: gate-exchange/gate-info-trend-analysis (version 1.0.3)

--- name: gate-info-trendanalysis version: "2026.4.3-1" updated: "2026-04-03" description: "Trend and technical analysis. Use this skill ONLY when the user's query is exclusively about technical indicators or trend analysis for one coin with no other analysis dimensions. Trigger phrases: technical analysis, K-line, RSI, MACD, trend, support, resistance. If the query ALSO mentions fundamentals, risk, news, sentiment, or any other analysis dimension, use gate-info-research instead — it handles multi-dimension queries in a single unified report." required_credentials: [] required_env_vars: [] required_permissions: [] --- # gate-info-trendanalysis ## 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 `../gate-runtime-rules.md` → Also read `../info-news-runtime-rules.md` for gate-info / gate-news shared rules (tool degradation, report standards, security, routing, and optional local maintenance when `scripts/` is present). - **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. > A technicals-focused Skill. The user inputs a coin name + technical analysis intent; the system calls 4 Tools (K-line data, indicator history, multi-timeframe signals, real-time market snapshot) in parallel, then the LLM aggregates into a multi-dimensional technical analysis report. **Trigger Scenarios**: User explicitly mentions technical analysis, K-line, indicators, trend, support/resistance, or similar keywords. **Local maintenance (optional, repository copy only):** - If `scripts/update-skill.*` exists in the repository copy, `check` may compare the installed copy with the packaged skill source used by the current install. - Ask the user before `apply`. - `apply` updates files within this skill directory only. --- ## MCP Dependencies ### Required MCP Servers | MCP Server | Status | |------------|--------| | Gate-Info | ✅ Required | ### MCP Tools Used **Query Operations (Read-only)** - info_marketsnapshot_get_market_snapshot - info_markettrend_get_indicator_history - info_markettrend_get_kline - info_markettrend_get_technical_analysis ### 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 | User Intent | Keywords | Action | |-------------|----------|--------| | Technical analysis | "technical analysis" "K-line" "RSI" "MACD" "Bollinger" "moving average" "support" "resistance" "trend" | Execute this Skill's full workflow | | Comprehensive analysis (incl. fundamentals) | "analyze BTC for me" | Route to `gate-info-coinanalysis` | | Price only | "what's BTC price" | Call [REDACTED_SECRET] directly | | Raw K-line data only | "BTC 30-day K-line" | Call `info_markettrend_get_kline` directly — no need for full Skill | --- ## Execution Workflow ### Step 0: Multi-Dimension Intent Check Before executing this Skill, check if the user's query involves multiple analysis dimensions: - If the query is exclusively about technical indicators or trend analysis for one coin, proceed with this Skill. - If the query **also** mentions fundamentals, risk, news, sentiment, or any other analysis dimension beyond technicals, route to `gate-info-research` — it handles multi-dimension queries with unified tool deduplication and coherent report aggregation. ### Step 1: Intent Recognition & Parameter Extraction Extract from user input: - `symbol`: Coin ticker (BTC, ETH, SOL, etc.) - `timeframe`: Analysis timeframe (e.g., "daily" → 1d, "4-hour" → 4h; default: 1d) - `indicators`: Specific indicators the user cares about (e.g., "RSI", "MACD"; default: all) - `period`: K-line lookback days (default: 90) ### Step 2: Call 4 MCP Tools in Parallel | Step | MCP Tool | Parameters | Retrieved Data | Parallel | |------|----------|------------|----------------|----------| | 1a | `info_markettrend_get_kline` | `symbol={symbol}, timeframe={timeframe}, limit=90` | K-line OHLCV data (default 90 bars) | Yes | | 1b | [REDACTED_SECRET] | `symbol={symbol}, indicators=["rsi","macd","bollinger","ma"], timeframe={timeframe}` | Technical indicator history | Yes | | 1c | [REDACTED_SECRET] | `symbol={symbol}` | Multi-timeframe composite signals (1h/4h/1d/1w) | Yes | | 1d | [REDACTED_SECRET] | `symbol={symbol}, timeframe="1d", source="spot"` | Real-time market snapshot (price, volume, OI, funding rate) | Yes | > All 4 Tools are called in parallel. ### Step 3: LLM Analysis The LLM performs technical analysis on the raw data, completing the following reasoning: 1. Identify trend from candlestick patterns (uptrend / downtrend / sideways channel) 2. Combine indicator history to assess current position (overbought / oversold / neutral) 3. Evaluate multi-timeframe signal alignment or divergence 4. Identify key support and resistance levels ### Step 4: Output Structured Report --- ## Report Template ```markdown ## {symbol} Technical Analysis Report > Analysis time: {timestamp} | Primary timeframe: {timeframe} ### 1. Current Market Snapshot | Metric | Value | |--------|-------| | Price | ${price} | | 24h Change | {change_24h}% | | 24h Volume | ${volume_24h} | | 24h High | ${high_24h} | | 24h Low | ${low_24h} | | Open Interest | ${oi} (if available) | | Funding Rate | {funding_rate}% (if available) | ### 2. Trend Assessment **Overall Trend**: {Uptrend / Downtrend / Sideways / Trend Reversal} {Trend analysis based on candlestick patterns and MA alignment:} - MA7 / MA25 / MA99 alignment: {Bullish / Bearish / Tangled} - Recent candlestick patterns: {Bullish Engulfing / Doji / Hammer / etc.} (if notable) - Volume confirmation: {Rising volume + price up (healthy) / Declining volume + price up (weak momentum) / Rising volume + price down (accelerated selling)} ### 3. Technical Indicator Details #### RSI (14) | Timeframe | Value | Status | |-----------|-------|--------| | 1h | {rsi_1h} | {Overbought/Oversold/Neutral} | | 4h | {rsi_4h} | {Overbought/Oversold/Neutral} | | 1d | {rsi_1d} | {Overbought/Oversold/Neutral} | {RSI divergence analysis: any bullish/bearish divergence present?} #### MACD | Timeframe | DIF | DEA | Histogram | Status | |-----------|-----|-----|-----------|--------| | 1h | {dif} | {dea} | {histogram} | {Golden Cross/Death Cross/Above Zero/Below Zero} | | 4h | ... | ... | ... | ... | | 1d | ... | ... | ... | ... | #### Bollinger Bands (20, 2) | Metric | Value | |--------|-------| | Upper Band | ${upper} | | Middle Band | ${middle} | | Lower Band | ${lower} | | Bandwidth | {bandwidth}% | | Current Position | {price relative to bands + percentile} | {Narrowing bands → breakout imminent; price touching upper band → potential pullback to middle; touching lower band → potential bounce} ### 4. Key Price Levels | Type | Price | Basis | |------|-------|-------| | Strong Resistance | ${resistance_1} | {Previous high / MA99 / Upper Bollinger / Round number} | | Weak Resistance | ${resistance_2} | ... | | Weak Support | ${support_1} | ... | | Strong Support | ${support_2} | {Previous low / MA99 / Lower Bollinger / Volume profile cluster} | ### 5. Multi-Timeframe Signal Summary | Timeframe | Composite Signal | Bullish Indicators | Bearish Indicators | |-----------|-----------------|--------------------|--------------------| | 1h | {Strong Buy/Buy/Neutral/Sell/Strong Sell} | {count} | {count} | | 4h | ... | ... | ... | | 1d | ... | ... | ... | | 1w | ... | ... | ... | **Signal Consistency**: {Are multi-timeframe signals aligned? e.g., "Short-term bearish but medium/long-term bullish — divergence present"} ### 6. Overall Technical Assessment {LLM generates a comprehensive assessment:} - Current trend strength evaluation - Short-term (1-3 day) likely direction - Medium-term (1-2 week) likely direction - Key observation: a break above ${resistance_1} opens upside; a break below ${support_2} signals trend weakening ### Risk Warnings {Data-driven risk alerts} > Technical analysis is based on historical data and cannot predict future price movements. This does not constitute investment advice. ``` --- ## Decision Logic | Condition | Assessment | |-----------|------------| | RSI > 70 (multi-timeframe consistent) | "Multi-timeframe RSI overbought — high pullback probability" | | RSI < 30 (multi-timeframe consistent) | "Multi-timeframe RSI oversold — high bounce probability" | | MACD daily golden cross + 4h golden cross | "MACD multi-timeframe golden cross confirmed — bullish signal" | | MACD daily death cross + 4h death cross | "MACD multi-timeframe death cross confirmed — bearish signal" | | Bollinger bandwidth < 5% | "Extreme Bollinger squeeze — breakout imminent" | | Price breaks above upper Bollinger | "Short-term overextended — potential pullback to middle band" | | MA7 > MA25 > MA99 | "Bullish MA alignment" | | MA7 < MA25 < MA99 | "Bearish MA alignment" | | 3 consecutive days of rising volume + price up | "Rising volume rally — healthy trend" | | Declining volume + price up | "Low-volume rally — watch for weakening momentum" | | Short-term vs medium/long-term signals diverge | Flag "Bull/bear divergence — awaiting directional resolution" | | funding_rate > 0.1% | "Extreme long crowding in futures — risk of long squeeze" | | Any Tool returns empty/error | Skip that indicator analysis; note "Data unavailable" | --- ## Error Handling | Error Type | Handling | |------------|----------| | Coin does not exist | Prompt user to verify the coin name | | info_markettrend_get_kline insufficient data | Reduce lookback period or switch to larger timeframe; note limited data | | info_markettrend_get_technical_analysis fails | Derive signals from K-line and indicator history manually; label "Composite signal manually derived" | | info_markettrend_get_indicator_history partial indicators missing | Display available indicators; note missing ones as "temporarily unavailable" | | All Tools fail | Return error message; suggest the user try again later | --- ## Cross-Skill Routing | User Follow-up Intent | Route To | |-----------------------|----------| | "What about fundamentals?" / "Full analysis" | `gate-info-coinanalysis` | | "Why is it pumping/dumping?" | `gate-news-eventexplain` | | "On-chain chip analysis" | `gate-info-tokenonchain` | | "Compare XX and YY" | `gate-info-coincompare` | | "Recent news?" | `gate-news-briefing` | --- ## Safety Rules 1. **No trading advice**: Do not output "recommend going long/short" or "buy at XX" 2. **No specific price predictions**: Do not output "will rise to XX tomorrow" or "target price XX" 3. **Acknowledge limitations**: Clearly state that technical analysis is based on historical data and may fail 4. **Data transparency**: Label K-line data range and indicator parameter settings 5. **Flag missing data**: When indicators are unavailable, explicitly state it — never fabricate values

path: CHANGELOG.md
content: # Changelog

**Note:** Changes are consolidated as one initial entry for now; versioned entries will be used after official release.

---

## [2026.4.3-1] - 2026-04-03

### Changed

- Added `.clawhubignore` so repository-only maintenance scripts are excluded from published skill bundles.
- Clarified in `SKILL.md` that local maintenance steps apply only to the repository copy.
- No MCP workflow or business logic changes.

---

## [2026.4.1-1] - 2026-04-01

### Changed

- **info-news-runtime-rules.md**: Align version-check UX — do not surface technical failure details to end users; forbid auto-download of `update-skill.sh` / `update-skill.ps1` (manual copy from gate/gate-skills allowed); success paths (`update_available` / strict exit 3) still require per-skill confirmation before `apply`.
- **SKILL.md — Trigger update**: Document ClawHub packages may omit `update-skill.ps1`; agent rules for Bash vs PowerShell vs WSL/Git Bash vs silent skip; use the same shell family for Steps 1–2; do not run `apply` / `revoke-pending` when Step 1 is skipped; dual-arg `DEST` / `name` order with script auto-swap when only one path contains `SKILL.md`.
- **scripts/update-skill.sh**, **scripts/update-skill.ps1**: Strict `check` (`GATE_SKILL_CHECK_STRICT=1`, exit 3, `GATE_SKILL_CONFIRM_TOKEN`, `revoke-pending`); expanded default install-root resolution (Cursor, Codex, OpenClaw, `.agents`, Antigravity).

---

## [2026.3.25-1] - 2026-03-25

### Added

- **Runtime rules**: SKILL.md references shared `info-news-runtime-rules.md` with `gate-runtime-rules.md`; **Trigger update** (check / confirm / apply) and **Routing Rules** aligned to the gate-info / gate-news rollout.
- **Update scripts**: `scripts/update-skill.sh`, `scripts/update-skill.ps1` (same pilot implementation as sibling Info/News skills).

---

## [2026.3.12-1] - 2026-03-12

### Added

- Skill: Trend / technical analysis. Trigger: technical/trend analysis (e.g. "Technical analysis for BTC"). Tools: info_markettrend_get_kline, info_markettrend_get_indicator_history, info_markettrend_get_technical_analysis, info_marketsnapshot_get_market_snapshot. Tool count: 4.
- SKILL.md: Routing, 4-tool parallel table, parameter extraction, Judgment Logic (Bollinger/volume/divergence/funding), 7-section Report Template, Error Handling, Cross-Skill, Safety. Aligned with docs/pd-vs-skills, docs/PD_VS_SKILLS_OPTIMIZATION_SUMMARY.md.
- README.md, references/scenarios.md.

### Audit

- Read-only; no trading or order execution.


path: README.md
content: # gate-info-trendanalysis

## Overview

An AI Agent skill that performs **single-coin trend and technical analysis** (kline, multi-timeframe signals, RSI/MACD/MA, support/resistance) on Gate. Use when the user asks for technical or trend analysis of one coin. **4 tools are called in parallel** (no optional): `info_markettrend_get_kline`, `info_markettrend_get_indicator_history`, `info_markettrend_get_technical_analysis`, `info_marketsnapshot_get_market_snapshot`. Read-only.

### Core Capabilities

| Capability | Description | Example |
|------------|-------------|---------|
| **Technical analysis** | Multi-timeframe signals, bullish/bearish/neutral, support/resistance | "Do a BTC technical analysis" / "ETH technicals" |
| **Trend analysis** | Kline, indicator history (RSI, MACD, Bollinger, MA) | "Do a SOL trend analysis" |
| **7-section report** | Current snapshot, trend assessment, indicator details, key levels, multi-timeframe summary, overall assessment, risk warnings; "No data" when tool unavailable | Per SKILL.md Report Template |

### Routing

| User intent | Action |
|-------------|--------|
| Technical / trend analysis | Execute this skill |
| Comprehensive (incl. fundamentals) | Route to `gate-info-coinanalysis` |
| Price only | Call `info_marketsnapshot_get_market_snapshot` directly |
| Raw K-line only | Call `info_markettrend_get_kline` directly |

### Architecture

- **Input**: User message with one coin symbol and technical/trend intent. **Parameter extraction**: symbol, timeframe (default 1d/4h), indicators (default all), period (kline default 90).
- **Tools**: See SKILL.md — `info_markettrend_get_kline`, [REDACTED_SECRET], [REDACTED_SECRET], [REDACTED_SECRET]. All 4 in parallel.
- **Output**: 7-section report. **Judgment Logic** (RSI/MACD/MA/Bollinger/volume/divergence/funding), **Error Handling**, **Cross-Skill**, **Safety** — see SKILL.md.

## Source

- **Repository**: [github.com/gate/gate-skills](https://github.com/gate/gate-skills)
- **Publisher**: [Gate.com](https://www.gate.com)


path: references/mcp.md
content: ---
name: gate-info-trendanalysis-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for trend analysis: kline, indicator history, technical snapshots, and multi-timeframe synthesis."
---

# Gate Info TrendAnalysis MCP Specification

## 1. Scope and Trigger Boundaries

In scope:
- Technical trend analysis for a target coin/pair
- Multi-timeframe signal interpretation
- Indicator/Kline driven summaries

Out of scope:
- Full fundamental/news comprehensive reports
- Multi-coin comparative analysis

## 2. MCP Detection and Fallback

Detection:
1. Verify Gate-Info trend tools are available.
2. Probe with technical analysis or kline endpoint.

Fallback:
- If indicator history unavailable, use kline + technical snapshot only.

## 3. Authentication

- API key not required.

## 4. MCP Resources

No mandatory MCP resources.

## 5. Tool Calling Specification

| Tool | Role |
|---|---|
| `info_marketsnapshot_get_market_snapshot` | current price/market context |
| `info_markettrend_get_kline` | OHLCV series by timeframe |
| `info_markettrend_get_indicator_history` | historical indicator series |
| `info_markettrend_get_technical_analysis` | consolidated technical signal summary |

## 6. Execution SOP (Non-Skippable)

1. Resolve symbol and requested timeframe(s).
2. Pull current snapshot + kline + technical signals.
3. Pull indicator history when requested/available.
4. Build trend narrative with explicit timeframe tags.

## 7. Output Templates

```markdown
## Trend Analysis ({symbol})
- Current Snapshot: {price_context}
- Short-term Trend: {short_tf_signal}
- Mid-term Trend: {mid_tf_signal}
- Key Indicators: {rsi_macd_ma_summary}
- Critical Levels: {support_resistance}
- Signal Confidence: {confidence_note}
```

## 8. Safety and Degradation Rules

1. Always label the timeframe of each conclusion.
2. Avoid overconfidence when timeframe signals conflict.
3. If indicator data is missing, disclose and downgrade confidence.
4. Separate indicator facts from interpretation.
5. No direct trade execution recommendations in this skill.


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

## Scenario 1: Technical analysis (English)

**Context**: User wants technical analysis for BTC.

**Prompt Examples**:
- "Do a BTC technical analysis"
- "How is ETH technically?"
- "Do a SOL trend analysis"

**Expected Behavior**:
1. Extract symbol; call **4 tools in parallel** (no optional): [REDACTED_SECRET], [REDACTED_SECRET], `info_markettrend_get_kline` (e.g. limit=90), [REDACTED_SECRET] (rsi, macd, bollinger, ma). Use default timeframe 1d (or 4h) and source spot.
2. Output **7-section report**: Current Market Snapshot, Trend Assessment, Technical Indicator Details, Key Price Levels, Multi-Timeframe Signal Summary, Overall Technical Assessment, Risk Warnings. If a tool returns empty, show "No data" for that part.

## Scenario 2: Technical / trend (Chinese)

**Context**: User asks about technicals or trend in Chinese.

**Prompt Examples**:
- "How is ETH technically"
- "Do a trend analysis for SOL"

**Expected Behavior**:
1. Extract symbol; same 4-tool parallel chain as Scenario 1.
2. Return 7-section technical/trend summary; read-only.

## Scenario 3: Default timeframe

**Context**: User does not specify timeframe.

**Prompt Examples**:
- "Technical analysis for BTC"

**Expected Behavior**:
1. Use default **timeframe 1d** (or 4h), **period 90** for kline, source `spot`.
2. Fetch snapshot, technical_analysis, kline, indicator_history; output 7-section report. Any tool empty → "No data".


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