lazyweb-propose-ui-changes 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
• The skill instructs the agent to tell the user to run `curl -fsSL https://www.lazyweb.com/install.sh | sh`, which pipes a remote script directly into the shell. This is a security risk if the URL is compromised or if the user is tricked into running it. While it is a user action, the skill actively recommends it, which could be exploited in a social engineering scenario.
• High-risk permission hints: Shell or command execution
• The skill depends on external MCP tools and a hosted service (lazyweb.com). If the service is unavailable or the MCP is not configured, the skill cannot function, and the fallback instructions are limited.
• Quality score needs review