OpenAgentSkill
GitHub200+

Pre-install eval

customer-escalation 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
82
Eval report
85
Trust
87
Audit
67
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

84

pass

Task wording matches this skill metadata.

  • Evaluate customer-escalation before installing it in an agent workflow
  • other
  • Customer support workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add anthropics/knowledge-work-plugins --skill customer-escalation

Install command safety

92

pass

standard package or runtime install path

  • npx skills add anthropics/knowledge-work-plugins --skill customer-escalation

Trust score

85

pass

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

  • Strong shortlist
  • 30K GitHub stars
  • Apache-2.0

Audit score

87

pass

Safe to try

  • AI review approval is missing

Agent safety gate

67

warn

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

  • Require human approval before installing into a real workspace.
  • AI review approval is missing

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

72

warn

filesystem or document access, network or browser access

  • Browser automation: medium
  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • AI review approval is missing
  • Quality score needs review
  • Review status: 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

1d since push

Alternatives available

pass

82

Alternative skills are available for comparison.