AB blockchain-scanner
Blockchain Scanner: Query EVM blockchain data: balances (up to 20 addresses), transactions, gas prices, contract ABIs. Supports Ethereum, Polygon, Base, Arbitrum, Optimism. Use when an agent needs blockchain scanner, blockchain transaction history & activity tracking, ethereum gas price & fee management, smart contract development, crypto balance & account management, balance, address, chain through AgentPMT-hosted remote tool calls. Discovery terms: blockchain scanner.
Blockchain Scanner: Query EVM blockchain data: balances (up to 20 addresses), transactions, gas prices, contract ABIs.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:59High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": ["0xd8…045"]
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:69High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"0xd8…045",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:70High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"0xAb…C9B"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:102High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": ["0xd8…045"],
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:112High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": ["0xd8…045"],
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
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
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (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
- 85Steps. 79 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3608 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 474: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.