OpenAgentSkill
GitHub200+

Pre-install eval

secret-scan 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
59
Eval report
66
Trust
71
Audit
31
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 secret-scan before installing it in an agent workflow
  • other
  • Security and compliance 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

68

warn

credential-bearing install command, standard package or runtime install path

Trust score

66

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 20 GitHub stars
  • Apache-2.0

Audit score

71

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

31

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Metadata combines secrets access with shell or command execution

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

22

fail

secrets or environment access, shell or command execution

  • Shell or command execution: high
  • 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
  • Low GitHub adoption signal
  • High-risk permission hints: Shell or command execution, Secrets or environment access
  • Permission surface may require sandboxing
  • AI review approval is missing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

4d since push

Alternatives available

pass

82

Alternative skills are available for comparison.