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

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.
2. Every CLI command MUST exist under gate-cli v0.5.2. Call only what appears in playbooks/gate-info-web3.yaml. When preflight route is CLI, do not invoke Gate MCP tools from this skill.
3. Always pass --format json on data-collection commands.
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.
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.
6. Final user-facing reports may use the user’s locale; this SKILL.md stays English for discovery (see repository CLAUDE.md rule 1).