AD vercel-react-best-practices-cn
来自 Vercel 工程团队的 React 和 Next.js 性能优化指南。在编写、审查或重构 React/Next.js 代码时使用此 Skill 以确保最佳性能模式。触发于涉及 React 组件、Next.js 页面、数据获取、包优化或性能改进的任务。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 71. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (vercel-react-best-practices-cn) differs from the folder (react-best-practices-cn)
- 100Tools and files. No external tools needed
- 100Steps. 73 steps
- 100Execution cost. Instruction body is 991 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 66)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: suspicious
This documentation-only React/Next.js skill does not run code, but it needs review because some examples could steer agents toward unsafe inline scripts, auth-state handling, cookie logging, or shared user caches.
LLM: suspicious (high) · VirusTotal: · 29 May 2026