BF react
Operate React applications as a named tool: inspect and diagnose React/Vite projects, design component boundaries and state flow, implement accessible responsive UI, and verify behavior with the project's tests. Use when a task explicitly involves React, JSX/TSX, React hooks, React Router, Vite React configuration, or React build failures. Do not use for framework-agnostic frontend strategy (route to frontend-engineering), browser automation (route to playwright), accessibility policy or audits (route to web-accessibility), or non-React mobile apps (route to mobile-development).
Operate React applications as a named tool: inspect and diagnose React/Vite projects, design component boundaries and state flow, implement accessible…
As a process F 42/100 · Will not run — References files that are not bundled: ../web-accessibility/SKILL.md, ../playwright/SKILL.md, ../frontend-engineering/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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../web-accessibility/SKILL.md - warning
missing-refreference to a missing file: ../playwright/SKILL.md - warning
missing-refreference to a missing file: ../frontend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../mobile-development/SKILL.md - note
edit-residuethe text marks something as outdated (lines 23): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 42/100
- 0Tools and files. 4 referenced file(s) missing: ../web-accessibility/SKILL.md, ../playwright/SKILL.md, ../frontend-engineering/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
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1182 tokens
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
- 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
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 585: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.