Star200+

Pre-install eval

PROJ Option Pricing Matlab 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
75
Trust
67
Audit
51
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate PROJ Option Pricing Matlab before installing it in an agent workflow
  • finance
  • RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add jkirkby3/PROJ_Option_Pricing_Matlab

Install command safety

92

pass

standard package or runtime install path

  • npx skills add jkirkby3/PROJ_Option_Pricing_Matlab

Trust score

75

warn

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

  • Strong shortlist
  • 207 GitHub stars
  • MIT

Audit score

67

fail

Risky

  • Repository appears stale

Agent safety gate

51

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

MIT

  • MIT

Permission surface

86

pass

filesystem or document access

  • 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 require actively maintained dependencies
  • production agents without a repository review
  • Repository looks stale
  • Audit risk risky exceeds max_risk=medium
  • Repository appears stale
  • Financial research output is not financial advice; require human review before any live investment decision

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

fail

38

2y since push

Alternatives available

pass

82

Alternative skills are available for comparison.