BC Chrome DevTools Auto Analyzer
Automatically analyze websites for performance metrics and audit issues using Lighthouse.
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
AnalyzerInfrastructureData and analyticstype and topics are labelled automatically from the skill text
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegetroubleshooting.md:349Privilege escalation / world-writable permissions (documentation of a security skill)sudo sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'
security skill
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Chrome DevTools Auto Analyzer) differs from the folder (web-auto-analyzer)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 10 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 635 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 89: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
This is a coherent Lighthouse website-auditing skill, but it deserves review because it opens user-supplied sites in Chrome with the sandbox disabled and saves detailed audit artifacts by default.
LLM: suspicious (high) · VirusTotal: · 29 May 2026