CF frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
Builds, styles, and polishes web UI and UX.
As a process F 55/100 · Will not run — References files that are not bundled: references/ui-ux-db/README.md, references/design/image-to-code-skill.md, references/design/<brand>.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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-shell-known-hostscripts/perfection/lighthouse-audit.py:13Pipe-to-shell installer from a well-known host (still executes remote code) (code comment; documentation of a security skill)# curl -LsSf https://astral.sh/uv/install.sh | sh
commentsecurity skill
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5172 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/ui-ux-db/README.md - warning
missing-refreference to a missing file: references/design/image-to-code-skill.md - warning
missing-refreference to a missing file: references/design/<brand>.md - warning
missing-refreference to a missing file: references/ui-ux-db/
Process rating: all ten parameters 55/100
- 0Tools and files. 4 referenced file(s) missing: references/ui-ux-db/README.md, references/design/image-to-code-skill.md, references/design/<brand>.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5172 tokens
- 100Steps. 18 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- -5TODO / placeholder text left in the skill
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 197: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.