AC omnibot
Use when AI agents need to read, inspect, operate, navigate, debug, or verify browser state through the omnibot CLI and connected Chromium extension.
Omnibot is Browser Infrastructure for AI Agents.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5935 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
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. 19 mutating operations with no state check
- 40Consistency. Frontmatter name (omnibot) differs from the folder (omnibot-skills)
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5935 tokens
- 85Steps. 62 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Failures and branches. 2 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (27 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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 149: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 62 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (7 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.