CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-best-practices

React/Next.js performance best practices from Vercel. Use when writing, reviewing, or refactoring React/Next.js code for performance, data fetching, or bundle size.

Quality

71%

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 ./.agents/skills/04-develop/00-frontend-general/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.

A well-organized, token-efficient rule index with a sensible priority system, but it functions only as a table of contents: all executable detail is delegated to rules/ files that are missing from the bundle, leaving the body without a single code example or an explicit application workflow. Fixing the dangling references is the highest-impact improvement.

Suggestions

Include the actual rules/*.md files referenced in 'How to Use' (or a references/ bundle) — the directory does not exist in the bundle, so every detailed reference dangles and the skill's core content is unavailable.

Add a minimal executable example for at least the two CRITICAL categories (e.g., a Promise.all before/after and a direct-import vs barrel-file snippet) so the body offers actionable guidance without the missing files.

State an explicit application workflow, e.g. 'When reviewing: scan for async- waterfalls first, then bundle-, then server- rules; consult the rule file before refactoring', to turn the priority table into a usable sequence.

DimensionReasoningScore

Conciseness

The body is a tight index: 57 one-line rule entries, a priority table, and a short usage section, with no explanations of concepts Claude already knows and no padded prose. This fits anchor 4 (efficient, minor trimming possible) — the 'When to Apply' section and the intro paragraph substantially duplicate the frontmatter description, and a few rule one-liners state the obvious. It is not anchor 5 because of that redundancy, and far from anchor 3, which requires unnecessary explanation.

4 / 5

Actionability

Entries give specific API-level directives ("Use Promise.all() for independent operations", "Import directly, avoid barrel files", "Use toSorted() for immutability"), which is concrete guidance, but the body contains no code examples or commands and defers all executable detail to rules/*.md files — which are absent from the bundle, so the detailed guidance is unreachable. This matches anchor 3 (concrete but incomplete, key details missing) rather than anchor 4, which requires concrete code or commands with only minor gaps.

3 / 5

Workflow Clarity

There is no explicit multi-step process: the priority table (CRITICAL → LOW) implies a triage order and 'How to Use' says to read individual rule files, but no sequenced workflow for applying the rules during writing vs. reviewing, and no checkpoints. This fits anchor 3 (rough sequence implicit, checkpoints missing) — the simple-skill exception does not apply since the body is ~133 lines with an implied but unstated lookup process, and no destructive/batch cap is relevant.

3 / 5

Progressive Disclosure

The in-file structure is good — clear sections, a priority table, and a clearly signaled 'How to Use' pointing one level deep to rules/async-parallel.md and rules/bundle-barrel-imports.md — but scored against the actual bundle, those referenced files (and the whole rules/ directory) do not exist, so the disclosure chain the skill is built around is broken. This lands at anchor 3 (structure present but organization incomplete) rather than anchor 4, which assumes the referenced material is actually reachable.

3 / 5

Total

13

/

20

Passed

Description

70%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-formed description with an explicit and well-scoped 'Use when' clause, good natural trigger terms, and a clear niche. Its main weakness is that 'what the skill does' rests on the generic phrase 'performance best practices' rather than naming concrete capabilities. Third-person voice is used correctly.

Suggestions

Replace the generic 'provides best practices' framing with 2-3 concrete capabilities, e.g. 'Eliminates request waterfalls, reduces bundle size via direct imports, and optimizes re-renders in React/Next.js apps.'

Add a few natural trigger synonyms users actually say — 'slow renders', 'load time', 'speed up my React app' — to strengthen trigger coverage toward comprehensive.

DimensionReasoningScore

Specificity

The description names the domain clearly ("React/Next.js performance best practices from Vercel") and scopes it to "performance, data fetching, or bundle size", but the only action it attributes to the skill is the generic 'provides best practices' — no concrete capabilities like 'eliminates request waterfalls' or 'reduces barrel-file imports'. This matches anchor 3 (names domain with 1-2 concrete points) better than anchor 2, since the three focus areas add substance beyond a bare domain label, but it falls short of anchor 4, which requires several specific actions the skill performs.

3 / 5

Completeness

Both parts are present: 'what' ("React/Next.js performance best practices from Vercel") and an explicit 'when' ("Use when writing, reviewing, or refactoring React/Next.js code for performance, data fetching, or bundle size") with concrete trigger contexts. It sits between anchors 4 and 5: the 'when' clause is more explicit than anchor 4's example, but the 'what' is a category label rather than a list of concrete actions, so it does not clearly meet anchor 5's 'concrete trigger phrases' on both halves.

4 / 5

Trigger Term Quality

Natural phrases users would say are well covered: "React/Next.js", "performance", "data fetching", "bundle size", and the activity verbs "writing, reviewing, or refactoring". This fits anchor 4 (good keyword coverage, a few natural terms missing) — common variations like 'slow renders', 'load time', 'hydration', or 'speed up my app' are absent, so it does not reach anchor 5's comprehensive synonym coverage, while anchor 3 would understate the solid multi-context coverage.

4 / 5

Distinctiveness Conflict Risk

The performance-focused React/Next.js niche is clear and the trigger contexts are qualified ("for performance, data fetching, or bundle size"), giving mostly distinct triggers — matching anchor 4. It is not anchor 5 because 'writing React/Next.js code' and 'data fetching' are broad enough that a general React style guide or data-fetching library skill could also trigger; it is well above anchor 3, whose examples lack any qualifying scope.

4 / 5

Total

15

/

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

marchatton/agent-skills

Path

.agents/skills/04-develop/00-frontend-general/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.