BF web-accessibility
Design, build, and review accessible web interfaces with native semantics, keyboard and focus behavior, forms and recovery, responsive input, motion, assistive-technology testing, and WCAG 2.2-informed evidence. Use for a11y, WCAG, ARIA, screen-reader, keyboard, focus, dialog, form, widget, or accessibility review work across frameworks. Do not use this skill for unrelated requests; route to the nearest named specialist.
Design, build, and review accessible web interfaces with native semantics, keyboard and focus behavior, forms and recovery, responsive input, motion…
As a process F 45/100 · Will not run — References files that are not bundled: ../hugo-theme/SKILL.md, ../hugo-theme/references/design-accessibility.md, ../product-discovery/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../hugo-theme/SKILL.md - warning
missing-refreference to a missing file: ../hugo-theme/references/design-accessibility.md - warning
missing-refreference to a missing file: ../product-discovery/SKILL.md - warning
missing-refreference to a missing file: ../product-methodology/SKILL.md - warning
missing-refreference to a missing file: ../product-design-and-ux/SKILL.md - warning
missing-refreference to a missing file: ../react/SKILL.md - warning
missing-refreference to a missing file: ../vite/SKILL.md
Process rating: all ten parameters 45/100
- 0Tools and files. 7 referenced file(s) missing: ../hugo-theme/SKILL.md, ../hugo-theme/references/design-accessibility.md, ../product-discovery/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1217 tokens
- 100Running it twice. No mutating operations
- low No test case covers injection arriving through data
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 424: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 16 items
- +4Reference files are cited in the instructions (10 of 10)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.