gate-info-research

Name: gate-info-research
Author: gate

33stars18forks

How to install gate-info-research?

gate/gate-skills/gate-info-research

$npx -y skills add gate/gate-skills --skill gate-info-research

Installs into the current project.

Summary

Use this skill whenever the user wants Gate.info / Gate.news research via gate-cli: single-coin, market overview, multi-coin compare, TA, macro, or research+news. Trigger phrases include: analyze SOL, how is BTC, compare BTC and ETH, technical analysis, NFP impact, research with

Files · 1

View on GitHub

SKILL.md

1	# gate-info-research
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 (tool degradation, report standards, security, routing).
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. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (see Step 0.5, `cli_version >= 0.7.6`), prefer playbook `shortcut` / `additional_shortcut` blocks (`info +coin-overview`, `+market-overview`, etc.); on failure or older CLI, fall back to legacy `commands` in the playbook YAML.
15	2. Call `gate-cli info …` / `gate-cli news …` only as listed in [playbooks/gate-info-research.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-research.yaml). This primary skill does not call Gate MCP tools when preflight `route` is `CLI` (MCP is for legacy wrapper skills only).
16	3. Always pass `--format json` on data-collection commands. Never mix JSON and pretty output in the same pipeline.
17	4. If a required slot (e.g. `symbol` for `single_coin`) cannot be parsed with high confidence, ask the user to clarify. Never guess a ticker from a project name.
18	5. Cross-domain allowed: `gate-info-research` MAY call `gate-cli news …` when the `research_plus_news` playbook fires. It MUST NOT take over user queries whose primary intent is news / events / community; those route to `gate-news-intel`.
19	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery and indexing (see repository `CLAUDE.md` rule 1).
20
21	---
22
23	## Step 0 — Preflight
24
25	Follow the shared contract in [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim. Summary:
26
27	1. Run `gate-cli preflight --format json`; parse `.route`, `.status`, `.user_message`.
28	2. Branch: `CLI` → continue; `MCP_FALLBACK` → emit `__FALLBACK__` and halt; `BLOCK` → echo `user_message` and halt.
29	3. When `status == "ready_with_migration_warning"`, remember it — Step 3 appends one migrate hint at the end of the report.
30	4. Step 0.5 — Version gate: From the same `PREFLIGHT_JSON`, set `cli_version` and `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md) (`shortcuts_enabled=true` when `>= 0.7.6`).
31
32	Do NOT run the first data-collection command until Step 0 returns `route == "CLI"`.
33
34	---
35
36	<!--
37	Step 0.5 — Skill update check (OPT-IN, disabled by default).
38
39	The script [scripts/update-skill.sh](https://github.com/gate/gate-skills/blob/master/scripts/update-skill.sh) is shipped and functional, but agents
40	do NOT run it as part of the normal flow (zero overhead, no token needed).
41	Skill authors can still invoke it manually when they want to sync SKILL.md
42	from upstream:
43
44	bash "$SKILL_ROOT/scripts/update-skill.sh" check gate-info-research
45
46	Result semantics, strict-check mode (`GATE_SKILL_CHECK_STRICT=1`) and the
47	auto-apply path (`GATE_SKILL_UPDATE_MODE=auto`) are documented in
48	[skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md). To re-enable
49	this step inside the agent flow, delete this HTML comment wrapper so the
50	block becomes part of the rendered SKILL.md again.
51	-->
52
53	---
54
55	## Step 1 — Intent routing
56
57	Map the user's query to exactly one playbook id. Read the playbook definitions from [playbooks/gate-info-research.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-research.yaml). The mapping below is authoritative.
58
59	\| Playbook id \| When to pick \| Required slots \| Legacy skill it covers \|
60	\|-----------------------\|------------------------------------------------------------------------------------------------\|----------------\|------------------------------------------\|
61	\| `single_coin` \| "analyze SOL", "how is BTC

People who liked this also viewed

6 picks

Type

gate-info-research

33stars18forks

View on GitHub

How to install gate-info-research?

gate/gate-skills/gate-info-research

$npx -y skills add gate/gate-skills --skill gate-info-research

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# gate-info-research
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 (tool degradation, report standards, security, routing).
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. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (see Step 0.5, `cli_version >= 0.7.6`), prefer playbook `shortcut` / `additional_shortcut` blocks (`info +coin-overview`, `+market-overview`, etc.); on failure or older CLI, fall back to legacy `commands` in the playbook YAML.
15	2. Call `gate-cli info …` / `gate-cli news …` only as listed in [playbooks/gate-info-research.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-research.yaml). This primary skill does not call Gate MCP tools when preflight `route` is `CLI` (MCP is for legacy wrapper skills only).
16	3. Always pass `--format json` on data-collection commands. Never mix JSON and pretty output in the same pipeline.
17	4. If a required slot (e.g. `symbol` for `single_coin`) cannot be parsed with high confidence, ask the user to clarify. Never guess a ticker from a project name.
18	5. Cross-domain allowed: `gate-info-research` MAY call `gate-cli news …` when the `research_plus_news` playbook fires. It MUST NOT take over user queries whose primary intent is news / events / community; those route to `gate-news-intel`.
19	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery and indexing (see repository `CLAUDE.md` rule 1).
20
21	---
22
23	## Step 0 — Preflight
24
25	Follow the shared contract in [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim. Summary:
26
27	1. Run `gate-cli preflight --format json`; parse `.route`, `.status`, `.user_message`.
28	2. Branch: `CLI` → continue; `MCP_FALLBACK` → emit `__FALLBACK__` and halt; `BLOCK` → echo `user_message` and halt.
29	3. When `status == "ready_with_migration_warning"`, remember it — Step 3 appends one migrate hint at the end of the report.
30	4. Step 0.5 — Version gate: From the same `PREFLIGHT_JSON`, set `cli_version` and `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md) (`shortcuts_enabled=true` when `>= 0.7.6`).
31
32	Do NOT run the first data-collection command until Step 0 returns `route == "CLI"`.
33
34	---
35
36	<!--
37	Step 0.5 — Skill update check (OPT-IN, disabled by default).
38
39	The script [scripts/update-skill.sh](https://github.com/gate/gate-skills/blob/master/scripts/update-skill.sh) is shipped and functional, but agents
40	do NOT run it as part of the normal flow (zero overhead, no token needed).
41	Skill authors can still invoke it manually when they want to sync SKILL.md
42	from upstream:
43
44	bash "$SKILL_ROOT/scripts/update-skill.sh" check gate-info-research
45
46	Result semantics, strict-check mode (`GATE_SKILL_CHECK_STRICT=1`) and the
47	auto-apply path (`GATE_SKILL_UPDATE_MODE=auto`) are documented in
48	[skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md). To re-enable
49	this step inside the agent flow, delete this HTML comment wrapper so the
50	block becomes part of the rendered SKILL.md again.
51	-->
52
53	---
54
55	## Step 1 — Intent routing
56
57	Map the user's query to exactly one playbook id. Read the playbook definitions from [playbooks/gate-info-research.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-research.yaml). The mapping below is authoritative.
58
59	\| Playbook id \| When to pick \| Required slots \| Legacy skill it covers \|
60	\|-----------------------\|------------------------------------------------------------------------------------------------\|----------------\|------------------------------------------\|
61	\| `single_coin` \| "analyze SOL", "how is BTC

People who liked this also viewed

6 picks

Type