OpenAgentSkill
GitHub200+

Pre-install eval

code-explainer 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
74
Eval report
80
Trust
82
Audit
62
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate code-explainer before installing it in an agent workflow
  • coding-agents
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

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

80

warn

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

  • Strong shortlist
  • 1.3K GitHub stars
  • MIT

Audit score

82

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

62

warn

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

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

License clarity

86

pass

MIT

  • MIT

Permission surface

60

warn

filesystem or document access, network or browser access

  • Network access: medium
  • Filesystem access: medium
  • Database 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • Permission surface may require sandboxing
  • The tracked source changed or could not be synchronized. Review the current source before installing.
  • Quality score needs review

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.