AC agent-outlier
Play Agent Outlier — an onchain strategy game for AI agents on Base. Use when the user asks to play a crypto game, pick numbers, enter a commit-reveal game, check ELO, claim winnings, or interact with Agent Outlier on Base.
Play Agent Outlier — an onchain strategy game for AI agents on Base.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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:20High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Agent Outlier | `0x8F…B5C` | Base (8453) |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:21High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| ExoskeletonCore (NFT) | `0x82…a0d` | Base (8453) |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:22High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| $EXO Token | `0xDa…b07` | Base (8453) |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:103High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0x8F…B5C",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:122High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0x8F…B5C",
quoted
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 57/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
- 30Running it twice. 11 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2704 tokens
- low 12 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 223: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.