CF frontend-engineering
Build and maintain web frontends — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation. Do not use for backend service implementation, data engineering, or platform infrastructure work.
Build and maintain web frontends — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing…
As a process F 21/100 · Will not run — References files that are not bundled: ../playwright/SKILL.md, ../mobile-development/SKILL.md, ../react/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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../playwright/SKILL.md - warning
missing-refreference to a missing file: ../mobile-development/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 21/100
- 0Tools and files. 4 referenced file(s) missing: ../playwright/SKILL.md, ../mobile-development/SKILL.md, ../react/SKILL.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1335 tokens
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
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
- +3No numbered steps or checklist
- +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 326: enough signal without eating the budget
- +4Structure: 6 headings
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.