AB frontend-design-agency
Use when building, redesigning, or extending web-app frontends that must look production-ready, visually distinctive, and systemically designed instead of like generic AI-generated UI
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting
GeneratorSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenevaluation_output/evaluation_results.json:115High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"Design System Rules: Mindest-Ebenen Disp…ono",
detector
Files scanned: 34. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 157 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3255 tokens
- 100Running it twice. No mutating operations
- low 14 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 157 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (15 of 15)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.
External checks
ClawHub: clean
This is a German-language frontend design workflow skill with local reference assets and no evidence of hidden access, persistence, exfiltration, or destructive behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026