BB blockchain-exploration
Procedural knowledge for on-chain blockchain analysis using the openscan CLI
As a process B 68/100 · Nearly there — weak spots: when it triggers, consistency, progress reporting
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenrules/token-balance.md:33High-entropy token-like string (may be an id, hash or a credential)--token-address 0xA0…B48 \
-
low Secrets in code
secret-high-entropy-tokenrules/tx-history.md:13High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)openscan tx-history 0xd8…045 --chain 1
detector -
low Secrets in code
secret-high-entropy-tokenrules/tx-history.md:18High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)openscan tx-history 0xd8…045 \
detector -
low Secrets in code
secret-high-entropy-tokenrules/tx-history.md:24High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)openscan tx-history 0xd8…045 \
detector
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 68/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (blockchain-exploration) differs from the folder (openscan-blockchain-exploration)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 7 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 884 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (6 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 76: 120–800 characters recommended
- -45 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
This is a disclosed, read-only blockchain analysis skill that uses the OpenScan CLI and optional RPC/API credentials, with privacy and secret-handling caveats but no hidden or destructive behavior found.
LLM: benign (high) · VirusTotal: · 29 May 2026