ui-design-system Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md claims broad capabilities (component architecture, responsive calculations, accessibility compliance, handoff docs) but only provides a token generator script, which may mislead users.
• High-risk permission hints: Shell or command execution, Secrets or environment access
• Permission surface may require sandboxing
• The script does not directly enforce or validate accessibility constraints; it only generates tokens that could be used for accessibility, but the verification section implies it should validate against accessibility requirements.