Pre-install eval

Baoyu Design 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
79
Eval report
80
Trust
86
Audit
42
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Baoyu Design before installing it in an agent workflow
  • agent-skills
  • Web scraping workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

80

warn

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

  • Strong shortlist
  • 3.8K GitHub stars
  • MIT

Audit score

86

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

42

warn

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

  • The tracked source changed or could not be synchronized. Review the current source before installing.

License clarity

86

pass

MIT

  • MIT

Permission surface

22

fail

secrets or environment access, shell or command execution

  • Shell or command execution: high
  • Browser automation: medium
  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Shell or command execution, Secrets or environment access
  • Dependency or permission surface needs review
  • The tracked source changed or could not be synchronized. Review the current source before installing.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

warn

76

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.