Star0

Pre-install eval

Urik 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
81
Trust
86
Audit
70
Safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Urik before installing it in an agent workflow
  • legal-compliance
  • Sports analytics workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add urikdev/Urik

Install command safety

92

pass

standard package or runtime install path

  • npx skills add urikdev/Urik

Trust score

81

warn

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

  • Strong shortlist
  • 385 GitHub stars
  • GPL-3.0

Audit score

86

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

70

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • Permission surface may require sandboxing

License clarity

86

pass

GPL-3.0

  • GPL-3.0

Permission surface

60

warn

secrets or environment access, 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • Permission surface may require sandboxing
  • Quality score needs review
  • Permission surface needs review: secrets or environment access, filesystem or document access

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

7d since push

Alternatives available

pass

82

Alternative skills are available for comparison.