Star0

Pre-install eval

Sql.Js 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
84
Eval
85
Trust
87
Audit
67
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

84

pass

Task wording matches this skill metadata.

  • Evaluate Sql.Js before installing it in an agent workflow
  • data-analysis
  • Database and SQL workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add sql-js/sql.js

Install command safety

92

pass

standard package or runtime install path

  • npx skills add sql-js/sql.js

Trust score

85

pass

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

  • Strong shortlist
  • 14K GitHub stars
  • Unknown

Audit score

87

pass

Safe to try

  • License is unclear

Agent safety gate

67

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

74

warn

filesystem or document access, database access

  • Network access: medium
  • Filesystem access: medium
  • Database 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
  • License is unclear
  • License clarity: Unknown
  • Production credentials, payments, or irreversible account changes without explicit human review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

74

Public metadata needs stronger README/SKILL.md context

Recent maintenance

warn

76

4mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.