gate-info-research

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. Every CLI command in this skill MUST exist under gate-cli v0.5.2. Do not invent +coin-overview / +market-overview / other aggregate shortcuts. If a shortcut ships in a later CLI, it will be opt-in via the playbook's cli_future_shortcut field, not by editing this file.
2. Call gate-cli info … / gate-cli news … only as listed in 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).
3. Always pass --format json on data-collection commands. Never mix JSON and pretty output in the same pipeline.
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.
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.
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).