BF ui-master-static
Use this skill whenever the user wants to build a production-grade UI with native/vanilla CSS — no Tailwind, no CSS-in-JS, no utility framework. Triggers include: plain Vite + HTML/CSS projects, static sites, simple landing pages, or any project explicitly avoiding a CSS framework; requests for a header, navbar, dashboard shell, or landing layout built with 'plain CSS' or 'native CSS'; requests for modern visual effects (glassmorphism, gradients, scroll animations, parallax, 3D transforms, micro-interactions, CSS Houdini); or establishing a CSS architecture (custom properties as design tokens, BEM naming, file organization) for a project without a component framework. Do NOT use this skill for Tailwind CSS or shadcn/ui projects — use the ui-master skill instead. Do NOT use for CSS-in-JS (styled-components, emotion) or CSS Modules-first projects unless the user explicitly wants the BEM/vanilla approach applied there too.
Triggers include: plain Vite + HTML/CSS projects, static sites, simple landing pages, or any project explicitly avoiding a CSS framework; requests for a…
As a process F 50/100 · Will not run — References files that are not bundled: examples/header.css, examples/dashboard.css, examples/effects-showcase.css
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/header.css - warning
missing-refreference to a missing file: examples/dashboard.css - warning
missing-refreference to a missing file: examples/effects-showcase.css
Process rating: all ten parameters 50/100
- 0Tools and files. 3 referenced file(s) missing: examples/header.css, examples/dashboard.css, examples/effects-showcase.css
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 12 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1463 tokens
- 100Running it twice. No mutating operations
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
- +3Description length 933: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 8 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.