mirror of
https://github.com/GMGNAI/gmgn-skills.git
synced 2026-11-02 07:46:11 +00:00
fix(routing): register the 5 unregistered skills and split the buy-intent route
The routing table listed only 7 of the repo's 12 skills. gmgn-contract-dd,
gmgn-cooking, gmgn-holder-analysis, gmgn-wallet-analysis and gmgn-token-buy
were absent, so an unregistered skill effectively did not exist to the router.
Three routes also sent buy-side asks somewhere that cannot answer them:
- "is this token safe" / "check this token" went to gmgn-token, which
returns raw fields and no verdict. Split into three rows: a token name or
symbol with buy intent goes to gmgn-token-buy (the only skill that
resolves a name to the one right contract and sizes the order); a bare
address wanting a score goes to gmgn-contract-dd; raw fields for an
address already in hand stay with gmgn-token.
- "buy TOKEN" went straight to gmgn-swap, bypassing due diligence. Narrowed
to the skip-the-checks case; a plain "buy TOKEN" is gmgn-token-buy.
Measured on a 20-case routing eval (10 positives) with `claude -p`, first
Skill call recorded, 12 skills installed:
routing table unchanged recall 1/10 and 3/10 over two runs
routing table with this change recall 7/10, reproduced exactly twice
Precision stayed 100% with zero false positives in every run. The 3 remaining
misses are eval cases with no token name, a placeholder address, and an
unsupported chain — none of them resolvable by routing.
Description-level fixes were tried first and measured dead: narrowing
gmgn-token's description, adding a runtime hand-off to gmgn-token's body, and
rewriting gmgn-token-buy's own description each scored 0/10.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
5a221cb259
commit
04dadf6fa9
@@ -33,6 +33,11 @@ This is a **Claude Code plugin** — a collection of GMGN OpenAPI skills for on-
|
||||
| `gmgn-track` | Track trade activity of wallets I follow, KOL trades, Smart Money trades across chains | User asks about trades from wallets they follow; user wants to see what KOLs or Smart Money are buying/selling; user asks "show me what wallets I follow have traded recently", "what are KOLs buying", "show me smart money moves on BSC" |
|
||||
| `gmgn-swap` | Token swap execution + order status query | User wants to swap tokens, execute a trade, or check an order status; user asks "swap SOL for USDC", "buy this token", "check my order"; **requires private key configured in `.env`** |
|
||||
| `gmgn-kline-pattern` | Names the chart pattern (uptrend channel / breakdown / bounce off the lows / distribution / basing / chop) and scores it 0-100 from six measurements computed off the kline response | User asks about 走势, 趋势, 形态, price action, chart pattern, "is it breaking down", "is it consolidating"; user wants a read of the chart rather than the raw candles |
|
||||
| `gmgn-token-buy` | Resolves a token NAME to the one right contract, then sizes the buy order | User names a token by name/symbol (not only an address) and wants to buy it, or gives an address plus an amount and wants the order sized: 能不能买, 能不能冲, 我想梭, 帮我买 200u 的 XX, 确认是正主不是仿盘再买. Owns copycat disambiguation and position/slippage/gas sizing; hands execution to `gmgn-swap` after explicit confirmation. |
|
||||
| `gmgn-contract-dd` | One 0-100 contract due-diligence score for a bare address | User pastes a token address and wants a verdict number, with no name to disambiguate and no amount to size. |
|
||||
| `gmgn-holder-analysis` | Chip / holder structure of one token | User asks about holder distribution or chip concentration. |
|
||||
| `gmgn-wallet-analysis` | Wallet decision dossier | User asks whether a wallet is worth copy-trading. |
|
||||
| `gmgn-cooking` | Launchpad token creation | User wants to create or launch a token. |
|
||||
|
||||
## Quick Decision Guide
|
||||
|
||||
@@ -40,7 +45,9 @@ Match the user's request to the right skill and workflow:
|
||||
|
||||
| User says | Action |
|
||||
|-----------|--------|
|
||||
| "is this token safe", "check this token", "research this token", token address provided | `gmgn-token` → full workflow: `docs/workflow-token-research.md` |
|
||||
| token NAME or symbol + buy intent — "能不能买", "能不能冲", "我想梭", "帮我买 200u 的 XX", "确认是正主不是仿盘再买", with or without an amount | `gmgn-token-buy` — the only skill that resolves a name to the one right contract and sizes the order |
|
||||
| bare token address + "safe?" / "打个分" / "尽调", no name to disambiguate and no amount to size | `gmgn-contract-dd` |
|
||||
| "is this token safe", "check this token", "research this token", raw fields for an address already in hand | `gmgn-token` → full workflow: `docs/workflow-token-research.md` |
|
||||
| "deep report", "full analysis", "全面分析这个项目", "深度报告", "值不值得重仓" | `gmgn-token` + `gmgn-market` → `docs/workflow-project-deep-report.md` |
|
||||
| "what's trending", "hot tokens", "top tokens by volume" | `gmgn-market trending` |
|
||||
| "走势怎么样", "什么形态", "is it breaking down" | `gmgn-kline-pattern` |
|
||||
@@ -55,7 +62,7 @@ Match the user's request to the right skill and workflow:
|
||||
| "跟单评分", "钱包评分", "值不值得跟单", "is this wallet worth copying", "copy trade score", wallet address provided + copy-trade decision | `gmgn-wallet-score` (copy-tradeability angle — score + backtest) |
|
||||
| "钱包发盘情况怎么样", "是不是发币方钱包", "dev 信誉怎么样", "is this a token-creator wallet" | `gmgn-wallet-score` (Dev-reputation angle) |
|
||||
| "risk warning", "风险预警", "有没有巨鲸出货", "流动性正常吗", "这个项目还安全吗" | `gmgn-token` + `gmgn-track` → `docs/workflow-risk-warning.md` |
|
||||
| "swap", "buy TOKEN", "sell TOKEN" | `gmgn-swap` — MUST run `gmgn-token security` on output token first |
|
||||
| "swap", "sell TOKEN", "buy TOKEN" **only when the user says skip the checks** | `gmgn-swap` — MUST run `gmgn-token security` on output token first. A plain "buy TOKEN" with no skip-the-checks instruction is `gmgn-token-buy`. |
|
||||
| "chart", "price history", "kline", "OHLCV" | `gmgn-market kline` |
|
||||
| "my holdings", "my portfolio", "what tokens do I hold" | `gmgn-portfolio holdings` |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user