Star200+

Pre-install eval

dating-web 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
81
Eval report
80
Trust
88
Audit
60
Agent 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

84

pass

Task wording matches this skill metadata.

  • Evaluate dating-web before installing it in an agent workflow
  • design-creative
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add nexu-io/open-design --skill dating-web

Install command safety

92

pass

standard package or runtime install path

  • npx skills add nexu-io/open-design --skill dating-web

Trust score

80

warn

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

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

Audit score

88

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

60

warn

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

  • Require human approval before installing into a real workspace.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

Apache-2.0

  • Apache-2.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
  • production agents without a repository review
  • The skill references an external 'active DESIGN.md' that is not included in the repository, which may cause ambiguity if the skill is used outside the intended context.
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing
  • Permission surface needs review: secrets or environment access, filesystem or document access

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.