bim-clash-detection 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 provided SKILL.md excerpt is truncated, but the full file is expected to be complete in the repository.
• SKILL.md lacks explicit setup instructions and a clear step-by-step workflow for using the provided classes, relying on the agent to implement the detection logic.
• No limitations or edge-case considerations are documented (e.g., bounding box approximation accuracy, handling of incomplete models).
• Quality score needs review