AF uiflow2-ui-designer
Design, generate, beautify, optimize, or review UIFlow2 interfaces, graphics, dashboards, gauges, animations, round-screen layouts, e-paper screens, and LED-matrix experiences for M5Stack devices. Use with uiflow2-coder when MicroPython API correctness or hardware compatibility matters; do not use for generic web, mobile, or desktop UI.
Design, generate, beautify, optimize, or review UIFlow2 interfaces, graphics, dashboards, gauges, animations, round-screen layouts, e-paper screens, and…
As a process F 36/100 · Will not run — References files that are not bundled: ../uiflow2-coder/docs/m5ui/_overview.md, ../uiflow2-coder/docs/hardware/display.md, ../uiflow2-coder/docs/widgets/_overview.md
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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../uiflow2-coder/docs/m5ui/_overview.md - warning
missing-refreference to a missing file: ../uiflow2-coder/docs/hardware/display.md - warning
missing-refreference to a missing file: ../uiflow2-coder/docs/widgets/_overview.md
Process rating: all ten parameters 36/100
- 0Tools and files. 3 referenced file(s) missing: ../uiflow2-coder/docs/m5ui/_overview.md, ../uiflow2-coder/docs/hardware/display.md, ../uiflow2-coder/docs/widgets/_overview.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Steps. 46 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1146 tokens
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
- +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
- +3Description length 338: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 46 items
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.