Star0

Pre-install eval

Spring Analysis 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
74
Eval
80
Trust
72
Audit
56
Safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Spring Analysis before installing it in an agent workflow
  • productivity-automation
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add seaswalker/spring-analysis

Install command safety

92

pass

standard package or runtime install path

  • npx skills add seaswalker/spring-analysis

Trust score

80

warn

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

  • Strong shortlist
  • 14K GitHub stars
  • Unknown

Audit score

72

warn

Needs review

  • License is unclear

Agent safety gate

56

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

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
  • License is unclear
  • Repository appears stale
  • Documentation summary is thin

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

74

Public metadata needs stronger README/SKILL.md context

Recent maintenance

fail

22

3y since push

Alternatives available

pass

82

Alternative skills are available for comparison.