BB debank
Query blockchain wallet data via DeBank API — balances, DeFi positions, tokens, NFTs, transaction history, gas prices, and token approvals. Use when the user asks about wallet balances, portfolio, DeFi positions, token prices, NFT holdings, transaction history, or gas prices on any EVM chain.
As a process B 69/100 · Nearly there — weak spots: result and completion, consistency, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read
-
low Secrets in code
secret-high-entropy-tokenREADME.md:57High-entropy token-like string (may be an id, hash or a credential)/debank user balance 0xd8…045
-
low Secrets in code
secret-high-entropy-tokenREADME.md:61High-entropy token-like string (may be an id, hash or a credential)Show me the DeFi positions for 0xd8…045
-
low Broad scope
meta-dynamic-shellSKILL.md:20Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`which debank 2>/dev/null || echo "NOT_INSTALLED"`
-
low Broad scope
meta-dynamic-shellSKILL.md:32Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`debank config show 2>&1`
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected flow-seq-start at node end at line 4, column 26: argument-hint: [command] [args...] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (debank) differs from the folder (debank-skill)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 857 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (10 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 293: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.