BF web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, best practices, and browser automation testing. Supports automated testing with PinchTab for headless/headed browser control, multi-instance orchestration, and token-efficient content extraction.
As a process F 41/100 · Will not run — References files that are not bundled: ../performance/SKILL.md, ../core-web-vitals/SKILL.md, ../accessibility/SKILL.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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
-
low Dangerous commands
cmd-pipe-to-shellSKILL.md:185Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill; the skill's own vendor host)curl -fsSL https://pinchtab.com/install.sh | bash
security skillvendor-host
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../performance/SKILL.md - warning
missing-refreference to a missing file: ../core-web-vitals/SKILL.md - warning
missing-refreference to a missing file: ../accessibility/SKILL.md - warning
missing-refreference to a missing file: ../seo/SKILL.md - warning
missing-refreference to a missing file: ../best-practices/SKILL.md
Process rating: all ten parameters 41/100
- 0Tools and files. 5 referenced file(s) missing: ../performance/SKILL.md, ../core-web-vitals/SKILL.md, ../accessibility/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (web-quality-audit) differs from the folder (web-quality-audit-ecc)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 88 steps
- 100Execution cost. Instruction body is 3404 tokens
- low The response is described with custom markup (3 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)
- -2localhost URLs: will not work for another user
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 269: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 88 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.