AB semia
Audit an agent skill with Semia inside OpenClaw. Use when the user asks to run `semia scan <path>`, "Run Semia audit on this skill", or audit a skill/plugin for behavior risk.
As a process B 71/100 · Nearly there — weak spots: running it twice, progress reporting
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
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 71/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2616 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (8 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +3Description length 175: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.
External checks
ClawHub: suspicious
The skill set is mostly coherent developer guidance, but one review helper defaults to running nested Codex with full local access and sandbox bypass, so it should be reviewed before installation.
LLM: suspicious (medium) · VirusTotal: · 5 Jun 2026