vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/vercel-react-best-practices/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clean, well-organized rule index that respects token budget, but it defers all executable detail to rule files that are not actually present in the bundle, weakening actionability and navigation. Adding the referenced files or inlining minimal code examples would lift the weaker dimensions.

Suggestions

Ship the referenced bundle (rules/*.md per rule and AGENTS.md) so the deferred code examples and detailed guidance actually resolve, or remove the dangling references.

Inline at least one short executable code snippet per critical category (e.g., async-parallel, bundle-barrel-imports) so the skill is actionable without external files.

Add a brief explicit workflow for applying the rules during review/refactoring (identify category -> match rule -> verify fix), with a validation checkpoint for refactors.

Dimension	Reasoning	Score
Conciseness	The body is a lean catalog of rule names with one-line descriptions and a priority table, assuming Claude knows the underlying concepts; it is not a 5 because the full 57-rule index is inlined rather than deferred, which is slightly more than the overview needs.	4 / 5
Actionability	Rules are named with brief one-line hints (e.g., "Use Promise.all() for independent operations") but no executable code examples, and the promised rule files containing examples do not exist in the bundle; concrete guidance is present but incomplete.	3 / 5
Workflow Clarity	"How to Use" sketches a loose consult-the-catalog flow but there is no sequenced workflow or checkpoint; acceptable for a reference skill, yet the guidance is implicit rather than enumerated.	3 / 5
Progressive Disclosure	Structure (categories, priority table, quick reference) is reasonable, but the body inlines the entire rule list and points to referenced files (rules/*.md, AGENTS.md) that are absent from the bundle, leaving navigation promised but undelivered.	3 / 5
	Total	13 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-formed: it states a clear purpose, uses third-person voice, and provides explicit trigger guidance with natural keywords. It is strong on completeness and only slightly less comprehensive on trigger synonyms and action specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("React and Next.js performance optimization guidelines") and several concrete actions ("writing, reviewing, or refactoring React/Next.js code"), with minor gaps in coverage; not a 5 because the actions are generic dev verbs rather than a comprehensive enumeration of perf operations.	4 / 5
Completeness	Clearly states what it does ("performance optimization guidelines") and explicitly answers when with concrete trigger phrases ("This skill should be used when..." and "Triggers on tasks involving..."), matching the anchor for explicit what-and-when.	5 / 5
Trigger Term Quality	Natural developer terms are present ("React components", "Next.js pages", "data fetching", "bundle optimization", "performance improvements"); a few common synonyms are missing (e.g., re-renders, Core Web Vitals), keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The React/Next.js performance niche with specific triggers is mostly distinct; minor overlap risk remains with broader web-performance skills, so it sits just below the clear-niche anchor.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Draculabo/AntigravityManager
Path: .agent/skills/vercel-react-best-practices/SKILL.md
Commit: e29cfdc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.