CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.15x
Quality

74%

Does it follow best practices?

Impact

96%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/cloud-profile/skills/vercel-react-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 an efficient, well-organized catalog of 70 rules with concrete API-level one-liners, but it functions purely as an index: all executable detail is deferred to rule files that are not present in the bundle, and there is no explicit workflow for applying the rules. It needs either inlined key examples or shipped, verified reference files to be fully usable.

Suggestions

Inline one or two short code examples for the highest-priority rules (e.g., async-parallel, bundle-barrel-imports) so the quick reference is actionable even without the rule files.

Add an explicit application workflow, e.g., 'When reviewing code: 1) match the task to a category by priority, 2) locate the rule by prefix, 3) read rules/<prefix>-<name>.md before refactoring.'

Ship the referenced bundle files (rules/*.md and AGENTS.md) or fix the references — the body's core navigation ('Read individual rule files', 'For the complete guide with all rules expanded: AGENTS.md') currently points at files that do not exist in the bundle.

DimensionReasoningScore

Conciseness

The body is a lean index — 70 one-line rule summaries like "Use Promise.all() for independent operations" with no explanations of concepts Claude already knows. Minor duplication (the priority table repeats category/impact/prefix info already shown in section headers, and 'When to Apply' restates the frontmatter description) keeps it just below anchor 5's "every token earns its place".

4 / 5

Actionability

One-liners name concrete APIs ("Use React.cache() for per-request deduplication", "Use next/dynamic for heavy components"), but many rules are too terse to apply ("Use better-all for partial dependencies") and all code examples are deferred to rules/*.md files. This matches anchor 3 ("Some concrete guidance but incomplete... missing key details") rather than anchor 4's "mostly executable guidance".

3 / 5

Workflow Clarity

The navigation flow (priority table → category quick reference → rule file) is implied but never given as an explicit sequence; "How to Use" only says "Read individual rule files for detailed explanations" with no steps for applying rules during writing vs. reviewing vs. refactoring. Anchor 3 fits: structure present but the usage sequence remains implicit.

3 / 5

Progressive Disclosure

The body is structured as an index with clearly signaled one-level-deep references ("rules/async-parallel.md", "AGENTS.md"), but none of the referenced files exist in the provided bundle — there is no rules/ directory, references/, or AGENTS.md, so the disclosure chain dead-ends. Good signaling and structure, but unverifiable/broken references keep it at anchor 3 rather than anchor 4.

3 / 5

Total

13

/

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 that clearly answers both what the skill is and when to use it, with explicit trigger phrases and proper third-person voice. Its main weakness is specificity: it describes the skill as generic "guidelines" without naming the concrete capability areas it covers.

Suggestions

Replace the generic phrase 'performance optimization guidelines' with concrete capability areas, e.g., 'Eliminates request waterfalls, reduces bundle size, and prevents unnecessary re-renders in React/Next.js code.'

Add common user phrasings such as 'bundle size', 'slow rendering', or 'app speed' to the trigger list for broader natural-term coverage.

DimensionReasoningScore

Specificity

"React and Next.js performance optimization guidelines" names the domain and "writing, reviewing, or refactoring React/Next.js code" gives 1-2 concrete application actions, but the description never enumerates specific capabilities (e.g., eliminating waterfalls, reducing bundle size, preventing re-renders). This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") rather than anchor 4, which requires several specific listed actions.

3 / 5

Completeness

"React and Next.js performance optimization guidelines from Vercel Engineering" explicitly states what the skill is, and "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" explicitly states when with concrete trigger phrases. Clear anchor 5 match; anchor 4's weaker 'when' doesn't apply since triggers are enumerated.

5 / 5

Trigger Term Quality

"React components, Next.js pages, data fetching, bundle optimization, or performance improvements" plus "writing, reviewing, or refactoring" gives good natural keyword coverage a user would actually say. A few common phrasings ("bundle size", "slow", "re-renders", "speed up") are missing, so it falls just short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The React/Next.js performance niche is mostly distinct, but broad trigger phrases like "React components" and "data fetching" create minor overlap risk with general React development or data-fetching skills. Anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") fits better than anchor 5's "minimal conflict risk".

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

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/vercel-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.