Star0

Pre-install eval

Sqlmc 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
77
Eval
78
Trust
82
Audit
62
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

94

pass

Task wording matches this skill metadata.

  • Evaluate Sqlmc before installing it in an agent workflow
  • data-analysis
  • Coding agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add malvads/sqlmc

Install command safety

92

pass

standard package or runtime install path

  • npx skills add malvads/sqlmc

Trust score

78

warn

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

  • Strong shortlist
  • 378 GitHub stars
  • AGPL-3.0

Audit score

82

pass

Safe to try

  • Quality score needs review

Agent safety gate

62

warn

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

  • Require human approval before installing into a real workspace.
  • Quality score needs review

License clarity

86

pass

AGPL-3.0

  • AGPL-3.0

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
  • Quality score needs review
  • Production credentials, payments, or irreversible account changes without explicit human review
  • Sensitive private data before reviewing repository code, license, and permission surface

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

74

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.