AB frontend-design
Build polished, conversion-aware frontends with strong visual taste, clear hierarchy, and production-grade HTML/CSS/JS. Landing pages, dashboards, components, emails, redesigns — all as working files. Avoids generic AI aesthetics. Every design has a point of view.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting
GeneratorSoftware developmentInfrastructureMarketingtype and topics are labelled automatically from the skill text
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5654 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 66/100
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (frontend-design) differs from the folder (frontend-design-skill)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 11 branches
- 70Execution cost. Instruction body is 5654 tokens
- 85Steps. 165 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 24 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 264: enough signal without eating the budget
- +4Structure: 64 headings
- +3Step-by-step instructions: 165 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: clean
This is an instruction-only frontend design skill with purpose-aligned file creation and a form example that users should review before publishing.
LLM: benign (high) · VirusTotal: · 29 May 2026