SKILLEMALL.ai
GitHub ↗ RU Sign in

AC web3-data

Explore Web3 on-chain data using Chainbase APIs. Use this skill when the user asks about blockchain data, token holders, wallet addresses, token prices, NFTs, ENS domains, transactions, DeFi portfolios, or any on-chain analytics. Triggers include: "top holders of", "who holds", "wallet address", "address labels", "token price", "token transfers", "NFT owners", "ENS domain", "on-chain data", "blockchain query", "SQL query on-chain", or any request to look up, analyze, or explore Web3/blockchain data across Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, Avalanche, zkSync, and other EVM chains.

ClawHub Agent Skills author: lxcong v1.0.0 7 files · 1 script body ≈ 918 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting

AnalyzerInfrastructureSoftware developmentData and analyticstype 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
92/100
safety, quality, tests
Safety 60%
90
Quality 40%
96
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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.

Exfiltration 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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

    ✓ No critical or high findings

    Medium and low: 6
    • medium Exfiltration net-credential-use scripts/chainbase.sh:67
      Credential used in a network call (verify the destination is the intended service)
      curl -s "$call_url" -H "${call_header}: ${API_KEY}"
    • low Secrets in code secret-high-entropy-token SKILL.md:74
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - USDT: `0xdA…ec7` (ETH)
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:75
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - USDC: `0xA0…B48` (ETH)
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:76
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - WETH: `0xC0…Cc2` (ETH)
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:77
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - DAI: `0x6B…d0F` (ETH)
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:78
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - WBTC: `0x22…599` (ETH)
      quoted

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 16 steps
    • 100Failures and branches. 3 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 918 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

    • +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
    • +5Description quotes 11 example trigger phrases
    • +3Description length 601: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 16 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: clean
    This skill is a coherent Chainbase Web3 data lookup helper with expected external API use and no evidence of hidden persistence, destructive behavior, or off-purpose data access.
    LLM: benign (high) · VirusTotal: suspicious · 28 May 2026