Star200+

Pre-install eval

vercel-react-best-practices 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
79
Eval report
77
Trust
87
Audit
55
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate vercel-react-best-practices before installing it in an agent workflow
  • design-creative
  • GitHub automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add CherryHQ/cherry-studio --skill vercel-react-best-practices

Install command safety

92

pass

standard package or runtime install path

  • npx skills add CherryHQ/cherry-studio --skill vercel-react-best-practices

Trust score

77

warn

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

  • Strong shortlist
  • 51K GitHub stars
  • MIT

Audit score

87

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

MIT

  • MIT

Permission surface

60

warn

filesystem or document access, network or browser 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
  • SKILL.md only provides a high-level quick reference with rule names and categories, lacking the detailed explanations, code examples, and workflow steps needed for an agent to correctly apply the guidelines. It is effectively a summary rather than a self-contained skill.
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing
  • Inconsistency in rule count: the description in SKILL.md states 'Contains 62 rules' while AGENTS.md and README mention '40+ rules'. This discrepancy undermines clarity.

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.