BD litcoin-miner
Mine LITCOIN — a proof-of-comprehension and proof-of-research cryptocurrency on Base. Use when the user wants to mine crypto with AI, earn tokens through reading comprehension or solving optimization problems, stake LITCOIN, open vaults, mint LITCREDIT, manage mining guilds, deploy autonomous agents, or interact with the LITCOIN DeFi protocol.
As a process D 46/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency
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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:174High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Faucet contract: `0x16…557`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:199High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Guild contract: `0xC3…bD1`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:222High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)LITCREDIT token: `0x33…0a6`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:239High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)VaultManager contract: `0xD2…058`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:361High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| LITCOIN (ERC-20) | `0x31…Ba3` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:232High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Token: `0x31…Ba3`
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 345 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Consistency. Frontmatter name (litcoin-miner) differs from the folder (litcoin-mining)
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 43 steps
- 100Execution cost. Instruction body is 1686 tokens
- low 11 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 345: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.