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

62%

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 rule catalog with clear priorities and an unambiguous single action, but it loses points for inlining all rules with no executable examples and for pointing to detail files that are not present in the bundle. The biggest issue is broken/missing references undermining the progressive-disclosure design.

Suggestions

Add the missing referenced files (rules/*.md and AGENTS.md) to the bundle, or remove the references and inline minimal executable code examples for at least the CRITICAL/HIGH rules so the body is self-contained.

Trim the inline rule list to the top-priority categories (CRITICAL/HIGH) and move the MEDIUM/LOW rules entirely into the detail files to tighten the overview and improve conciseness.

Add a short explicit selection workflow (e.g., match the task to a category trigger → read the rule file → apply the correct pattern → verify the change preserves behavior) so the application sequence is not only implicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient short bullets that assume Claude's competence, but it inlines all 65 rules including many LOW/LOW-MEDIUM priority ones whose tokens do not clearly earn their place at the overview level and could be offloaded to detail files.

2 / 3

Actionability

Rules are named with specific imperative directives ("Use Promise.all()", "Import directly, avoid barrel files"), but the body contains no executable code or copy-paste examples — all concrete code is deferred to the referenced rule files.

2 / 3

Workflow Clarity

As a single-purpose reference/catalog skill, the single action (identify the relevant category by priority and consult the matching rule) is unambiguous via the priority table and "When to Apply" section, so the simple-skills exception applies.

3 / 3

Progressive Disclosure

References to detail files (rules/*.md, AGENTS.md) are explicitly signaled and one level deep, but those files do not exist in the bundle and the full rule list is inlined rather than split out, matching the anchor for content that should be separate being inline.

2 / 3

Total

9

/

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 strong: it specifies concrete actions, uses natural trigger terms, explicitly answers both what and when, and carves out a distinct niche. No meaningful weaknesses to address.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("writing, reviewing, or refactoring React/Next.js code") and specific task types (components, pages, data fetching, bundle optimization), matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly states what ("React and Next.js performance optimization guidelines") and provides an explicit "Triggers on..." clause for when, satisfying both halves rather than leaving the trigger implied.

3 / 3

Trigger Term Quality

Covers natural terms users would say ("React components", "Next.js pages", "data fetching", "bundle optimization", "performance improvements") with broad, natural variation rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (React/Next.js performance from Vercel) with framework-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
calesthio/OpenMontage
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.