CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

76%

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/vercel-react-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The SKILL.md body is an efficient, well-organized index with a sensible priority system, but its entire progressive-disclosure layer is broken: all referenced detail files (rules/*.md and AGENTS.md) are missing from the bundle, leaving 65 one-line rules with no underlying code examples or explanations. As shipped, it functions as a bare checklist rather than the guide it claims to be.

Suggestions

Ship the referenced detail files: include the rules/ directory with the 65 rule .md files (and AGENTS.md) that the body points to, or remove/repair the references so no path in SKILL.md dangles.

Add a minimal inline code example for at least the two CRITICAL categories (e.g., async-parallel with Promise.all(), bundle-barrel-imports with a direct-import snippet) so the entry file stays actionable even when rule files are not loaded.

State the consultation workflow explicitly (e.g., '1. Match the code to a rule category via the Quick Reference, 2. Pick highest-priority applicable rules, 3. Open the rule file for before/after examples'), and drop the duplicated priority/impact column from the table since the section headers already carry it.

DimensionReasoningScore

Conciseness

The body is a lean index: 65 one-line rule directives with prefixes, no explanation of concepts Claude already knows, and no padded prose — every rule line carries information. It falls short of anchor 5 because of duplication: the priority table repeats the category/impact/prefix information that the Quick Reference section headers state again, and the 4-line blockquote clarifying AGENTS.md scope could be tightened. Not anchor 3, since there is no unnecessary explanation — only minor redundancy.

4 / 5

Actionability

Each rule line is a genuine directive ("Use Promise.all() for independent operations", "Import directly, avoid barrel files", "Hoist RegExp creation outside loops") — but they are one-liners with no code examples, no commands, and no key details in the body itself. Anchor 4 expects 'concrete code or commands with minor gaps', which the body does not provide; anchor 3 ('some concrete guidance but incomplete; missing key details') fits — especially because the promised executable examples live in rules/*.md files that are not present in this bundle, so the detail layer is entirely missing.

3 / 5

Workflow Clarity

Usage is well-sequenced for an index-style skill: 'When to Apply' states the entry conditions, the priority table gives an explicit CRITICAL→LOW ordering to consult rules, and 'How to Use' explains what each rule file contains (why/incorrect/correct/context). This is a read/reference skill with no risky or destructive operations, so no validation checkpoints apply; the main reason it is not 5 is that the sequence (consult index → prioritize by impact → open rule file) is implied rather than stated as an explicit ordered workflow.

4 / 5

Progressive Disclosure

The structure is designed as a textbook overview-plus-index pointing one level deep to rules/async-parallel.md, rules/bundle-barrel-imports.md, and AGENTS.md — but none of these files exist in the bundle; references/, scripts/, assets/, rules/, and AGENTS.md are all absent. Per the guideline to score against the actual bundle structure, every detailed reference is a dangling pointer that fails when followed, which is worse than anchor 3 ('references present but not clearly signaled'). Anchor 2 ('minimal structure; references are buried' / content that belongs in separate files is effectively unreachable) is the closest match.

2 / 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: it explicitly states both what it provides and when to use it, with an enumerated, natural-sounding trigger list and third-person voice. Minor gaps in trigger-synonym coverage (no 're-renders', 'bundle size', 'hydration', 'App Router') keep it just short of the top anchors.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — "writing, reviewing, or refactoring React/Next.js code" plus "data fetching, bundle optimization" — with only minor coverage gaps (no mention of re-render/rendering optimization, which the body says are MEDIUM-priority categories). It lists several specific actions but is not fully comprehensive, matching the anchor 4 example ('Extracts text from PDF files, fills forms, converts pages to images') rather than the comprehensive anchor 5; it is well above anchor 3, which expects only 1-2 concrete actions.

4 / 5

Completeness

Both 'what' and 'when' are explicitly answered with concrete trigger phrases: what — "React and Next.js performance optimization guidelines from Vercel Engineering"; when — "This skill should be used when writing, reviewing, or refactoring React/Next.js code" and "Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements". This matches the anchor 5 example structure ('Extract text and tables from PDF files... Use when the user mentions PDFs, forms, or document extraction') and is stronger than anchor 4, where the 'when' is present but could be more explicit — here the trigger clause is explicit and enumerated.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would actually say: "React components", "Next.js pages", "data fetching", "bundle optimization", "performance improvements". Not anchor 5 because common variations users say are missing — e.g. 'slow renders', 're-renders', 'bundle size', 'App Router', 'hydration' — whereas anchor 5 expects 'synonyms and file extensions' level coverage like 'PDF files, PDFs, .pdf'. It clearly exceeds anchor 3 ('Some relevant keywords but missing common variations') since the core natural terms are present.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — React/Next.js *performance* optimization — and the trigger set is enumerated, giving minimal conflict risk with unrelated skills. Not anchor 5 because triggers like 'writing React components' or 'data fetching' could also fire for general React style/testing/data-fetching skills (minor overlap with closely related skills), matching anchor 4; it is clearly more distinct than anchor 3 ('could still overlap with similar skills').

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

calesthio/OpenMontage

Path

.agents/skills/vercel-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.