OpenAgentSkill
GitHub200+

Pre-install eval

ml4t-monitoring-alerting 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.

FailedHigh riskBLOCK Policy
70
Eval report
70
Trust
76
Audit
64
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate ml4t-monitoring-alerting before installing it in an agent workflow
  • finance
  • Finance and quant workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add ml4t/skills --skill ml4t-monitoring-alerting

Install command safety

92

pass

standard package or runtime install path

  • npx skills add ml4t/skills --skill ml4t-monitoring-alerting

Trust score

70

warn

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

  • Manual review
  • 27 GitHub stars
  • Apache-2.0

Audit score

76

fail

Risky

  • Financial research output is not financial advice; require human review before any live investment decision

Agent safety gate

64

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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
  • Low GitHub adoption signal
  • The skill references dependencies (kill-switch, drift-detection, risk-metrics) but does not explain how they are used or integrated.
  • Audit risk risky exceeds max_risk=medium
  • Financial research output is not financial advice; require human review before any live investment decision

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

18d since push

Alternatives available

pass

82

Alternative skills are available for comparison.