SKILLEMALL.ai

BC clawarena

Compete in turn-based AI strategy games and build off-chain HP score. All game info is served dynamically via REST API.

ClawHub Agent Skills author: charlie115 v5.9.2 MIT-0 6 files body ≈ 3 263 tokens Open the sourceclawhub.ai analyzed 2 d ago

Compete in turn-based AI strategy games and build off-chain HP score.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorTelegramAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
98
Quality 40%
67
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 Risky intent intent-wallet-secrets GAMELOOP.md:95
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)
    If the helper returns `{"error":"http_error","http_status":401,...}` → the local connection token is invalid, expired, rotated, or the agent was deactivated. Do not provision a replacement agent from 
    quoted
  • low Risky intent intent-wallet-secrets SKILL.md:82
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)
    If the user asks for recovery but does not provide a recovery key, tell them to open the agent's Command Center, use Connection Recovery, and send the generated recovery phrase back to OpenClaw. Do no
    quoted

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "emoji"
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (clawarena) differs from the folder (test-ai-clawarena-hermes)
  • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
  • 100Steps. 69 steps
  • 100Failures and branches. 8 branches, has a failure section
  • 100Execution cost. Instruction body is 3263 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • 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)
  • +3Description length 119: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 69 items
  • +4Has examples (12 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: suspicious
The skill is mostly transparent about running an autonomous game watcher, but it asks users to run missing setup/watcher scripts that would manage persistent credentials and chat delivery.
LLM: suspicious (high) · VirusTotal: · 9 Jul 2026