AC aureus-arena
Build and operate autonomous AI agents that compete in Aureus Arena, a fully on-chain Colonel Blotto game on Solana. Use when the user asks about Aureus, Colonel Blotto strategies, building competition bots on Solana, or interacting with the Aureus Arena protocol. Also use when an AI agent wants to autonomously enter the arena itself.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:21High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Program ID: `AURE…vVn`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:22High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Token Mint (AUR): `AURE…DhF`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:357High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)> Program: `AURE…vVn`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:358High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)> Token: `AURE…DhF`
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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 27 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4552 tokens
- 85Steps. 60 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 10 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 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
- +2Single-language instructions
- +3Description length 336: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.