vercel-react-best-practices Eval
================================

Status: review
Score: 79/100
Risk: medium
Decision: manual_review
Policy: review
Reason: Test manually in an isolated workspace and compare against safer alternatives.

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

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- WARN Trust score: Good trust signals with a few areas worth checking before rollout.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- WARN Permission surface: filesystem or document access, network or browser access

Warnings:
- Trust score: Good trust signals with a few areas worth checking before rollout.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Permission surface: filesystem or document access, network or browser access
- High-risk permission hints: Secrets or environment access
- Permission surface may require sandboxing
- 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.
- 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.
- SKILL.md appears truncated in the provided excerpt (ends mid-sentence), suggesting the file may be incomplete or malformed as the primary skill entry.
- Permission surface needs review: filesystem or document access, network or browser access

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- 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.
- SKILL.md appears truncated in the provided excerpt (ends mid-sentence), suggesting the file may be incomplete or malformed as the primary skill entry.
- Permission surface needs review: filesystem or document access, network or browser access

URLs:
- Skill: https://www.openagentskill.com/skills/cherryhq-vercel-react-best-practices
- Audit: https://www.openagentskill.com/skills/cherryhq-vercel-react-best-practices/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=cherryhq-vercel-react-best-practices