CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-best-practices

React performance optimization guidelines from Mastra Engineering. 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

82%

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

78%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-engineered progressive-disclosure routing skill: the SKILL.md body stays an overview, every rule bullet points to a verified canonical rule file, and lookup commands make navigation concrete. The remaining gaps are modest — some duplicated overview sections and no explicit decision procedure for selecting among the 27 rules when reviewing code.

Suggestions

Drop or merge the 'When to Apply' section and the trailing 'Rule Categories' table, both of which restate information already in the description, the priority table, and the References section.

Add a short ordered decision procedure for the most common flows (e.g., 'When reviewing: check imports/barrels first, then data-fetching waterfalls, then render/setState patterns') so rule selection doesn't depend on reading the whole list.

Inline one two-line code example for the two CRITICAL rules (Promise.all and direct source import) so the highest-impact guidance is executable without opening a rule file.

DimensionReasoningScore

Conciseness

The body is a lean routing guide of terse directives that assumes React competence, with no padding explaining concepts Claude already knows. Minor trims exist — the 'When to Apply' section duplicates the description's triggers and the trailing 'Rule Categories' table repeats the priority table — matching anchor 4 (efficient, minor instances that could be trimmed) rather than anchor 5.

4 / 5

Actionability

Bullets give concrete, named APIs ('Promise.all()', 'startTransition', 'toSorted()', 'content-visibility: auto', 'skipToken'), executable grep commands for lookup, and every rule cites its rule-file slug for details. It stops short of anchor 5's copy-paste-ready code because implementation examples are delegated to the rule files rather than shown inline.

4 / 5

Workflow Clarity

The routing sequence is clear: consult the priority table, pick a category or slug, grep or open the canonical rule file, then apply. There are no validation checkpoints, but the skill involves no destructive or batch operations, so none are required. It falls short of anchor 5 because the decision flow for which of the 27 rules applies to a given task is implicit rather than an explicit ordered procedure.

4 / 5

Progressive Disclosure

The body is a pure overview with well-signaled, one-level-deep references: the catalog (references/react-best-practices-reference.md) and all 27 rule files under references/rules/ exist and match the cited slugs, each bullet names its rule file inline, and grep examples are provided for direct lookup. This matches anchor 5 (clear overview, appropriately split, easy navigation).

5 / 5

Total

17

/

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 answers both what the skill provides and when to use it, with explicit, natural trigger phrases. Its main weakness is specificity: it never says what the guidelines actually cover (e.g., waterfall elimination, bundle size, re-render patterns), leaving the capability statement generic.

Suggestions

Replace the generic 'performance optimization guidelines' with 2-3 concrete capability statements drawn from the skill's own categories, e.g., 'Eliminates request waterfalls, reduces bundle size, and prevents unnecessary re-renders in React code.'

Add a few common trigger synonyms such as 'hooks', 're-renders', or 'React performance' variations to widen natural keyword coverage.

Narrow the overly broad 'React components' trigger to performance- or quality-related component work to reduce overlap with general React style skills.

DimensionReasoningScore

Specificity

The description names the domain ('React performance optimization guidelines') and trigger contexts ('writing, reviewing, or refactoring React code'), but the skill's concrete capabilities are not enumerated — 'guidelines' is generic and the listed actions are user activities rather than what the skill does. This matches anchor 3 (names domain and 1-2 concrete actions) rather than anchor 4, which expects several specific skill actions.

3 / 5

Completeness

Both questions are explicitly answered: what ('React performance optimization guidelines from Mastra Engineering') and when, with concrete trigger phrases ('This skill should be used when writing, reviewing, or refactoring React code... Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements'). This clearly matches anchor 5; anchor 4 would require a less explicit 'when'.

5 / 5

Trigger Term Quality

Natural keywords users would say are well covered: 'React components', 'data fetching', 'bundle optimization', 'performance improvements', 'refactoring'. A few common variations are missing (hooks, re-renders, React.js), fitting anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The React performance niche is distinct and triggers are mostly performance-specific ('bundle optimization', 'data fetching', 'performance improvements'). Minor overlap risk remains with general React coding/style skills because 'React components' is a broad trigger, fitting anchor 4 rather 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

mastra-ai/mastra

Path

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