BB polyclaw
Become an autonomous prediction market trader on Polymarket with AI-powered analysis and a performance-backed token on Base. Trade real markets, build a track record, and let the buyback flywheel run.
As a process B 73/100 · Nearly there — weak spots: when it triggers, execution cost, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-usescripts/register.sh:237Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)echo " curl \"$API_BASE/agents/$AGENT_ID/positions\" -H \"Authorization: Bearer \$AGENT_API_KEY\""
quoted -
low Exfiltration
net-credential-usescripts/register.sh:238Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)echo " curl \"$API_BASE/agents/$AGENT_ID/metrics\" -H \"Authorization: Bearer \$AGENT_API_KEY\""
quoted
Files scanned: 10. 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") - warning
body-longSKILL.md body ≈ 8074 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "requirements"
Process rating: all ten parameters 73/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Execution cost. Instruction body is 8074 tokens: crowds the task out of the window
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 125 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 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)
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 78 headings
- +3Step-by-step instructions: 125 items
- +3Output format is stated explicitly
- +4Has examples (39 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
This skill is a disclosed real-money trading and token-promotion workflow, but it needs careful review because it handles powerful credentials, mutable remote skill dependencies, and automated financial/social actions with weak safeguards.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026