BB openscan-crypto
Navigate and query crypto networks via OpenScan infrastructure. Use when the user asks about blockchain data — balances (ETH, ERC20, BTC), blocks, transactions, gas prices, mempool, fee estimates, token lookups, event decoding, RPC endpoints, or ENS resolution. Supports Ethereum, Bitcoin, Arbitrum, Optimism, Base, Polygon, BNB and Sepolia. Powered by @openscan/network-connectors and @openscan/metadata.
Navigate and query crypto networks via OpenScan infrastructure.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions
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 · 11
✓ No critical or high findings
Medium and low: 11
-
low Secrets in code
secret-high-entropy-tokenscripts/crypto-cli.mjs:734High-entropy token-like string (may be an id, hash or a credential)// Use the ENS Universal Resolver at 0xce…F67
-
low Secrets in code
secret-high-entropy-tokenscripts/crypto-cli.mjs:735High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const UNIVERSAL_RESOLVER = "0xce…F67";
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/crypto-cli.mjs:772High-entropy token-like string (may be an id, hash or a credential)// ENS Registry: 0x00…e1e
-
low Secrets in code
secret-high-entropy-tokenscripts/crypto-cli.mjs:774High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const ENS_REGISTRY = "0x00…e1e";
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/crypto-cli.mjs:1108High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const ENS_REGISTRY = "0x00…e1e";
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/priceFeeds.mjs:21High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)poolAddress: "0xB4…9Dc", // USDC/WETH Uniswap V2
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/priceFeeds.mjs:28High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)poolAddress: "0x0d…852", // WETH/USDT Uniswap V2
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/priceFeeds.mjs:39High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)poolAddress: "0x6e…827", // WMATIC/USDC QuickSwap
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/priceFeeds.mjs:50High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)poolAddress: "0x16…daE", // USDT/WBNB PancakeSwap V2
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/priceFeeds.mjs:70High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)poolAddress: "0x00…416", // WBTC/USDC Uniswap V2
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:351High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| "Check Satoshi's balance" | `btc-address 1A1z…fNa` |
table
Files scanned: 13. 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 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (web, node) 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. 20 steps, 3 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3299 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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)
- +1No license
- +2Single-language instructions
- +3Description length 405: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (31 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.