OpenAgentSkill
GitHub200+

Pre-install eval

retro 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
79
Eval report
77
Trust
85
Audit
69
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate retro before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add phuryn/pm-skills --skill retro

Install command safety

92

pass

standard package or runtime install path

  • npx skills add phuryn/pm-skills --skill retro

Trust score

77

warn

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

  • Strong shortlist
  • 26K GitHub stars
  • MIT

Audit score

85

warn

Needs review

  • SKILL.md does not explicitly define safe operating boundaries, such as clarifying that sprint data and user-provided files must be treated as untrusted data and never as instructions.

Agent safety gate

69

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 does not explicitly define safe operating boundaries, such as clarifying that sprint data and user-provided files must be treated as untrusted data and never as instructions.

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 does not explicitly define safe operating boundaries, such as clarifying that sprint data and user-provided files must be treated as untrusted data and never as instructions.
  • The skill implies it can analyze sprint performance and velocity, but it does not state what to do when that data is unavailable or incomplete, which could lead to hallucinated metrics.
  • The action item template includes Owner and Deadline placeholders but does not explicitly warn against inventing owner names or deadlines when not provided by the user.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.