CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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/react-best-practices/skills/react-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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, prioritized one-line-per-rule index that respects token budget, and it doubles as a useful cheat sheet. However, its progressive-disclosure contract is broken: it points exclusively to rule files and a compiled AGENTS.md that are absent from the bundle, and it never explains the rules/ path layout, so the 'How to Use' instruction cannot actually be followed.

Suggestions

Ship the referenced files (rules/*.md including _sections.md, and AGENTS.md) in the bundle, or remove/correct the references — currently every path in 'How to Use' and 'Full Compiled Document' is broken.

State the path pattern for rule files (e.g., 'rules/<prefix>-<rule-name>.md') and how to map a task to a category, instead of listing only three example paths.

Drop the duplicated impact labels (CRITICAL/HIGH/MEDIUM appear in both the priority table and the section headers) to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is a lean index — 57 rules as one-line name-plus-summary entries with no padding or explanations of concepts Claude already knows. Minor trimming is possible: impact labels (CRITICAL/HIGH) appear redundantly in both the priority table and the section headers, and the full 57-rule catalog could arguably live in a reference file. That matches anchor 4 (efficient, minor instances that could be trimmed) rather than anchor 5.

4 / 5

Actionability

Each rule line is concrete advice ('Use Promise.all() for independent operations'), but the body itself contains no executable code and its key instruction — 'Read individual rule files' — omits how to locate the file for a given rule: the path layout of rules/ is never stated, and only three arbitrary example paths are shown. This is anchor 3 (some concrete guidance but incomplete, missing key details), not anchor 4.

3 / 5

Workflow Clarity

'When to Apply' and the priority-ordered categories imply a lookup workflow (identify category, read the rule, apply it), but the sequence is never spelled out and the task-to-rule-file mapping is implicit. As a reference/lookup skill with no destructive or batch operations there is no validation cap, but the implicit lookup steps fit anchor 3 (steps present but with gaps) better than the clear, checkpointed sequence of anchor 4.

3 / 5

Progressive Disclosure

Scored against the actual bundle: every referenced path — rules/async-parallel.md, rules/bundle-barrel-imports.md, rules/_sections.md, and AGENTS.md — does not exist in the bundle (no rules/ directory, no AGENTS.md, no references/, scripts/, or assets/). The index itself is well organized, but navigation beyond it is impossible because all references are broken, and the full 57-rule catalog is inlined in SKILL.md. This fits anchor 2 (minimal effective structure; references effectively dead) better than anchor 3, where references at least resolve.

2 / 5

Total

12

/

20

Passed

Description

78%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 well-constructed description with an explicit and concrete 'when/trigger' clause in appropriate third-person voice. Its main weakness is a generic 'what' — it promises 'performance optimization guidelines' without naming any specific capabilities, which limits specificity and slightly blurs distinctiveness on the broadest trigger terms.

DimensionReasoningScore

Specificity

The description names the domain ('React and Next.js performance optimization guidelines') but the capability statement stays generic — 'guidelines ... to ensure optimal performance patterns' — without listing any concrete actions (e.g., eliminating waterfalls, bundle-size optimization, re-render tuning). It matches anchor 3 (domain plus minimal/generic actions) better than anchor 4, which expects several specific actions listed.

3 / 5

Completeness

It explicitly answers both: what ('React and Next.js performance optimization guidelines from Vercel Engineering') and when ('This skill should be used when writing, reviewing, or refactoring React/Next.js code ... Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements'). The 'when' clause has concrete trigger phrases, matching anchor 5; the what is present and clear, so it is not the anchor-4 case of a weakly specified 'when'.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'React components', 'Next.js pages', 'data fetching', 'bundle optimization', 'performance improvements', plus 'writing, reviewing, or refactoring React/Next.js code'. A few natural terms users would say are missing (e.g., 'bundle size', 'slow renders', 'hydration'), so it falls just under the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

The React/Next.js performance niche is mostly distinct with clear triggers, but 'data fetching' and 'performance improvements' are broad enough to overlap with general data-fetching or profiling skills. This is exactly the anchor-4 case (mostly distinct, minor overlap risk) rather than anchor 5 (clear niche with minimal conflict).

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/react-best-practices/skills/react-best-practices/SKILL.md

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.