ui-designer
PassAudited by ClawScan on May 7, 2026.
Overview
This looks like a normal instruction-only UI design assistant with no code, install steps, credentials, or system access; the main thing to notice is its use of shared design context and other agents if available.
Based on the provided artifacts, this skill is safe to install for UI design assistance. Before using it with confidential projects, confirm what the context-manager and any collaborating agents can see or store, and ask the agent to make final delivery and accessibility claims only when they are actually supported.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Existing shared context could shape design decisions, and design deliverables may be reused or visible through the context-manager if your environment supports one.
The skill directs the agent to retrieve and update shared design context. This is aligned with UI design work, but stored context could influence later outputs or retain design details.
Always begin by requesting design context from the context-manager ... Notify context-manager of all design deliverables
Use this with a trusted context-manager, review what design information is stored, and avoid sharing confidential brand or product details unless that is intended.
If your agent platform enables these collaborations, design requirements or deliverables could be passed to other agents.
The skill explicitly anticipates collaboration with other agents. This is normal for a design workflow, but the artifact does not define identity, permission, or data-sharing boundaries between agents.
Integration with other agents: - Collaborate with ux-researcher on user insights - Provide specs to frontend-developer - Work with accessibility-tester on compliance
Confirm which agents are available and trusted before sharing sensitive design, product, or customer information through this workflow.
A user could over-trust the final summary if it claims accessibility validation or deliverables that were not actually completed.
The completion template contains specific claims about component count, dark mode support, and WCAG validation that may be inaccurate if copied literally for every task.
Completion message format: "UI design completed successfully. Delivered comprehensive design system with 47 components ... Accessibility validated at WCAG 2.1 AA level."
Treat the completion text as a template only; require the agent to report the actual deliverables created and any accessibility checks actually performed.