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.

65

Quality

77%

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

65%Weight 40%Scale 1-3

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

The content is a well-organized, token-efficient rule index, but it stops short of executable guidance and references detail files (rules/*.md, AGENTS.md) that are not present in the bundle, weakening both actionability and progressive disclosure.

Suggestions

Ship the referenced `rules/<rule>.md` files and `AGENTS.md` in the bundle so the one-level-deep references actually resolve, or inline a few representative code examples in the body.

Replace the vague "Read individual rule files" instruction with a concrete navigation step, e.g. naming the highest-priority file to consult first for a given task type.

For the most critical (CRITICAL-priority) rules, include a short executable correct-code snippet directly in the body so Claude can act without an external file lookup.

DimensionReasoningScore

Conciseness

The body is a lean one-line-per-rule index organized into tables and lists, assuming Claude's React knowledge and avoiding padded explanation of basic concepts.

3 / 3

Actionability

Each rule gives an actionable one-line directive (e.g., "Use Promise.all() for independent operations"), but the body contains no executable code examples, deferring them to rule files that are referenced but not present.

2 / 3

Workflow Clarity

This is a reference catalog rather than a multi-step workflow; the "How to Use" section only vaguely says to "Read individual rule files" with no sequencing or checkpoints, though the priority-ordered categories provide some structure.

2 / 3

Progressive Disclosure

The body is conceptually an overview pointing one level deep to `rules/*.md` and `AGENTS.md`, but those referenced files do not exist in the bundle, and all 64 rules are inlined rather than being split into separate files.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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-constructed with explicit triggers, natural keywords, and a clear niche. Its only weakness is that the named actions are somewhat high-level rather than concrete operations.

DimensionReasoningScore

Specificity

It names the domain and several actions ("writing, reviewing, or refactoring React/Next.js code", "data fetching", "bundle optimization"), but these are high-level verbs rather than multiple concrete operations comparable to the PDF anchor's "extract text, fill forms, merge documents."

2 / 3

Completeness

It explicitly states what the skill provides ("performance optimization guidelines") and when to use it ("This skill should be used when..." and "Triggers on..."), covering both what and when.

3 / 3

Trigger Term Quality

Natural terms a user would actually say appear throughout: "React components", "Next.js pages", "data fetching", "bundle optimization", and "performance improvements".

3 / 3

Distinctiveness Conflict Risk

The React/Next.js performance niche is clearly scoped with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.