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.

64

Quality

75%

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

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, efficiently structured rule index with good progressive-disclosure intent, but it provides no inline executable code examples and references bundle files that are not present in the actual bundle.

Suggestions

Inline at least one concrete code example (e.g., a before/after for async-parallel) so the skill is actionable directly from SKILL.md without requiring the missing rules/*.md files.

Verify and ship the referenced bundle (rules/*.md and AGENTS.md) or remove the file-path references if the rules are not bundled.

Trim the Quick Reference section to avoid restating the category names and prefixes already in the priority table.

DimensionReasoningScore

Conciseness

The body is a structured index/table rather than padded prose, which is efficient, but the ~120-line Quick Reference restates the category names and prefixes already shown in the priority table and could be tightened.

2 / 3

Actionability

Each rule is paired with a concrete one-line directive (e.g., "Use Promise.all() for independent operations"), but the actual executable code examples are deferred to the rules/*.md files rather than appearing in SKILL.md, leaving the inline guidance instructive but not copy-paste ready.

2 / 3

Workflow Clarity

"When to Apply", the priority-ordered category table, and "How to Use" give a usable sequence for selecting and reading rules, but there are no explicit checkpoints or validation steps in the apply-then-verify flow.

2 / 3

Progressive Disclosure

Content is well-split with one-level-deep references (rules/*.md, AGENTS.md) and clear navigation, but the referenced bundle paths (rules/async-parallel.md, AGENTS.md) do not exist in the provided bundle directories, so the disclosure cannot be fully verified against actual files.

2 / 3

Total

8

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-triggered with natural terminology and a clear, distinct React/Next.js performance niche. It capably answers what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("writing, reviewing, or refactoring React/Next.js code", "data fetching, bundle optimization, or performance improvements") rather than vague language; the capabilities are named in third-person gerund form, matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what ("React and Next.js performance optimization guidelines") and when ("This skill should be used when..." / "Triggers on...").

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say — "React components, Next.js pages, data fetching, bundle optimization, or performance improvements" — with an explicit "Triggers on tasks involving..." clause.

3 / 3

Distinctiveness Conflict Risk

Clear niche (React/Next.js performance) with distinct, domain-specific triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.