SKILLEMALL.ai
GitHub ↗ RU Sign in

BB frontend-ui-pipeline

Frontend UI workflow for turning vague ideas, UI drafts, and feedback into buildable frontend plans and iteration steps.

ClawHub Agent Skills author: Mr.Q v1.1.0 MIT-0 21 files body ≈ 1 660 tokens Open the sourceclawhub.ai↗ analyzed 30 h ago

Frontend UI workflow for turning vague ideas, UI drafts, and feedback into buildable frontend plans and iteration steps.

As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
B
73/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 21. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 73/100

  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. No external tools needed
  • 100Steps. 96 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1660 tokens
  • 100Running it twice. Mutating operations check current state
  • low 11 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
  • +2Single-language instructions
  • +3Description length 120: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 96 items
  • +3Output format is stated explicitly
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: clean
This is a Markdown-only frontend planning skill with disclosed, limited project-documentation writes and no executable install-time behavior.
LLM: benign (high) · VirusTotal: · 5 Jun 2026