CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/build-web-apps/skills/react-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 rule catalog with clear priority ordering and progressive-disclosure intent, but it lacks in-skill executable guidance and its referenced bundle files (rules/, AGENTS.md) are missing from the actual bundle.

Suggestions

Ship the referenced bundle files (rules/async-parallel.md, rules/bundle-barrel-imports.md, and AGENTS.md) so the progressive-disclosure references resolve to real content.

Add one or two short, concrete code examples in SKILL.md for the highest-impact (CRITICAL) rules so the skill is directly actionable without opening rule files.

Use markdown links (e.g. [rules/async-parallel.md](rules/async-parallel.md)) instead of plain code-block paths so navigation to rule files is signaled and clickable.

DimensionReasoningScore

Conciseness

Lean and efficient index of rule prefixes with terse one-line descriptions; assumes Claude's competence and contains no padded concept explanations or unnecessary verbosity.

5 / 5

Actionability

Provides a catalog of named rules with brief summaries but no concrete code, commands, or examples in SKILL.md itself — actionable detail is deferred to rule files rather than being directly executable here.

3 / 5

Workflow Clarity

The priority-ordered category table and 'When to Apply' / 'How to Use' sections give a clear structure for selecting and reading rules, though it is a reference catalog rather than a sequenced multi-step workflow.

4 / 5

Progressive Disclosure

Structure design is good — an overview pointing one level deep to rules/*.md and AGENTS.md — but those referenced bundle files do not actually exist in the bundle, so the navigation references are broken.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description that clearly states its purpose and provides explicit, natural trigger guidance covering the main React/Next.js performance scenarios. It distinguishes itself well from generic skills via the specific framework and task list.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete activities (writing, reviewing, refactoring React/Next.js code) alongside specific trigger areas, though the actions are framed as activities rather than concrete operations.

4 / 5

Completeness

Explicitly answers both 'what' (React/Next.js performance optimization guidelines from Vercel) and 'when' ('should be used when writing, reviewing, or refactoring', 'Triggers on...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural, user-spoken terms like 'React components, Next.js pages, data fetching, bundle optimization, performance improvements' with good coverage, missing only a few synonyms or file extensions.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (React/Next.js performance from Vercel Engineering) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.