SKILLEMALL.ai
GitHub ↗ RU Sign in

BC dexscan-skill

使用此技能获取链上市场数据：代币行情、代币信息、信号、社交热度、聪明钱地址。 **触发场景**： - 用户提到 dexscan - 用户提到代币行情、价格、市值、成交量、流动性、涨跌幅、持币地址数 - 用户提到代币信号、首次信号推送最大涨幅、信号推送 - 用户提到代币热度、热度排行榜、KOL讨论 - 用户提到聪明钱、牛人榜、地址盈亏 - 用户提到搜索代币、搜索地址

ClawHub Agent Skills author: yishixing01 v1.0.5 MIT-0 6 files body ≈ 1 176 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
88
Quality 40%
79
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 12

✓ No critical or high findings

Medium and low: 12
  • low Secrets in code secret-high-entropy-token references/address.md:160
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "tokenContractAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/address.md:244
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "baseAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/coin.md:90
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "tokenContractAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/coin.md:201
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "tokenContractAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/coin.md:221
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "address": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/coin.md:333
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "cursor": { "address": "38Hb…ump", "signalTime": 1776122402000 },
    quoted
  • low Secrets in code secret-high-entropy-token references/coin.md:336
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "address": "38Hb…ump",
    quoted
  • low Secrets in code secret-high-entropy-token references/market.md:89
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "tokenContractAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/market.md:195
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "tokenContractAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/market.md:215
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "address": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/market.md:313
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "baseAddress": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token references/market.md:316
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "quoteAddress": "EPjF…t1v",
    quoted

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 40 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1176 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 183: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.

External checks

ClawHub: suspicious
This appears to be a real DexScan market-data skill, but it needs review because it can use wallet analytics and searches parent .env files for API credentials.
LLM: suspicious (high) · VirusTotal: · 5 Jul 2026