Pre-install eval

nature-statistics 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
82
Eval report
80
Trust
86
Audit
70
Agent safety

manual review

Review the audit page, then allow agent install in a sandboxed workflow.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate nature-statistics before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add Yuan1z0825/nature-skills --skill nature-statistics

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Yuan1z0825/nature-skills --skill nature-statistics

Trust score

80

warn

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

  • Strong shortlist
  • 39K GitHub stars
  • Apache-2.0

Audit score

86

pass

Safe to try

  • The SKILL.md excerpt is truncated in the provided documentation, but the visible content is coherent and complete enough for review.

Agent safety gate

70

warn

Good audit and safety signals with no high-risk permission hints in public metadata.

  • Review the audit page, then allow agent install in a sandboxed workflow.
  • Safe-to-try audit

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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 need a vendor-supported SLA
  • production agents without a repository review
  • The SKILL.md excerpt is truncated in the provided documentation, but the visible content is coherent and complete enough for review.
  • The output format template contains an incomplete sentence ('Reviewer-risk note - What a statistical reviewer may stil') which could confuse users.
  • 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

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.