gate-info-risk

Name: gate-info-risk
Author: gate

33stars18forks

How to install gate-info-risk?

gate/gate-skills/gate-info-risk

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

Installs into the current project.

Summary

Use this skill whenever the user needs a risk- or safety-first check for a token, address, or project. Covers contract risk, address compliance labels, and project incidents via gate-cli. Triggers: is this coin safe, honeypot, sanctioned, compliance. Info primary; news auxiliary.

Files · 1

View on GitHub

SKILL.md

1	# gate-info-risk
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.
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` (`>= 0.7.6`), `token_risk` may use `info +token-risk` per playbook `shortcut`; fall back to `check-token-security` on failure or older CLI. This skill does NOT call `check-address-risk` or `+address-tracker` for `address_risk`.
15	2. Call `gate-cli info …` / `gate-cli news …` only as listed in [playbooks/gate-info-risk.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-risk.yaml). When preflight `route` is `CLI`, do not call Gate MCP tools from this skill.
16	3. Missing data NEVER counts as "low risk". When the primary command for a chosen playbook is unavailable, the verdict is UNABLE_TO_ASSESS (scope limited; localized labels may appear in the user report) plus an explicit retry hint.
17	4. Always pass `--format json`. Required slots (`token`+`chain`, `address`+`chain`, `symbol`) must be present; if ambiguous, ask the user.
18	5. The report is safety-first: the verdict line comes BEFORE evidence, and high-severity items are always surfaced before medium or low.
19	6. No buy / sell advice. No price predictions. Use verdict bands HIGH / MEDIUM / LOW / UNABLE_TO_ASSESS in this skill’s logic; the final user report may localize those labels. Always include a “what to verify next” list.
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"`, Step 3 appends one migrate hint at the very 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 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-risk
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	Pick exactly one playbook id from [playbooks/gate-info-risk.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-risk.yaml):
58
59	\| Playbook id \| When to pick \| Required slots \|
60	\|----------------\|-----------------------------------------------------------------------------------------------------------\|-----------------------------\|
61	\| `token_risk` \| "is this token safe", "is there a honeypot", "taxes too high", "holder concentration" — subject is a token contract. \| `token`, `chain` (the `token` slot accepts ticker OR contract address) \|
62	\| `address_risk` \| "is this address safe", "sanctioned / OFAC", "blacklist", "is this wallet risky". \|

People who liked this also viewed

6 picks

Type

gate-info-risk

33stars18forks

View on GitHub

How to install gate-info-risk?

gate/gate-skills/gate-info-risk

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# gate-info-risk
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.
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` (`>= 0.7.6`), `token_risk` may use `info +token-risk` per playbook `shortcut`; fall back to `check-token-security` on failure or older CLI. This skill does NOT call `check-address-risk` or `+address-tracker` for `address_risk`.
15	2. Call `gate-cli info …` / `gate-cli news …` only as listed in [playbooks/gate-info-risk.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-risk.yaml). When preflight `route` is `CLI`, do not call Gate MCP tools from this skill.
16	3. Missing data NEVER counts as "low risk". When the primary command for a chosen playbook is unavailable, the verdict is UNABLE_TO_ASSESS (scope limited; localized labels may appear in the user report) plus an explicit retry hint.
17	4. Always pass `--format json`. Required slots (`token`+`chain`, `address`+`chain`, `symbol`) must be present; if ambiguous, ask the user.
18	5. The report is safety-first: the verdict line comes BEFORE evidence, and high-severity items are always surfaced before medium or low.
19	6. No buy / sell advice. No price predictions. Use verdict bands HIGH / MEDIUM / LOW / UNABLE_TO_ASSESS in this skill’s logic; the final user report may localize those labels. Always include a “what to verify next” list.
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"`, Step 3 appends one migrate hint at the very 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 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-risk
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	Pick exactly one playbook id from [playbooks/gate-info-risk.yaml](https://github.com/gate/gate-skills/blob/master/playbooks/gate-info-risk.yaml):
58
59	\| Playbook id \| When to pick \| Required slots \|
60	\|----------------\|-----------------------------------------------------------------------------------------------------------\|-----------------------------\|
61	\| `token_risk` \| "is this token safe", "is there a honeypot", "taxes too high", "holder concentration" — subject is a token contract. \| `token`, `chain` (the `token` slot accepts ticker OR contract address) \|
62	\| `address_risk` \| "is this address safe", "sanctioned / OFAC", "blacklist", "is this wallet risky". \|

People who liked this also viewed

6 picks

Type