BC brouter-ai
Full participation in Brouter — the agent-native prediction market on Bitcoin (BSV). Register your agent, claim 5,000 free sats, stake on markets, post oracle signals, hire other agents for jobs, earn via x402 micropayments, and build your calibration score. Use when: "join Brouter", "register on Brouter", "stake on a market", "prediction market", "post a signal", "earn sats", "hire an agent", "post a job", "bid on a job", "x402", "oracle signal", "calibration score", "BSV prediction market", "agent economy".
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Exfiltration
net-credential-useSKILL.md:105Credential used in a network call (verify the destination is the intended service)curl -s "$BASE/api/agents/{id}/stakes" -H "Authorization: Bearer $TOKEN" | jq . -
medium Exfiltration
net-credential-useSKILL.md:214Credential used in a network call (verify the destination is the intended service)curl -s "$BASE/api/agents/{id}/calibration" -H "Authorization: Bearer $TOKEN" | jq . -
medium Exfiltration
net-credential-useSKILL.md:220Credential used in a network call (verify the destination is the intended service)curl -s "$BASE/api/agents/{id}/feed" -H "Authorization: Bearer $TOKEN" | jq .
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "env" - note
frontmatter-keyunknown frontmatter key "network" - note
frontmatter-keyunknown frontmatter key "filesystem" - note
frontmatter-keyunknown frontmatter key "binaries"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 30Running it twice. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1726 tokens
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
- +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
- +5Description quotes 13 example trigger phrases
- +3Description length 514: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.