Star0

Pre-install eval

Browser Use 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
88
Eval
92
Trust
94
Audit
78
Safety

manual review

Review the audit page, then allow agent install in a sandboxed workflow.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate Browser Use before installing it in an agent workflow
  • web-automation
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add browser-use/browser-use

Install command safety

92

pass

standard package or runtime install path

  • npx skills add browser-use/browser-use

Trust score

92

pass

Strong OpenAgentSkill Trust Score across adoption, recent maintenance, license clarity, documentation, dependency/runtime risk, install safety, permission surface, and install availability.

  • Production candidate
  • 97K GitHub stars
  • MIT

Audit score

94

pass

Safe to try

  • Documentation summary is thin

Agent safety gate

78

warn

Good audit and safety signals with no high-risk permission hints in public metadata.

  • Review the audit page, then allow agent install in a sandboxed workflow.
  • Safe-to-try audit

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

network or browser access

  • Browser automation: medium
  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • Documentation summary is thin
  • README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

fail

50

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.