OpenAgentSkill
GitHub200+

Pre-install eval

beat-hintermann-taa-perspective 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
72
Trust
76
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 beat-hintermann-taa-perspective before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add swaylq/master-skill --skill beat-hintermann-taa-perspective

Install command safety

92

pass

standard package or runtime install path

  • npx skills add swaylq/master-skill --skill beat-hintermann-taa-perspective

Trust score

72

warn

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

  • Strong shortlist
  • 128 GitHub stars
  • MIT

Audit score

76

warn

Needs review

  • SKILL.md is partially truncated in the excerpt (ends mid-sentence), but the full file appears complete in the repository.

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 is partially truncated in the excerpt (ends mid-sentence), but the full file appears complete in the repository.

License clarity

86

pass

MIT

  • MIT

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
  • production agents without a repository review
  • SKILL.md is partially truncated in the excerpt (ends mid-sentence), but the full file appears complete in the repository.
  • The skill is a knowledge/perspective distillation rather than an executable workflow; it may require additional context or integration to be used as an agent action.
  • Quality score needs review
  • Stars/forks activity: 128 stars, 11 forks; issue activity unavailable in current metadata

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.