Star200+

Pre-install eval

bim-clash-detection Eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

Needs reviewMedium riskREVIEW Policy
75
Eval report
72
Trust
80
Audit
68
Agent safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate bim-clash-detection before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill bim-clash-detection

Install command safety

92

pass

standard package or runtime install path

  • npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill bim-clash-detection

Trust score

72

warn

Good trust signals with a few areas worth checking before rollout.

  • Strong shortlist
  • 282 GitHub stars
  • MIT

Audit score

80

warn

Needs review

  • The provided SKILL.md excerpt is truncated, but the full file is expected to be complete in the repository.

Agent safety gate

68

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • The provided SKILL.md excerpt is truncated, but the full file is expected to be complete in the repository.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network access: medium

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.
  • No OpenAgentSkill engagement data yet
  • 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).

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.