AD bitcoin
Query Bitcoin (BTC L1) blockchain data with USD pricing — wallet balances, address info, transaction details, UTXO analysis, fee estimation, mempool stats, and live network health. Uses Mempool.space REST API (https://mempool.space/docs/api/rest). No API key required.
Query Bitcoin (BTC L1) blockchain data with USD pricing — wallet balances, address info, transaction details, UTXO analysis, fee estimation, mempool stats…
As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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-tokenREADME.md:145High-entropy token-like string (may be an id, hash or a credential)python3 scripts/bitcoin_client.py address 1A1z…2Kt
-
low Secrets in code
secret-high-entropy-tokenREADME.md:315High-entropy token-like string (may be an id, hash or a credential)python3 scripts/bitcoin_client.py address 1A1z…2Kt
-
low Secrets in code
secret-high-entropy-tokenscripts/bitcoin_client.py:478High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)python3 bitcoin_client.py address 1A1z…2Kt
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:85High-entropy token-like string (may be an id, hash or a credential)address 1A1z…2Kt
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 268 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "credits"
Process rating: all ten parameters 44/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Consistency. Frontmatter name (bitcoin) differs from the folder (bitcoin-2)
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 58 steps, 2 vague phrases
- 100Execution cost. Instruction body is 1711 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (10 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.