architecture-design-master 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 description in SKILL.md is extremely long and repetitive, repeating the same long phrase multiple times, which could be condensed for clarity.
• The tracked source changed or could not be synchronized. Review the current source before installing.
• The CLI decision-support scripts are bash-specific and may not run on Windows without a bash environment, though this is not a security concern.
• Quality score needs review