Star0

Pre-install eval

OpenBB 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
86
Eval
83
Trust
90
Audit
78
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate OpenBB before installing it in an agent workflow
  • Finance
  • Research agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add OpenBB-finance/OpenBB

Install command safety

92

pass

standard package or runtime install path

  • npx skills add OpenBB-finance/OpenBB

Trust score

83

pass

Good trust signals with a few areas worth checking before rollout.

  • Strong shortlist
  • 46K GitHub stars
  • Unknown

Audit score

90

warn

Needs review

  • License is unclear

Agent safety gate

78

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

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
  • high-compliance environments without internal security review
  • No OpenAgentSkill engagement data yet
  • License is unclear
  • Documentation summary is thin
  • License clarity: Unknown

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

19d since push

Alternatives available

info

55

No close alternatives were found in the current shortlist.