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.

65

Quality

77%

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

71%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 clean, token-efficient rule catalog with strong structure, but its usefulness is undercut by the absence of the referenced rule files and AGENTS.md, and by the lack of inline executable examples. Shipping the referenced files and a few representative code snippets would substantially raise the score.

Suggestions

Provide the referenced rules/*.md files and AGENTS.md so the one-level-deep navigation actually resolves.

Include 1-2 inline executable code examples (e.g., a Promise.all before/after) so the body is actionable without requiring the external files.

Expand the terse "How to Use" section with a brief decision flow for selecting a category by problem type.

DimensionReasoningScore

Conciseness

Lean rule index with one-line glosses, no padding, and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Rule glosses are concrete directives (e.g., "Use Promise.all() for independent operations"), but the body contains no executable code examples — they live only in the referenced rule files, leaving key implementation details missing.

3 / 5

Workflow Clarity

The priority table sequences rules by impact and "How to Use" describes the lookup-and-apply flow clearly; no validation checkpoints are needed since this is a non-destructive reference skill, though the usage section is terse.

4 / 5

Progressive Disclosure

The body is a well-structured overview pointing one level deep to rules/*.md and AGENTS.md, but those referenced bundle files do not exist, so the clear navigation is undermined by missing targets.

3 / 5

Total

15

/

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 well-crafted description that clearly states purpose and trigger conditions in third person with concrete, natural-sounding keywords. Minor gains possible by adding file-extension triggers and tightening the broadest performance phrasing.

DimensionReasoningScore

Specificity

Names the React/Next.js performance domain and several concrete activities ("writing, reviewing, or refactoring", "data fetching, bundle optimization"); falls short of comprehensive capability enumeration expected at 5.

4 / 5

Completeness

Explicitly answers both what ("performance optimization guidelines") and when ("This skill should be used when... Triggers on tasks involving...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would say ("writing, reviewing, or refactoring React/Next.js code", "bundle optimization", "data fetching") with good synonym coverage, but missing file extensions and a few common variations.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear React/Next.js performance niche with distinctive Vercel framing; minor overlap risk from the broad phrase "performance improvements".

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
mediago-dev/mediago
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.