SKILLEMALL.ai
GitHub ↗ RU Sign in

AB cmc-api-dex

API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user mentions DEX API, asks about on-chain token data, wants to look up tokens by contract address, needs security/rug risk checks, or is building DEX integrations. This is the definitive reference for CMC DEX API questions. Trigger: "DEX API", "token by contract address", "CMC security API", "liquidity pool API", "/cmc-api-dex"

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files body ≈ 1 346 tokens Open the sourcegithub.com↗ analyzed 2 d ago

API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis.

As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

IntegrationSoftware developmenttype 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
A
91/100
safety, quality, tests
Safety 60%
88
Quality 40%
95
Run on models
none yet
Process rating
B
73/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    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 · 8

    ✓ No critical or high findings

    Medium and low: 8
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read
    • low Secrets in code secret-high-entropy-token references/security.md:136
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "contract_address": "0x69…933",
      quoted
    • low Secrets in code secret-high-entropy-token references/tokens.md:132
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "ethereum", "contract_address": "0x69…933"},
      quoted
    • low Secrets in code secret-high-entropy-token references/tokens.md:133
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "solana", "contract_address": "DezX…263"}
      quoted
    • low Secrets in code secret-high-entropy-token references/tokens.md:258
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "ethereum", "contract_address": "0x69…933"},
      quoted
    • low Secrets in code secret-high-entropy-token references/tokens.md:259
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "ethereum", "contract_address": "0x95…4cE"}
      quoted
    • low Secrets in code secret-high-entropy-token references/use-cases.md:67
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "ethereum", "contract_address": "0x69…933"},
      quoted
    • low Secrets in code secret-high-entropy-token references/use-cases.md:68
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      {"network_slug": "solana", "contract_address": "DezX…263"}
      quoted

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "requires-credentials"

    Process rating: all ten parameters 73/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 28 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1346 tokens
    • 100Running it twice. No mutating operations
    • low 10 top-level sections: this looks like several domains in one skill

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 482: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 28 items
    • +3Output format is stated explicitly
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (6 of 6)

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