OpenAgentSkill
GitHub200+

Pre-install eval

otel-telemetry-emissions 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
70
Eval report
71
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 otel-telemetry-emissions 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 ollygarden/opentelemetry-agent-skills --skill otel-telemetry-emissions

Install command safety

92

pass

standard package or runtime install path

  • npx skills add ollygarden/opentelemetry-agent-skills --skill otel-telemetry-emissions

Trust score

71

warn

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

  • Manual review
  • 97 GitHub stars
  • Apache-2.0

Audit score

76

warn

Needs review

  • The SKILL.md excerpt is truncated in the submission, but the provided content is clear and complete enough for evaluation.

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.
  • The SKILL.md excerpt is truncated in the submission, but the provided content is clear and complete enough for evaluation.

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
  • The SKILL.md excerpt is truncated in the submission, but the provided content is clear and complete enough for evaluation.
  • No explicit setup or installation instructions are provided, though the skill is self-contained and requires no special setup.
  • Quality score needs review
  • GitHub adoption: 97 GitHub stars

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.