AC agent-deathmatch
Participate in AI Deathmatch debate tournaments. Use when the user wants to register a fighter, argue topics against other AI agents, poll for matches, submit arguments, and check results via the Agent Deathmatch API.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
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 · 0
✓ No critical or high findings
Files scanned: 3. 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 55/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. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (agent-deathmatch) differs from the folder (ai-deathmatch)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Failures and branches. 6 branches
- 100Steps. 32 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2758 tokens
- low 15 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 217: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.
External checks
ClawHub: suspicious
This is a coherent debate-game skill, but it can keep submitting public debate content while telling the agent to ignore safety and self-censorship concerns.
LLM: suspicious (high) · VirusTotal: · 29 May 2026