| name | gate-info-web3 |
| version | 2026.6.22-1 |
| updated | 2026-06-22 |
| description | 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. Delegate: gate-info-risk (safety), gate-info-research (broad research), gate-news-intel (events/sentiment). v0.7.6+ shortcuts (+address-tracker, +token-onchain, +community-scan); legacy fallback below 0.7.6. |
gate-info-web3
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 and gate-news shared rules (tool degradation, report standards, security, routing).
- 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.
CLI and playbook contract
- 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.
- 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.
- Always pass
--format json on data-collection commands.
- 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.
- Required slots (
address+chain, token+chain, platform, exchange+asset, symbol, entity_query) must be explicit; if ambiguous, ask — do not guess chain or contract.
- Final user-facing reports may use the user’s locale; this
SKILL.md stays English for discovery (see repository CLAUDE.md rule 1).
Step 0 — Preflight
Follow skills/_shared/preflight.md verbatim:
- Run
gate-cli preflight --format json; parse .route, .status, .user_message.
- Branch:
CLI → continue; MCP_FALLBACK → emit __FALLBACK__ and halt; BLOCK → echo user_message and halt.
- When
status == "ready_with_migration_warning", Step 3 appends one migrate hint at the end of the report.
- Step 0.5: Set
cli_version and shortcuts_enabled per skills/_shared/cli-version-routing.md.
Do NOT run any info / news data call until route == "CLI".
Step 1 — Intent routing
Map the user query to exactly one playbook id from playbooks/gate-info-web3.yaml.
| Playbook id | When to pick | Required slots |
|---|
address_tracking | Trace a wallet / “who is this address” / recent on-chain activity (behavior, not safety verdict). | address, chain |
token_onchain | Token-level flow / holders / smart-money style signals for a known token + chain. | token, chain |
entity_intel | Named desk / fund / entity (e.g. what a named desk is doing). | entity_query |
protocol_platform | Protocol TVL, fees, volume, profile, history, or yield on a named platform (e.g. Uniswap, Aave). | platform |
exchange_reserves | Exchange reserve / proof-of-reserves style questions for an asset. | exchange, asset |
liquidation_heatmap | Perp / futures liquidation density by price (which price levels see liquidations). | symbol |
stablecoin_bridge | Stablecoin market / peg / chain distribution, or bridge rankings — not a single-token DEX question. | — |
token_onchain_social | User wants on-chain data plus news/sentiment/UGC in one pass. | token, chain |
Slot extraction notes
chain: normalize to ids the CLI accepts (eth, bsc, arbitrum, base, solana, ...). If missing, ask.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-platform-info / get-yield-pools as the playbook lists.token vs symbol: on-chain playbooks use token (+ chain); reserves / heatmap often use listed symbol (e.g. BTC, USDC).
Cross-skill routing at Step 1
| User signal | Route to |
|---|
| Safety / honeypot / blacklist / compliance verdict (safety-first) | gate-info-risk (primary) |
| General research, fundamentals, macro, multi-coin compare without on-chain/protocol framing | gate-info-research (primary) |
| Pure “why did it move”, “community narrative”, no on-chain ask | gate-news-intel (primary) |
Step 2 — Data collection
Execute the chosen playbook. Commands in the same parallel_group may run concurrently; wait for the group before the next.
Shortcut routing (gate-cli >= 0.7.6)
When shortcuts_enabled, run playbook shortcut blocks per skills/_shared/cli-version-routing.md:
| Playbook | Shortcut |
|---|
address_tracking | info +address-tracker |
token_onchain | info +token-onchain |
token_onchain_social | +token-onchain then +community-scan when symbol_present (coin: {symbol}); resolve ticker from coin_context when token is contract_address. +community-scan covers UGC/X/sentiment only — news_brief (search-news headlines) runs via post_shortcut_optional_ids. All news ids require symbol_present; skip them if unresolved (do not pass contract to --coin). |
Note missing_sections may include trace-fund-flow or smart_money — cite in report.
Legacy-only paths
info onchain trace-fund-flow and info onchain get-entity-profile: not shipped. Use get-address-info + get-address-transactions or news feed web-search.- Below 0.7.6, use legacy
commands in the playbook YAML (plus optional search-platforms pre-check for fuzzy platform names).
Failure policy
- Required command fails → abort, surface CLI error, no fabricated section.
- Optional command fails → mark the matching subsection as no data in Step 3.
- News/web search may be partial or opinion-heavy — tag those lines as community / media, not as on-chain facts.
Step 3 — Synthesis
Produce exactly six sections, in this order (section titles in the final user report may be localized; structure is fixed):
Report template
## Web3 intel — {subject}
### 1. Subject and executive takeaways
- Objects (address / token / protocol / exchange / entity / theme)
- 1–3 neutral bullets; separate **on-chain verifiable** vs **needs confirmation**
### 2. On-chain activity (core)
- Recent interaction types, large transfers, label-based identity hints — **only** from on-chain / `info onchain` commands
### 3. Flows, positioning, smart money, entity read
- Flow and holder / positioning structure (`get-address-transactions`, `get-token-onchain`)
- Smart-money or whale-style signals (from token-onchain data)
- Entity questions: if `web-search` is used, mark as **second-hand** narrative
### 4. Protocol or platform metrics (if relevant)
- Scale (TVL, volume, fees), direction of change, pools or assets that matter (`platformmetrics` commands)
### 5. Community or news context (if relevant)
- Only when the playbook includes news / web-search: short factual + tone summary; **keep separate** from sections 2–3
### 6. Risks and watchlist
- Data gaps, follow-up on-chain signals, **non-advice** watch items
> This report is based on public data and tool output; it is not investment advice.
Migrate hint (only if Step 0 had ready_with_migration_warning)
Append verbatim the migration blockquote line from skills/_shared/report-style.md (the line starting with ⚙️ and gate-cli migrate --dry-run), same as other primary skills.
Cross-skill routing + Safety rules
Routing
Follow skills/_shared/routing.md. Web3-specific reminders:
| Follow-up intent | Target |
|---|
| “Is it safe / honeypot / sanctioned?” | gate-info-risk (primary) |
| “Full research report / worth buying?” (no on-chain focus) | gate-info-research (primary) |
| “Why pump/dump / Twitter drama only” | gate-news-intel (primary) |
Safety rules
Follow skills/_shared/report-style.md. Web3-specific:
- No buy/sell recommendations; no price targets.
- Do not treat empty on-chain data as proof of safety — that belongs in risk skill.
- When web-search or UGC is used, prefix interpretive lines with media / community so they are not confused with chain state.
References
