Pre-install eval

joinquant-skill 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.

FailedHigh riskBLOCK Policy
65
Eval report
65
Trust
72
Audit
44
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate joinquant-skill before installing it in an agent workflow
  • coding-agents
  • Finance and quant workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

65

warn

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

  • Manual review
  • 75 GitHub stars
  • NOASSERTION

Audit score

72

fail

Risky

  • Dependency or permission surface needs review

Agent safety gate

44

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

License clarity

86

pass

NOASSERTION

  • NOASSERTION

Permission surface

48

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Network access: medium
  • Filesystem 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
  • Repository license is NOASSERTION; no clear open-source license is specified.
  • Audit risk risky exceeds max_risk=medium
  • High-risk permission hints: Shell or command execution
  • Dependency or permission surface needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.