react-best-practices

React performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring React code to ensure optimal performance patterns. Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./registry/skills/react-best-practices/SKILL.md

Quality

Content

75%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 token-efficient, well-organized index that excels at progressive disclosure and conciseness, correctly pushing detail into reference files. Its weakness is actionability at the overview level — no inline executable examples — and slightly implicit navigation to individual files.

Suggestions

Add 1-2 inline code snippets for the highest-priority CRITICAL rules (e.g. a Promise.all example under Eliminating Waterfalls) so the overview is actionable without opening a file.

Link each rule ID to its file (e.g. `async-parallel` -> [references/async-parallel.md]) or add a single explicit pointer per category to make navigation unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is a lean index of rule IDs with one-line descriptions, a priority table, and no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	The body provides concrete rule identifiers and brief actionable hints ('Move await into branches where actually used') but no executable code or commands in SKILL.md itself — actual code lives in the reference files, leaving guidance incomplete at the overview level.	3 / 5
Workflow Clarity	The priority table sequences the categories and 'How to Use' explains the single lookup action ('Read individual files as needed'), giving a clear sequence with only minor gaps in how to pick a starting rule within a category.	4 / 5
Progressive Disclosure	Well-structured overview split across 37 one-level-deep reference files organized by category with a priority table; references are signaled by rule ID but lack explicit per-file markdown links, a minor navigation gap.	4 / 5
	Total	16 / 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-structured description that clearly states both purpose and trigger conditions in third person, with solid natural trigger terms. The main weakness is that the stated actions (writing/reviewing/refactoring) are generic verbs rather than concrete performance capabilities.

Suggestions

Replace the generic verbs ('writing, reviewing, or refactoring') with concrete capabilities like 'identifying re-render waste, eliminating data-fetch waterfalls, and reducing bundle size'.

Add common synonyms users say, such as 'rendering performance', 'memoization', or 'React slow renders' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('React performance optimization guidelines') and a few actions ('writing, reviewing, or refactoring React code'), but the actions are generic verbs rather than concrete capabilities, so it stops at '1-2 concrete actions, not comprehensive'.	3 / 5
Completeness	Explicitly answers both 'what' (React performance optimization guidelines) and 'when' with concrete trigger phrases ('Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements').	5 / 5
Trigger Term Quality	Includes natural user-facing terms ('React components, data fetching, bundle optimization, performance improvements') with good coverage, though a few common synonyms (e.g. 'rendering', 'memoization') are missing.	4 / 5
Distinctiveness Conflict Risk	The performance niche with triggers like 'bundle optimization' and 'data fetching' is mostly distinct, but the broad 'writing, reviewing, or refactoring React code' phrasing creates minor overlap risk with general React skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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: provectus/awos-recruitment
Path: registry/skills/react-best-practices/SKILL.md
Commit: 298fce7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.