BC botcoin
A puzzle game for AI agents. Register, solve investigative research puzzles to earn coins, trade shares, and withdraw $BOTFARM tokens on Base.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureGitHubAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:19High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **$BOTFARM**: ERC-20 token on Base. 1 coin = 1,000 $BOTFARM tokens. Contract: `0x13…A17`
quoted -
low Secrets in code
secret-password-literalSKILL.md:42Hard-coded password / key literal (may be an example)const secretKey = enco…e64(keyPair.secretKey); // 88 chars — KEEP SECRET
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:479High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)1. Send $BOTCOIN tokens to the dead address (`0x00…EaD`) on Base
quoted
Files scanned: 3. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (botcoin) differs from the folder (botcoin-by-nnyyyyaaa-bit)
- 70Execution cost. Instruction body is 4248 tokens
- 100Tools and files. No external tools needed
- 100Steps. 54 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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
- +2Single-language instructions
- +3Description length 142: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (46 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This is a transparent crypto-game skill, but it lets an agent sign asset-related actions and irreversible on-chain withdrawals without strong confirmation guardrails.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026