OpenAgentSkill
GitHub200+

Pre-install eval

ThClaws 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
90
Eval report
89
Trust
90
Audit
86
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 ThClaws before installing it in an agent workflow
  • agent-frameworks
  • 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

89

pass

Strong OpenAgentSkill Trust Score across adoption, recent maintenance, license clarity, documentation, dependency/runtime risk, install safety, permission surface, and install availability.

  • Production candidate
  • 1.1K GitHub stars
  • Apache-2.0

Audit score

90

pass

Safe to try

  • No major audit warning from metadata.

Agent safety gate

86

warn

Strong metadata, audit, install, and review signals. Suitable for agent shortlists after normal workspace review.

  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.
  • No major trust warnings detected from available metadata
  • Production credentials, payments, or irreversible account changes without explicit human review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

warn

76

4mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.