CF react-performance
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).…
As a process F 33/100 · No process to follow — References files that are not bundled: ../react-patterns/SKILL.md, ../react-testing/SKILL.md, ../frontend-patterns/SKILL.md
The same skill appears in 3 more places: RA-Skills, RA-Skills, everything-claude-code
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../react-patterns/SKILL.md - warning
missing-refreference to a missing file: ../react-testing/SKILL.md - warning
missing-refreference to a missing file: ../frontend-patterns/SKILL.md - warning
missing-refreference to a missing file: ../accessibility/SKILL.md - warning
missing-refreference to a missing file: ../nextjs-turbopack/SKILL.md - warning
missing-refreference to a missing file: ../../rules/react/ - note
edit-residuethe text marks something as outdated (lines 556): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 33/100
- 0Tools and files. 6 referenced file(s) missing: ../react-patterns/SKILL.md, ../react-testing/SKILL.md, ../frontend-patterns/SKILL.md
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 70Execution cost. Instruction body is 4401 tokens
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 386: enough signal without eating the budget
- +4Structure: 70 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (35 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.