CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

turbopack

Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.

60

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 ./plugins/vercel/skills/turbopack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, highly actionable reference with concrete config, commands, and a sensible webpack-fallback path. Its weaknesses are inlined basics Claude already knows and a monolithic single-file structure where a references/ split would reduce token cost.

Suggestions

Cut or compress the Global CSS and CSS Modules subsections (root-layout import, Button example) to bare statements — Claude already knows how CSS Modules and global CSS imports work.

Move the loader-migration table and the full Production Build Diagnostics / Performance Profiling sections into references/ (e.g. references/migration.md, references/diagnostics.md) and keep one-line pointers in SKILL.md.

Make validation checkpoints explicit in the build-failure workflow, e.g. "run BUNDLER=webpack next build to confirm the failure is Turbopack-specific before changing config", instead of leaving verification implicit.

DimensionReasoningScore

Conciseness

Mostly efficient reference-style content, but sections like Global CSS ("Import global CSS in your root layout") and the CSS Modules Button example re-explain basics Claude already knows and could be trimmed.

3 / 5

Actionability

Extensive copy-paste-ready guidance (next.config examples, turbopack.rules, NEXT_TURBOPACK_TRACING=1, BUNDLER=webpack next build, migration table) with only minor gaps such as the incomplete withBundleAnalyzer snippet.

4 / 5

Workflow Clarity

The build-failure diagnostics are a clear numbered sequence and the migration path ends in a webpack fallback plus a compare-both-bundlers verification step, but validation checkpoints elsewhere (e.g. profiling, memory) are implicit rather than explicit.

4 / 5

Progressive Disclosure

Sections are well-organized and navigable, but ~300 lines of reference material (full loader-migration table, diagnostics, profiling guide) are inlined in SKILL.md with no bundle files; content that belongs in references/ files is in the main body.

3 / 5

Total

14

/

20

Passed

Description

78%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 with an explicit and concrete "Use when..." trigger clause anchored to a distinctive niche. Its main weakness is the thin what-statement ("Turbopack expert guidance"), which says little about what the skill actually does.

Suggestions

Replace the generic "Turbopack expert guidance" opener with the concrete capabilities the skill provides, e.g. "Configure the Next.js Turbopack bundler, migrate webpack loaders, and debug Turbopack build and HMR issues."

Add missing natural trigger variations such as "hot reload", "webpack migration", or "next dev --turbopack" to widen trigger matching.

DimensionReasoningScore

Specificity

Phrases like "configuring the Next.js bundler, optimizing HMR, debugging build issues" list several specific action areas, but the what-statement "Turbopack expert guidance" is itself generic, leaving minor gaps in coverage.

4 / 5

Completeness

An explicit "Use when" clause with concrete triggers covers the when, but the what ("Turbopack expert guidance") only vaguely states what the skill does, so it falls between the vague-what (3) and fully explicit (5) anchors.

4 / 5

Trigger Term Quality

Natural terms "Next.js bundler", "HMR", "build issues", and "Turbopack vs Webpack" match what users would say, but common synonyms such as "hot reload", "webpack migration", or the `next dev --turbopack` invocation are missing.

4 / 5

Distinctiveness Conflict Risk

"Turbopack" plus "Next.js bundler" defines a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

openai/plugins

Path

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