OpenAgentSkill
GitHub200+

Pre-install eval

develop-adr 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
75
Eval report
78
Trust
80
Audit
64
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 develop-adr before installing it in an agent workflow
  • automation
  • RAG and knowledge workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add product-on-purpose/pm-skills --skill develop-adr

Install command safety

92

pass

standard package or runtime install path

  • npx skills add product-on-purpose/pm-skills --skill develop-adr

Trust score

78

warn

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

  • Strong shortlist
  • 644 GitHub stars
  • Apache-2.0

Audit score

80

warn

Needs review

  • SKILL.md instructs users to use references/TEMPLATE.md for the output format, but references/TEMPLATE.md is not present in the submitted file list. Ensure that file is included or inline the template directly in SKILL.md.

Agent safety gate

64

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 instructs users to use references/TEMPLATE.md for the output format, but references/TEMPLATE.md is not present in the submitted file list. Ensure that file is included or inline the template directly in SKILL.md.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

86

pass

filesystem or document access

  • 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 instructs users to use references/TEMPLATE.md for the output format, but references/TEMPLATE.md is not present in the submitted file list. Ensure that file is included or inline the template directly in SKILL.md.
  • Quality score needs review
  • Production credentials, payments, or irreversible account changes without explicit human review
  • Sensitive private data before reviewing repository code, license, and permission surface

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.