CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-performance

React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.

Quality

74%

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 ./skills/react-performance/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.

A well-organized, highly actionable reference catalog with executable code pairs and a useful priority scheme. Its main weaknesses are the absence of verification checkpoints in the review workflow, a monolithic single-file structure despite its size, and re-teaching of basic patterns Claude already knows.

Suggestions

Add a verification loop to the workflow: after applying a rule, re-measure the symptom (e.g., re-run Lighthouse or re-check bundle size) and revert if the metric did not improve, plus a 'profile first' checkpoint before applying re-render or JS micro-optimizations.

Split the 8 category sections into per-category reference files (e.g., references/waterfalls.md, references/bundle-size.md) and keep SKILL.md as the priority index plus activation guidance, so the full 575-line catalog is not loaded on every invocation.

Trim rules that restate knowledge Claude already has (Promise.all parallelism, passive scroll listeners, Set membership checks, caching arr.length) down to one-line checklist items, or move them to a low-priority reference file.

DimensionReasoningScore

Conciseness

The INCORRECT/CORRECT code-pair style is terse and lean, but a substantial share of the catalog restates patterns Claude already knows (Promise.all for parallelism, passive scroll listeners, Set vs Array.includes, caching arr.length) with explanatory asides ('the listener cannot preventDefault()', 'Each digit costs bytes'), matching anchor 3: mostly efficient but includes unnecessary explanation that could be trimmed.

3 / 5

Actionability

Nearly every rule ships an executable, copy-paste-ready TypeScript/TSX snippet in INCORRECT/CORRECT pairs, but a few are placeholder pseudocode rather than real APIs (createScrollHook() 'singleton subject under the hood') and some fragments lack surrounding context, placing it just below anchor 5.

4 / 5

Workflow Clarity

The Priority Index table and 'When to Activate' section give a clear review ordering, and no destructive operations apply so no cap is triggered, but there are no verification checkpoints (e.g., profile-first, Lighthouse/Core Web Vitals confirmation after applying a fix), matching anchor 3: sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the entire ~575-line rule catalog lives inline in SKILL.md. Internal structure is good (numbered sections, priority table, prefix scheme) and the Related section links out one level, but bulk content that would naturally split into per-category reference files stays inline, matching anchor 3 rather than the well-split anchor 4/5 structures.

3 / 5

Total

13

/

20

Passed

Description

83%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 what the skill covers and when to use it, with an explicit 'Use when...' clause and concrete category names. It could be sharpened by converting category labels into action verbs and adding natural user phrasings like 'slow', 'page speed', or 'web vitals'.

DimensionReasoningScore

Specificity

The description names the domain (React/Next.js performance) and lists several concrete coverage areas ('waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced'), but frames them as rule categories ('Organizes 70+ rules') rather than concrete actions like the anchor-5 examples, so it sits between anchors 4 and 5.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('Organizes 70+ rules across 8 priority categories...') and a concrete 'Use when writing, reviewing, or refactoring React/Next.js code for performance' trigger clause, matching the anchor-5 example's structure of explicit what + explicit when with trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say — 'React', 'Next.js', 'performance', 'refactoring', 'code' review — but common variations like 'slow', 'page speed', 'Lighthouse', or 'web vitals' are absent, matching anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym list.

4 / 5

Distinctiveness Conflict Risk

The performance niche is clear, but the broad triggers ('writing, reviewing, or refactoring React/Next.js code') create minor overlap risk with closely related sibling React skills (e.g., react-patterns, react-testing referenced in the body); this fits anchor 4 ('mostly distinct; minor overlap risk') better than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (576 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 6 suspicious

Warning

Total

13

/

16

Passed

Repository

affaan-m/ECC

Path

skills/react-performance/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.