SKILLEMALL.ai
RU Sign in

AB subscan-api-skill

Subscan API query assistant. Trigger immediately when the user needs to query blockchain data (blocks, accounts, transactions, staking, governance, assets, etc.), wants to call the Subscan API, or says things like "query on-chain data", "look up a block/address/transaction", "get from Subscan", "subscan api", "subscan-api-skill". Automatically selects the correct endpoint from local swagger docs and formats the results.

ClawHub Agent Skills author: Carl v1.0.0 MIT-0 8 files body ≈ 2 267 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

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

IntegrationInfrastructuretype 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
90/100
safety, quality, tests
Safety 60%
90
Quality 40%
91
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Consistency w 8
40
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

    Medium and low: 10
    • low Secrets in code secret-high-entropy-token swagger/swagger.json:7190
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "example": "EaBR…tPf",
      quoted
    • low Secrets in code secret-high-entropy-token swagger/swagger.json:7304
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "example": "EaBR…tPf",
      quoted
    • low Secrets in code secret-high-entropy-token swagger/swagger.json:7431
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "example": "EaBR…tPf",
      quoted
    • low Secrets in code secret-high-entropy-token swagger/swagger.json:9802
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "example": "14RY…ZgZ",
      quoted
    • low Secrets in code secret-high-entropy-token swagger/swagger.json:10025
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "example": "14RY…ZgZ",
      quoted
    • low Secrets in code secret-high-entropy-token swagger/swagger.yaml:5322
      High-entropy token-like string (may be an id, hash or a credential)
      example: EaBR…tPf
    • low Secrets in code secret-high-entropy-token swagger/swagger.yaml:5408
      High-entropy token-like string (may be an id, hash or a credential)
      example: EaBR…tPf
    • low Secrets in code secret-high-entropy-token swagger/swagger.yaml:5500
      High-entropy token-like string (may be an id, hash or a credential)
      example: EaBR…tPf
    • low Secrets in code secret-high-entropy-token swagger/swagger.yaml:7230
      High-entropy token-like string (may be an id, hash or a credential)
      example: 14RY…ZgZ
    • low Secrets in code secret-high-entropy-token swagger/swagger.yaml:7393
      High-entropy token-like string (may be an id, hash or a credential)
      example: 14RY…ZgZ

    Files scanned: 8. 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 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 40Consistency. Frontmatter name (subscan-api-skill) differs from the folder (subscan-api)
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 20 steps
    • 100Failures and branches. 9 branches, has a failure section
    • 100Execution cost. Instruction body is 2267 tokens
    • 100Running it twice. No mutating operations
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (8 tags): a typed call is more reliable

    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)
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 423: enough signal without eating the budget
    • +4Structure: 24 headings
    • +3Step-by-step instructions: 20 items
    • +3Output format is stated explicitly
    • +4Has examples (8 code blocks)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    This appears to be a real Subscan API helper, but it needs review because it stores an API key locally and its helper can send that key to any URL if misused.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026