From c4d612d2b3afd6944d98a3cc59a9553488aa4672 Mon Sep 17 00:00:00 2001 From: chenjunfeng Date: Fri, 28 Aug 2026 19:06:33 +0800 Subject: [PATCH] docs(contract-dd): fold the routing split into this file and drop the CLAUDE.md PR MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #213 fixed the collision by editing CLAUDE.md's Quick Decision Guide. Keeping the library consistent matters more than closing that collision from outside: no other skill in skills/ reaches into a project doc, and this skill should not be the first. So the split now lives where the rest of the repo puts it — in the skill file — and #213 is closed rather than merged. The existing hand-off table only covered the outbound direction (user wants the explanation, not the verdict). It now covers the inbound direction too, which is where the collision actually was: - **One number vs the raw fields.** "check this token", "research this token", "what's the liquidity", "who holds this" are gmgn-token; 打个分, 尽调, 这个币安全吗, 能不能买, rug check, score this contract are this skill. The description already competes at selection time; this states the same boundary for a reader who has already loaded the file. - **A bare address with no question** is a verdict ask: score here, offer the fields after. Step 0 still resolves token vs wallet first, and the wallet branch now names gmgn-portfolio alongside gmgn-wallet-analysis, since raw holdings / P&L / activity are the portfolio skill's, not the dossier's. Still one file, still no changes outside skills/gmgn-contract-dd/. Co-Authored-By: Claude Opus 5 --- skills/gmgn-contract-dd/SKILL.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/skills/gmgn-contract-dd/SKILL.md b/skills/gmgn-contract-dd/SKILL.md index c98df11..a5b2a5b 100644 --- a/skills/gmgn-contract-dd/SKILL.md +++ b/skills/gmgn-contract-dd/SKILL.md @@ -88,15 +88,18 @@ gmgn-cli market kline --chain sol --address Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11Mc ## Relationship to the neighbouring skills -The holder section (0.35) and the price section (0.20) are deliberately coarse: they exist to move one verdict number, not to explain a chip structure or a chart. When the user wants the explanation rather than the verdict, hand off: +Four skills take a token address. They answer different questions and must not be substituted for each other: | The user wants | Skill | |---|---| +| **one number** — 打个分, 尽调, CA 尽调, 这个币安全吗, 能不能买, rug check, score this contract | **this one** | +| the raw fields — check this token, research this token, what's the liquidity, who holds this, the pool and trader lists | `gmgn-token` | | the chip breakdown — distribution, entry cost, whale / dev / KOL behaviour, risk wallets | `gmgn-holder-analysis` | | a read of the chart — the pattern named, with its own 0-100 | `gmgn-kline-pattern` | -| the raw security / pool / holder / trader fields | `gmgn-token` | -Those skills read the same raw fields on different thresholds and different weights, so their numbers will not match this composite, and neither number is a correction of the other. Never substitute one of their scores for a section score here, and never place two of these numbers side by side without saying they measure different things. +A bare address with no question attached is a verdict ask: score it here, then offer the raw fields afterwards. Step 0 resolves token vs wallet before any of that — a bare base58 address is equally a wallet, and `token info` returns the same empty block either way — so a wallet goes to `gmgn-wallet-analysis` for the dossier, or `gmgn-portfolio` when the raw holdings, P&L and activity are what is wanted. + +The holder section (0.35) and the price section (0.20) are deliberately coarse: they exist to move one verdict number, not to explain a chip structure or a chart. Those three skills read the same raw fields on different thresholds and different weights, so their numbers will not match this composite, and neither number is a correction of the other. Never substitute one of their scores for a section score here, and never place two of these numbers side by side without saying they measure different things. ## Step 0 — Does GMGN have a record for this address at all?