OpenAgentSkill
GitHub200+

Pre-install eval

aiml-access-diagnostics 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
62
Eval report
62
Trust
70
Audit
38
Agent safety

do not auto install

Permission surface: secrets or environment access, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate aiml-access-diagnostics before installing it in an agent workflow
  • research
  • Coding agents 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 aiml-access-diagnostics

Install command safety

92

pass

standard package or runtime install path

  • npx skills add aws/tools-for-devops-agent --skill aiml-access-diagnostics

Trust score

62

warn

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

  • Manual review
  • 42 GitHub stars
  • Apache-2.0

Audit score

70

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

38

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

46

fail

secrets or environment access, filesystem or document 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 supporting files such as references/access-chain-model.md and a read-only data-collection allowlist, but those files are not present in the submitted file listing; the skill is incomplete as packaged.
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing

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.