gate-news-intel

Name: gate-news-intel
Author: gate

33stars18forks

How to install gate-news-intel?

gate/gate-skills/gate-news-intel

$npx -y skills add gate/gate-skills --skill gate-news-intel

Installs into the current project.

Summary

Use this skill whenever the user’s main ask is news, events, listings, social/UGC, or market move attribution. Primary gate-cli news (optional info for market context). Covers briefings, event explain, market move attribution via explain-market-move, exchange announcements, UGC X

Files · 1

View on GitHub

SKILL.md

1	# gate-news-intel
2
3	## General Rules
4
5	⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
6	Do NOT select or call any tool until all rules are read. These rules have the highest priority.
7	→ Read [gate-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/gate-runtime-rules.md)
8	→ Also read [info-news-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/info-news-runtime-rules.md) for gate-info and gate-news shared rules.
9	- Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they
10	exist in the MCP server.
11
12	## CLI and playbook contract
13
14	1. Primary boundary: news, events, announcements, and social/UGC intelligence. Optional `info` calls appear only in playbooks that explicitly add market or coin background (`intel_plus_market`, `market_wide_intel`).
15	2. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (`>= 0.7.6`), prefer playbook `shortcut` / `info_shortcut` blocks; fall back to legacy `commands` on failure or older CLI. When preflight `route` is `CLI`, do not use Gate MCP from this skill.
16	3. Always pass `--format json` on data-collection commands.
17	4. Separate fact from opinion: label facts (dated events, official announcements, news wires) vs community / UGC / X / social (always cite source type: UGC, X, Reddit, YouTube, sentiment index).
18	5. Synthesis order (PRD 5.6.7):
19	- “Why did it drop / crash?” → causal event chain first (Section 2), then optionally market/coin background (Section 4).
20	- “How does the community see ...?” → Section 3 (community / UGC / X / sentiment) before broad market overview (Section 4).
21	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery (repository `CLAUDE.md` rule 1).
22
23	---
24
25	## Step 0 — Preflight
26
27	Follow [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim:
28
29	1. Run `gate-cli preflight --format json`; parse `.route`, `.status`, `.user_message`.
30	2. Branch: `CLI` → continue; `MCP_FALLBACK` → emit `__FALLBACK__` and halt (legacy MCP fallback is outside this repo’s primary skills); `BLOCK` → echo `user_message` and halt.
31	3. When `status == "ready_with_migration_warning"`, remember it — Step 3 appends one migrate hint at the end of the report.
32
33	4. Step 0.5 — Version gate: From `PREFLIGHT_JSON.cli_version`, set `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md). Store `cli_version` for Step 1 (`market_move_explain` needs `>= 0.7.2` for `explain-market-move`).
34
35	Do NOT run `news` / `info` data collection until `route == "CLI"`.
36
37	---
38
39	## Step 1 — Intent routing
40
41	Map the user query to exactly one playbook id from [playbooks/gate-news-intel.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-news-intel.yaml).
42
43	\| Playbook id \| When to pick \| Required slots \|
44	\|-------------\|----------------\|----------------\|
45	\| `news_brief` \| Headlines / “what happened recently” with a named asset \| `symbol` \|
46	\| `event_explain` \| Pure event timeline / detail lookup without price-move attribution \| `symbol` \|
47	\| `market_move_explain` \| “Why did X move / crash / pump / dump”, price-move attribution, market move reason \| `symbol`, `query` \|
48	\| `exchange_listings` \| Listings, delistings, maintenance, announcements \| — \|
49	\| `community_intel` \| “Community take”, Reddit, YouTube, X, social / sentiment (social-first) \| `symbol` \|
50	\| `intel_plus_market` \| User wants news + market or coin background \| `symbol` \|
51	\| `market_wide_intel` \| Broad “what is happening in crypto” without a ticker \| — \|
52
53	#### Version-dependent routing
54
55	`market_move_explain` requires `gate-cli` v0.7.2+ (the earliest version that ships `explain-market-move`). The playbook's `cli_baseline` field documents this. All other playbooks remain compatible with v0.5.2.
56
57	If routed to `market_move_explain` but `cli_version` < 0.7.2: fall back to `event_explain` and include this notice in the report footer:
58	> explain-market-move requires gate-cli v0.7.2+. Falling back to event_explain with manual news/event stitching. Upgrade gate-cli for server-side Tavily-powe

People who liked this also viewed

6 picks

Type

gate-news-intel

33stars18forks

View on GitHub

How to install gate-news-intel?

gate/gate-skills/gate-news-intel

$npx -y skills add gate/gate-skills --skill gate-news-intel

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# gate-news-intel
2
3	## General Rules
4
5	⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
6	Do NOT select or call any tool until all rules are read. These rules have the highest priority.
7	→ Read [gate-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/gate-runtime-rules.md)
8	→ Also read [info-news-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/info-news-runtime-rules.md) for gate-info and gate-news shared rules.
9	- Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they
10	exist in the MCP server.
11
12	## CLI and playbook contract
13
14	1. Primary boundary: news, events, announcements, and social/UGC intelligence. Optional `info` calls appear only in playbooks that explicitly add market or coin background (`intel_plus_market`, `market_wide_intel`).
15	2. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (`>= 0.7.6`), prefer playbook `shortcut` / `info_shortcut` blocks; fall back to legacy `commands` on failure or older CLI. When preflight `route` is `CLI`, do not use Gate MCP from this skill.
16	3. Always pass `--format json` on data-collection commands.
17	4. Separate fact from opinion: label facts (dated events, official announcements, news wires) vs community / UGC / X / social (always cite source type: UGC, X, Reddit, YouTube, sentiment index).
18	5. Synthesis order (PRD 5.6.7):
19	- “Why did it drop / crash?” → causal event chain first (Section 2), then optionally market/coin background (Section 4).
20	- “How does the community see ...?” → Section 3 (community / UGC / X / sentiment) before broad market overview (Section 4).
21	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery (repository `CLAUDE.md` rule 1).
22
23	---
24
25	## Step 0 — Preflight
26
27	Follow [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim:
28
29	1. Run `gate-cli preflight --format json`; parse `.route`, `.status`, `.user_message`.
30	2. Branch: `CLI` → continue; `MCP_FALLBACK` → emit `__FALLBACK__` and halt (legacy MCP fallback is outside this repo’s primary skills); `BLOCK` → echo `user_message` and halt.
31	3. When `status == "ready_with_migration_warning"`, remember it — Step 3 appends one migrate hint at the end of the report.
32
33	4. Step 0.5 — Version gate: From `PREFLIGHT_JSON.cli_version`, set `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md). Store `cli_version` for Step 1 (`market_move_explain` needs `>= 0.7.2` for `explain-market-move`).
34
35	Do NOT run `news` / `info` data collection until `route == "CLI"`.
36
37	---
38
39	## Step 1 — Intent routing
40
41	Map the user query to exactly one playbook id from [playbooks/gate-news-intel.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-news-intel.yaml).
42
43	\| Playbook id \| When to pick \| Required slots \|
44	\|-------------\|----------------\|----------------\|
45	\| `news_brief` \| Headlines / “what happened recently” with a named asset \| `symbol` \|
46	\| `event_explain` \| Pure event timeline / detail lookup without price-move attribution \| `symbol` \|
47	\| `market_move_explain` \| “Why did X move / crash / pump / dump”, price-move attribution, market move reason \| `symbol`, `query` \|
48	\| `exchange_listings` \| Listings, delistings, maintenance, announcements \| — \|
49	\| `community_intel` \| “Community take”, Reddit, YouTube, X, social / sentiment (social-first) \| `symbol` \|
50	\| `intel_plus_market` \| User wants news + market or coin background \| `symbol` \|
51	\| `market_wide_intel` \| Broad “what is happening in crypto” without a ticker \| — \|
52
53	#### Version-dependent routing
54
55	`market_move_explain` requires `gate-cli` v0.7.2+ (the earliest version that ships `explain-market-move`). The playbook's `cli_baseline` field documents this. All other playbooks remain compatible with v0.5.2.
56
57	If routed to `market_move_explain` but `cli_version` < 0.7.2: fall back to `event_explain` and include this notice in the report footer:
58	> explain-market-move requires gate-cli v0.7.2+. Falling back to event_explain with manual news/event stitching. Upgrade gate-cli for server-side Tavily-powe

People who liked this also viewed

6 picks

Type