AD binance-web3
Query token prices, market data, K-line charts, and smart money trading signals via Binance Web3 APIs. Use when users search tokens, check prices, view market data, analyze charts, or track smart money signals on BSC/Base/Solana/Ethereum.
As a process D 38/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-secret-in-urlscripts/token-search.sh:7Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl -s "https://web3…com/bapi/defi/v5/public/wallet-direct/buw/wallet/market/token/search?keyword=…&chainIds=…&orderBy=…" \
placeholder -
low Exfiltration
net-credential-usescripts/token-search.sh:7Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s "https://web3…com/bapi/defi/v5/public/wallet-direct/buw/wallet/market/token/search?keyword=…&chainIds=…&orderBy=…" \
vendor-host
Files scanned: 10. 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 38/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 353 tokens
- 100Running it twice. No mutating operations
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -34 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 238: enough signal without eating the budget
- +4Structure: 8 headings
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.