OpenAgentSkill
GitHub200+

Pre-install eval

implement-authorization 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
66
Eval report
69
Trust
73
Audit
53
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate implement-authorization before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add igmarin/rails-agent-skills --skill implement-authorization

Install command safety

92

pass

standard package or runtime install path

  • npx skills add igmarin/rails-agent-skills --skill implement-authorization

Trust score

69

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 25 GitHub stars
  • MIT

Audit score

73

warn

Needs review

  • SKILL.md references references/output-style.md multiple times, but that file is not present in the submitted skill directory; either include it or remove the references.

Agent safety gate

53

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • SKILL.md references references/output-style.md multiple times, but that file is not present in the submitted skill directory; either include it or remove the references.

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

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
  • production agents without a repository review
  • Low GitHub adoption signal
  • SKILL.md references references/output-style.md multiple times, but that file is not present in the submitted skill directory; either include it or remove the references.
  • No explicit limitations or safe operating boundaries section is included; the skill could clarify supported Rails versions and the assumption that authentication already exists.
  • Quality score needs review

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.