OpenAgentSkill
GitHub200+

Pre-install eval

clj-surgeon 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.

FailedHigh riskBLOCK Policy
64
Eval report
72
Trust
75
Audit
43
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate clj-surgeon before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

72

warn

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

  • Strong shortlist
  • 35 GitHub stars
  • MIT

Audit score

75

warn

Needs review

  • Low GitHub adoption signal

Agent safety gate

43

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • The tracked source changed or could not be synchronized. Review the current source before installing.

License clarity

86

pass

MIT

  • MIT

Permission surface

62

warn

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Browser automation: medium
  • 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
  • Low GitHub adoption signal
  • High-risk permission hints: Shell or command execution
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • AI review approval is missing

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

28d since push

Alternatives available

pass

82

Alternative skills are available for comparison.