OpenAgentSkill
GitHub200+

Pre-install eval

thorlabs-blender-optical-path 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
72
Eval report
72
Trust
77
Audit
61
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 thorlabs-blender-optical-path before installing it in an agent workflow
  • security
  • Security and compliance workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add k-telux/OpticalModeler --skill thorlabs-blender-optical-path

Install command safety

92

pass

standard package or runtime install path

  • npx skills add k-telux/OpticalModeler --skill thorlabs-blender-optical-path

Trust score

72

warn

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

  • Strong shortlist
  • 215 GitHub stars
  • MIT

Audit score

77

warn

Needs review

  • The SKILL.md is highly detailed but may be overwhelming for new users; it relies heavily on external reference documents and scripts that are not fully described in the main file.

Agent safety gate

61

warn

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

  • Require human approval before installing into a real workspace.
  • The SKILL.md is highly detailed but may be overwhelming for new users; it relies heavily on external reference documents and scripts that are not fully described in the main file.

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

filesystem or document access

  • Network access: medium
  • Filesystem 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 SKILL.md is highly detailed but may be overwhelming for new users; it relies heavily on external reference documents and scripts that are not fully described in the main file.
  • The skill assumes a specific environment (Blender, Python scripts) and does not provide explicit setup instructions within SKILL.md, though the repository likely contains them.
  • Quality score needs review
  • Stars/forks activity: 215 stars, 2 forks; issue activity unavailable in current metadata

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.