OpenAgentSkill
GitHub200+

Pre-install eval

snapshots 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
62
Eval report
65
Trust
70
Audit
46
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate snapshots 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 Aicoo-Team/AICOO-Skills --skill snapshots

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Aicoo-Team/AICOO-Skills --skill snapshots

Trust score

65

warn

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

  • Manual review
  • 35 GitHub stars
  • MIT

Audit score

70

warn

Needs review

  • Inconsistent base URL variable: $PULSE_BASE is used in some examples but not defined; should be replaced with the actual base URL or defined consistently.

Agent safety gate

46

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: Shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

62

warn

shell or command execution, network or browser access

  • Shell or command execution: high
  • 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
  • Inconsistent base URL variable: $PULSE_BASE is used in some examples but not defined; should be replaced with the actual base URL or defined consistently.
  • High-risk permission hints: Shell or command execution
  • No mention of error handling, rate limits, or API response validation in the skill documentation.

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

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.