CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

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-organized, concise rule index that clearly signals progressive disclosure, but its referenced rule files and AGENTS.md are absent from the bundle, undermining the navigation it promises.

Suggestions

Provide the referenced rules/*.md rule files and AGENTS.md in the bundle so the 'How to Use' and 'Full Compiled Document' pointers resolve to real content.

Include a few inline executable code examples for the highest-priority (CRITICAL) rules so the skill is actionable without requiring every rule file to be opened.

Add a brief 'How to apply a rule' workflow step (read rule file -> apply pattern -> verify) so the navigation path through the rules is fully sequenced.

DimensionReasoningScore

Conciseness

The body is a lean rule index that assumes Claude's competence, with no padding or explanation of basic concepts, earning every token's place.

5 / 5

Actionability

Concrete rule identifiers and a clear 'How to Use' section point to per-rule files, but the body itself is an index without inline executable code examples, leaving minor gaps.

4 / 5

Workflow Clarity

'When to Apply', the priority-ranked category table, and 'How to Use' give a clear sequence for navigating the rules; no destructive/batch operations apply so the validation cap is not triggered.

4 / 5

Progressive Disclosure

Structure is clean with one-level-deep references (rules/*.md, AGENTS.md), but the referenced bundle files do not actually exist in the skill directory, so navigation leads to missing materials.

3 / 5

Total

16

/

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, third-person description that clearly states both capability and trigger conditions with concrete, natural keywords. Minor room for additional synonyms and broader coverage.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ('writing, reviewing, or refactoring React/Next.js code', 'data fetching, bundle optimization'), with only minor coverage gaps relative to the comprehensive 5-anchor.

4 / 5

Completeness

It explicitly answers both 'what' ('React and Next.js performance optimization guidelines') and 'when' ('Triggers on tasks involving ...'), with concrete trigger phrases matching the 5-anchor.

5 / 5

Trigger Term Quality

It includes natural user-facing keywords ('React components', 'Next.js pages', 'data fetching', 'bundle optimization', 'performance improvements') with good coverage, missing a few common synonyms or extensions.

4 / 5

Distinctiveness Conflict Risk

The React/Next.js performance niche is clearly distinct with specific triggers, with only minor overlap risk against general coding skills.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openstatusHQ/data-table-filters
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.