OpenAgentSkill
GitHub200+

Pre-install eval

aws-health-events 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
69
Eval report
67
Trust
73
Audit
61
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

94

pass

Task wording matches this skill metadata.

  • Evaluate aws-health-events 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 aws/tools-for-devops-agent --skill aws-health-events

Install command safety

92

pass

standard package or runtime install path

  • npx skills add aws/tools-for-devops-agent --skill aws-health-events

Trust score

67

warn

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

  • Manual review
  • 42 GitHub stars
  • Apache-2.0

Audit score

73

warn

Needs review

  • SKILL.md's description instructs agents to 'ALWAYS use this skill' at the start of any incident investigation, which can cause over-activation and unnecessary AWS Health API calls even when AWS-side events are unlikely to be related.

Agent safety gate

61

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's description instructs agents to 'ALWAYS use this skill' at the start of any incident investigation, which can cause over-activation and unnecessary AWS Health API calls even when AWS-side events are unlikely to be related.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

86

pass

network or browser access

  • 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
  • SKILL.md's description instructs agents to 'ALWAYS use this skill' at the start of any incident investigation, which can cause over-activation and unnecessary AWS Health API calls even when AWS-side events are unlikely to be related.
  • The provided SKILL.md excerpt does not clearly include error-handling guidance for common failures such as AccessDeniedException, SubscriptionRequiredException, or unsupported region/endpoint issues.
  • Pagination and response-size handling for DescribeEvents and DescribeAffectedEntities are not explicitly described in the excerpt, which could lead to incomplete results or missed events in large accounts.

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.