BB chain-sensei
On-chain intelligence for AI agents. Analyze wallets, detect risks, trace transactions, and get instant insights on any Ethereum address. Built by an agent, for agents. Free tier: basic wallet analysis. Premium via x402: deep risk scoring, batch operations, alerts.
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenREADME.md:35High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"Check 0x68…Bfa"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"Analyze 0x68…Bfa on Base"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:122High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)User: "Check 0x68…Bfa"
quoted
Files scanned: 4. 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") - note
frontmatter-keyunknown frontmatter key "environment" - note
frontmatter-keyunknown frontmatter key "credentials" - note
frontmatter-keyunknown frontmatter key "persistence" - note
frontmatter-keyunknown frontmatter key "risk_disclosure"
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1142 tokens
- 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
- +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 265: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 33 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.