Star0

Pre-install eval

Football.Json 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
77
Eval
78
Trust
83
Audit
55
Safety

do not auto install

Permission surface: secrets or environment access, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Football.Json before installing it in an agent workflow
  • sports-analytics
  • Sports analytics workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add openfootball/football.json

Install command safety

92

pass

standard package or runtime install path

  • npx skills add openfootball/football.json

Trust score

78

warn

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

  • Strong shortlist
  • 958 GitHub stars
  • CC0-1.0

Audit score

83

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

55

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

CC0-1.0

  • CC0-1.0

Permission surface

46

fail

secrets or environment access, filesystem or document access

  • Network access: medium
  • Filesystem access: medium
  • Secrets or environment access: high

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
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

1mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.