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.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, token-efficient reference catalog with sound progressive disclosure. Its weaknesses are the absence of executable examples or an explicit workflow in the body, with the actionable detail deferred to rule files that are not present in the bundle.

Suggestions

Include at least one short, executable code example in the body (e.g., a Promise.all() before/after for async-parallel) so the skill is actionable without opening a rule file.

Add a brief numbered workflow for applying a rule (identify category by prefix -> read the rule file -> apply the correct pattern -> verify the change), with a validation checkpoint before committing.

Bundle the referenced rules/*.md and AGENTS.md files, or note that they are external, so the signaled progressive-disclosure references actually resolve.

DimensionReasoningScore

Conciseness

The body is a dense catalog of 57 rules with one-line descriptions and a priority table; it re-explains no concepts Claude already knows and avoids padding, so every token earns its place.

3 / 3

Actionability

It provides concrete rule names, prefixes, and file paths, but the body itself contains no executable code or worked examples — the actionable detail is deferred to the unbundled rule files, so guidance is incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

'When to Apply' and 'How to Use' give usage guidance and a loose read-the-rule-file sequence, but there is no explicit numbered workflow or validation checkpoint, leaving the sequence implicit.

2 / 3

Progressive Disclosure

It offers a clean overview (priority table + categorized quick reference) with one-level-deep, clearly signaled references (rules/*.md and AGENTS.md), making navigation easy; the referenced files are not bundled, but the structure itself is well organized.

3 / 3

Total

10

/

12

Passed

Description

90%

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, third-person description that clearly states both capability and triggers with natural keywords. The only weakness is that the listed actions are generic verbs rather than sharply distinct capabilities.

DimensionReasoningScore

Specificity

It names the domain and several actions ('writing, reviewing, or refactoring React/Next.js code'), but the verbs are generic dev activities rather than distinct concrete capabilities, so it does not reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It explicitly states what ('React and Next.js performance optimization guidelines') and when ('This skill should be used when... Triggers on tasks involving...'), satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

'React components, Next.js pages, data fetching, bundle optimization, or performance improvements' are natural terms a user would say, with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (React/Next.js performance) 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
gsd-build/gsd-2
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.