Star200+

Pre-install eval

unslop 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
84
Eval report
81
Trust
89
Audit
77
Agent 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

70

warn

Task fit is weak; compare alternatives before selecting.

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

Install path

92

pass

Install handoff is available.

  • npx skills add cursor/plugins --skill unslop

Install command safety

92

pass

standard package or runtime install path

  • npx skills add cursor/plugins --skill unslop

Trust score

81

warn

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

  • Strong shortlist
  • 4.8K GitHub stars
  • Unknown

Audit score

89

warn

Needs review

  • License is unclear

Agent safety gate

77

warn

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

  • Require human approval before installing into a real workspace.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network 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
  • Repository license is unclear and requires review before redistribution.
  • License is unclear
  • Documentation summary is thin
  • License clarity: Unknown

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

66

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.