BD lost-bitcoin
Search and analyze lost bitcoins - find old inactive wallets, analyze dormant addresses, track ancient coins and research forgotten wealth on the Bitcoin blockchain.
Search and analyze lost bitcoins - find old inactive wallets, analyze dormant addresses, track ancient coins and research forgotten wealth on the Bitcoin…
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:71High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"1A1z…fNa", # Genesis block
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:72High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"12c6…rJX", # Early miner
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:171High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"1Bit…kuE", # Bitcoin Eater
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:172High-entropy token-like string (may be an id, hash or a credential) (placeholder value)"1Cou…pVr", # Counterparty burn
placeholder -
low Secrets in code
secret-high-entropy-tokenSKILL.md:249High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"1A1z…fNa",
quoted
Files scanned: 1. 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")
Process rating: all ten parameters 47/100
- 0Result and completion. Does not say what the result is
- 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
- 40Consistency. Frontmatter name (lost-bitcoin) differs from the folder (lost-bitcoin-10li1)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4026 tokens
- 100Steps. 15 steps
- 100Running it twice. No mutating operations
- low 16 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +3Description length 165: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (12 code blocks)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.