Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

nextjs-turbopack

Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/nextjs-turbopack/SKILL.md

Quality

Content

57%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 body is well-organized and appropriately short with a clean single-file structure, but its guidance is hedged with repeated 'check the docs for your version' deferrals and version-conditional instructions that leave the reader without a definitive action. Concrete command examples exist but are bare, and enabling the Bundle Analyzer is described only in the abstract.

Suggestions

Consolidate the repeated 'check the docs for your version' hedges into one note (e.g., a single 'Version differences' line) and state the definitive flag per version instead of '(or --no-turbopack depending on your Next.js version)'.

Make the commands actionable: show the actual dev invocation with the disable flag (e.g. 'next dev --webpack' for Next.js 16) and a concrete config snippet for enabling the experimental Bundle Analyzer.

Add a quick verification step, e.g. how to confirm Turbopack is active from the dev-server banner or .next contents, so 'ensure you're on Turbopack' is checkable rather than aspirational.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not pad with concepts Claude already knows, but hedging is repeated four times ('check the docs for your release', 'see Next.js docs for your version', 'check the official Next.js docs for your version'), and version-specific numbers (16, 16.1) appear throughout outside any 'deprecated patterns' section, which the guidelines penalize. It could be meaningfully tightened, matching anchor 3.	3 / 5
Actionability	There is some concrete guidance ('next dev', 'next build', '--webpack', '--no-turbopack', 'cache is typically under .next'), but the commands block is bare with no flags, the Bundle Analyzer is only described as 'enable via config or experimental flag' with no snippet or command, and key details are deferred to external docs. This is incomplete concrete guidance, matching anchor 3.	3 / 5
Workflow Clarity	The 'When to Use' section gives decision guidance, but it is hedged into ambiguity — 'Disable with `--webpack` (or `--no-turbopack` depending on your Next.js version...)' and 'may use Turbopack or webpack depending on Next.js version' leave the actual action unresolved, and there is no checkpoint for verifying which bundler is active. Not a destructive/batch skill, so no hard cap applies, but sequence and checkpoints are only implicit, matching anchor 3.	3 / 5
Progressive Disclosure	The skill has no bundle files (no references/, scripts/, or assets/ directories exist), and the body is under 50 lines with well-organized sections (When to Use, How It Works, Examples, Best Practices) and no need for external references. Per the under-50-lines guideline, this scores 5 with just well-organized sections.	5 / 5
	Total	14 / 20 Passed

Description

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

The description is distinct and contains the key natural trigger terms (Next.js, Turbopack, webpack), but it reads as a topic list rather than a statement of concrete actions, and it lacks an explicit 'Use when...' trigger clause — the 'when to use Turbopack vs webpack' phrase refers to the subject matter, not skill invocation. It is serviceable but below the quality of the good examples.

Suggestions

Add an explicit trigger clause, e.g. 'Use when developing or debugging Next.js 16+ apps, when dev startup or HMR is slow, or when deciding between Turbopack and webpack.'

Convert topic nouns into concrete actions: 'Configure Turbopack for Next.js dev, diagnose slow dev startup and HMR, manage FS caching, and decide Turbopack vs webpack.'

Include a few more natural synonyms users would say — 'HMR', 'hot reload', 'slow dev server', 'bundle size' — to widen trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete topics ('incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack'), but these are noun-phrase topics rather than concrete actions, and coverage has gaps. It lists domain plus a few specific items but is not comprehensive, matching anchor 3 rather than 4.	3 / 5
Completeness	The 'what' is reasonably clear (topics the skill covers), but 'when to use Turbopack vs webpack' describes the subject matter rather than when to invoke the skill — there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'Next.js', 'Turbopack', 'webpack', and 'dev speed' are natural terms users would say when needing this skill, giving good keyword coverage. A few common variations are missing ('HMR', 'hot reload', 'slow dev server', 'bundle size'), keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	'Next.js 16+', 'Turbopack', and 'webpack' carve out a clear, distinct niche with specific technical triggers. Minor overlap risk remains with a general Next.js or webpack tooling skill, so it does not reach anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .cursor/skills/nextjs-turbopack/SKILL.md
Revision: 25278e7

Reviewed: 29 days ago

Discovery Implementation Validation

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.

nextjs-turbopack

Table of Contents

Is this your skill?