OpenAgentSkill
GitHub200+

Pre-install eval

hardware 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
71
Eval report
75
Trust
76
Audit
60
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 hardware before installing it in an agent workflow
  • design-creative
  • Design and creative workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add telagod/code-abyss --skill hardware

Install command safety

92

pass

standard package or runtime install path

  • npx skills add telagod/code-abyss --skill hardware

Trust score

75

warn

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

  • Strong shortlist
  • 239 GitHub stars
  • MIT

Audit score

76

warn

Needs review

  • SKILL.md is a routing file and does not contain the full rule content; users must open the referenced files to get the actual guidance. This is acceptable but could be clearer in the description.

Agent safety gate

60

warn

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

  • Require human approval before installing into a real workspace.
  • SKILL.md is a routing file and does not contain the full rule content; users must open the referenced files to get the actual guidance. This is acceptable but could be clearer in the description.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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
  • SKILL.md is a routing file and does not contain the full rule content; users must open the referenced files to get the actual guidance. This is acceptable but could be clearer in the description.
  • No OpenAgentSkill engagement data yet
  • Quality score needs review
  • Stars/forks activity: 239 stars, 32 forks; issue activity unavailable in current metadata

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

warn

76

4mo since push

Alternatives available

info

55

No close alternatives were found in the current shortlist.