gate-info-web3

Name: gate-info-web3
Author: gate

33stars18forks

How to install gate-info-web3?

gate/gate-skills/gate-info-web3

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

Installs into the current project.

Summary

Use this skill whenever the user’s main ask is on-chain, protocol, or Web3 behavior (not a pure safety verdict). Covers address and token on-chain analysis, platform metrics, reserves, heatmaps, stablecoins, bridges; optional news/UGC. Legacy alias: gate-info-defianalysis. Delega

Files · 1

View on GitHub

SKILL.md

1	# gate-info-web3
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. Scope naming: Frame answers as Web3 / on-chain / protocol behavior. Do not narrow the narrative to “DeFi-only” unless the user’s question is strictly DeFi/TVL/yield. `gate-info-defianalysis` is a legacy alias for routing only — the canonical skill id is `gate-info-web3`.
15	2. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (`>= 0.7.6`), use playbook `shortcut` / `additional_shortcut` blocks; otherwise legacy `commands`. When preflight `route` is `CLI`, do not invoke Gate MCP tools from this skill.
16	3. Always pass `--format json` on data-collection commands.
17	4. Separate evidence types in the report: label on-chain / CLI facts vs community or media interpretation (news, web search, UGC). Never present rumor as chain truth.
18	5. Required slots (`address`+`chain`, `token`+`chain`, `platform`, `exchange`+`asset`, `symbol`, `entity_query`) must be explicit; if ambiguous, ask — do not guess chain or contract.
19	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery (see repository `CLAUDE.md` rule 1).
20
21	---
22
23	## Step 0 — Preflight
24
25	Follow [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim:
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"`, Step 3 appends one migrate hint at the end of the report.
30	4. Step 0.5: Set `cli_version` and `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md).
31
32	Do NOT run any `info` / `news` data call until `route == "CLI"`.
33
34	---
35
36	<!--
37	Step 0.5 — Skill update check (OPT-IN, disabled by default). See [skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md).
38	-->
39
40	---
41
42	## Step 1 — Intent routing
43
44	Map the user query to exactly one playbook id from [playbooks/gate-info-web3.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-web3.yaml).
45
46	\| Playbook id \| When to pick \| Required slots \|
47	\|-------------\|----------------\|----------------\|
48	\| `address_tracking` \| Trace a wallet / “who is this address” / recent on-chain activity (behavior, not safety verdict). \| `address`, `chain` \|
49	\| `token_onchain` \| Token-level flow / holders / smart-money style signals for a known token + chain. \| `token`, `chain` \|
50	\| `entity_intel` \| Named desk / fund / entity (e.g. what a named desk is doing). \| `entity_query` \|
51	\| `protocol_platform` \| Protocol TVL, fees, volume, profile, history, or yield on a named platform (e.g. Uniswap, Aave). \| `platform` \|
52	\| `exchange_reserves` \| Exchange reserve / proof-of-reserves style questions for an asset. \| `exchange`, `asset` \|
53	\| `liquidation_heatmap` \| Perp / futures liquidation density by price (which price levels see liquidations). \| `symbol` \|
54	\| `stablecoin_bridge` \| Stablecoin market / peg / chain distribution, or bridge rankings — not a single-token DEX question. \| — \|
55	\| `token_onchain_social` \| User wants on-chain data plus news/sentiment/UGC in one pass. \| `token`, `chain` \|
56
57	### Slot extraction notes
58
59	- `chain`: normalize to ids the CLI accepts (`eth`, `bsc`, `arbitrum`, `base`, `solana`, ...). If missing, ask.
60	- `platform`: accept fuzzy names; if multiple matches are plausible, run `gate-cli info platformmetrics search-platforms` only with flags verified in `gate-cli info platformmetrics search-platforms --help`, pick one slug, then run `get-defi-overview` / `get

People who liked this also viewed

6 picks

Type

gate-info-web3

33stars18forks

View on GitHub

How to install gate-info-web3?

gate/gate-skills/gate-info-web3

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# gate-info-web3
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. Scope naming: Frame answers as Web3 / on-chain / protocol behavior. Do not narrow the narrative to “DeFi-only” unless the user’s question is strictly DeFi/TVL/yield. `gate-info-defianalysis` is a legacy alias for routing only — the canonical skill id is `gate-info-web3`.
15	2. Legacy commands MUST exist under `gate-cli v0.5.2`. When `shortcuts_enabled` (`>= 0.7.6`), use playbook `shortcut` / `additional_shortcut` blocks; otherwise legacy `commands`. When preflight `route` is `CLI`, do not invoke Gate MCP tools from this skill.
16	3. Always pass `--format json` on data-collection commands.
17	4. Separate evidence types in the report: label on-chain / CLI facts vs community or media interpretation (news, web search, UGC). Never present rumor as chain truth.
18	5. Required slots (`address`+`chain`, `token`+`chain`, `platform`, `exchange`+`asset`, `symbol`, `entity_query`) must be explicit; if ambiguous, ask — do not guess chain or contract.
19	6. Final user-facing reports may use the user’s locale; this `SKILL.md` stays English for discovery (see repository `CLAUDE.md` rule 1).
20
21	---
22
23	## Step 0 — Preflight
24
25	Follow [skills/_shared/preflight.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/preflight.md) verbatim:
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"`, Step 3 appends one migrate hint at the end of the report.
30	4. Step 0.5: Set `cli_version` and `shortcuts_enabled` per [skills/_shared/cli-version-routing.md](../_shared/cli-version-routing.md).
31
32	Do NOT run any `info` / `news` data call until `route == "CLI"`.
33
34	---
35
36	<!--
37	Step 0.5 — Skill update check (OPT-IN, disabled by default). See [skills/_shared/update-workflow.md](https://github.com/gate/gate-skills/blob/master/skills/_shared/update-workflow.md).
38	-->
39
40	---
41
42	## Step 1 — Intent routing
43
44	Map the user query to exactly one playbook id from [playbooks/gate-info-web3.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-web3.yaml).
45
46	\| Playbook id \| When to pick \| Required slots \|
47	\|-------------\|----------------\|----------------\|
48	\| `address_tracking` \| Trace a wallet / “who is this address” / recent on-chain activity (behavior, not safety verdict). \| `address`, `chain` \|
49	\| `token_onchain` \| Token-level flow / holders / smart-money style signals for a known token + chain. \| `token`, `chain` \|
50	\| `entity_intel` \| Named desk / fund / entity (e.g. what a named desk is doing). \| `entity_query` \|
51	\| `protocol_platform` \| Protocol TVL, fees, volume, profile, history, or yield on a named platform (e.g. Uniswap, Aave). \| `platform` \|
52	\| `exchange_reserves` \| Exchange reserve / proof-of-reserves style questions for an asset. \| `exchange`, `asset` \|
53	\| `liquidation_heatmap` \| Perp / futures liquidation density by price (which price levels see liquidations). \| `symbol` \|
54	\| `stablecoin_bridge` \| Stablecoin market / peg / chain distribution, or bridge rankings — not a single-token DEX question. \| — \|
55	\| `token_onchain_social` \| User wants on-chain data plus news/sentiment/UGC in one pass. \| `token`, `chain` \|
56
57	### Slot extraction notes
58
59	- `chain`: normalize to ids the CLI accepts (`eth`, `bsc`, `arbitrum`, `base`, `solana`, ...). If missing, ask.
60	- `platform`: accept fuzzy names; if multiple matches are plausible, run `gate-cli info platformmetrics search-platforms` only with flags verified in `gate-cli info platformmetrics search-platforms --help`, pick one slug, then run `get-defi-overview` / `get

People who liked this also viewed

6 picks

Type