emcn-design-review 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 defaults fix=true, which can lead an agent to modify files across a broad scope without explicit per-change confirmation. This is a safety/usability concern, especially if the user passes a wide scope like 'whole codebase'.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The SKILL.md references `.claude/rules/emcn-components.md` for the chip footer layout but does not include that file's content or describe what to do if it is missing.