lazyweb-apply-design-best-practices 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 fetch and apply external SKILL.md files, which could introduce prompt injection if a pointer URL is compromised or replaced. The skill mitigates this by requiring verification and fallback, but the risk remains inherent to the design.
• High-risk permission hints: Shell or command execution, Secrets or environment access
• Permission surface may require sandboxing
• The skill references a Lazyweb MCP tool that may not be available in all environments; while a fallback is provided, the dependency on a proprietary tool could reduce portability.