AC lawbchess
Play chess on lawb.xyz/chess with on-chain wagers. Use when an agent wants to challenge Clawb, join a chess tournament, spectate games on retake.tv/clawb, or participate in lawb chess bounties. Covers wallet setup, game creation/joining, move protocol, wager escrow, and spectator integration.
As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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 · 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) (documentation table row)| USDC | `0x83…913` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:73High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| $LAWB | `0x7e…15B` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:79High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| $LAWB | `0xA7…b9F` | 6 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:80High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| GOLD | `0x6F…D4D` | 18 |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:81High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| MOSS | `0xeA…f09` | 18 |
table
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 72 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3861 tokens
- 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
- +2Single-language instructions
- +3Description length 293: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.