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.

1.02x

Quality

73%

Does it follow best practices?

Impact

98%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 well-organized, concise index of performance rules with clear priority structure, but it lacks executable examples in SKILL.md and the referenced detail files (rules/, AGENTS.md) do not exist, weakening both actionability and progressive disclosure.

Suggestions

Include the referenced bundle files (rules/*.md and AGENTS.md) so the progressive-disclosure path resolves, or remove the dangling references.

Add a few inline executable code snippets for the highest-priority CRITICAL rules (e.g. async-parallel, bundle-barrel-imports) so the body is actionable without requiring the missing rule files.

Consider showing just the top-priority rules inline and summarizing the lower-priority categories, reducing the 69-rule enumeration while keeping navigation clear.

Dimension	Reasoning	Score
Conciseness	A lean index of 69 rule identifiers with terse one-line summaries and no concept re-explanation; efficient though the full enumeration of all rules adds some bulk.	4 / 5
Actionability	Provides concrete directive-style guidance ('Use Promise.all() for independent operations', 'Import directly, avoid barrel files') but no executable code or commands in the body, and the referenced detail files are missing.	3 / 5
Workflow Clarity	Organized by priority with a clear 'When to Apply' and a single unambiguous reference action (look up the rule category, then read the rule file); not a destructive/batch workflow so no validation cap applies.	4 / 5
Progressive Disclosure	Sections and signaled references to rules/*.md and AGENTS.md exist, but those bundle files are not present in the skill directory, so the one-level-deep disclosure path is broken.	3 / 5
	Total	14 / 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 clearly states both what the skill does and when to use it, with concrete trigger terms and third-person voice. It is specific and distinctive, with only minor gaps in action and keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the React/Next.js performance domain plus several concrete actions ('writing, reviewing, or refactoring', 'bundle optimization', 'data fetching'), with minor gaps versus fully comprehensive enumeration.	4 / 5
Completeness	Explicitly answers both what ('React and Next.js performance optimization guidelines from Vercel Engineering') and when ('This skill should be used when… Triggers on tasks involving…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('React components', 'Next.js pages', 'data fetching', 'bundle optimization', 'performance improvements') with good coverage, though a few synonyms (SSR/RSC, rendering) are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Vercel React/Next.js performance optimization) with distinct triggers; minor overlap risk with general React or generic performance skills.	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: udecode/plate
Path: .agents/skills/vercel-react-best-practices/SKILL.md
Commit: d76efae

Reviewed: 3 days 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.