nextjs-turbopack

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

Quality

69%

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

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 compact, well-organized informational skill with solid basic commands and clean sectioning. Its main weaknesses are repetition and doc-deferral on the Bundle Analyzer and version-specific details, which reduce conciseness and actionability.

Suggestions

Consolidate the overlapping 'Turbopack is default in dev' and 'file-system caching' points so they appear once instead of in both 'When to Use' and 'How It Works'.

Replace the Bundle Analyzer's 'see Next.js docs' deferral with a concrete minimal config snippet (e.g. the experimental flag and a sample invocation) so the guidance is executable.

Move version-specific notes (Next.js 16, 16.1+, flag name variation) into a dedicated 'Version notes' or 'Deprecated/old patterns' section to keep the main guidance lean and avoid time-sensitive clutter.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with clear sections, but redundancy between 'When to Use' and 'How It Works' (Turbopack default in dev, FS caching repeated) plus repeated 'check the docs for your version' hedging and scattered version-specific info (Next.js 16, 16.1+) that lacks a deprecated/old-patterns section means it could be tightened.	3 / 5
Actionability	Provides concrete executable commands ('next dev', 'next build', 'next start', '--webpack', '--no-turbopack') but key advanced features like the Bundle Analyzer defer entirely to docs ('enable via config or experimental flag (see Next.js docs)') with no actual config example, leaving notable gaps.	3 / 5
Workflow Clarity	This is an informational rather than destructive/batch skill, and its guidance is organized into clear sequenced sections (When to Use, How It Works, Examples, Best Practices); no validation checkpoints are required for this non-destructive context, though there is no strict multi-step workflow.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references, yet well-organized into clearly signaled sections (When to Use, How It Works, Examples, Best Practices), satisfying the simple-skill exception for a top score.	5 / 5
	Total	15 / 20 Passed

Description

75%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 specific, well-targeted description that names concrete capabilities and includes a when clause for tool selection. It is slightly held back by a 'when' that leans toward in-skill tool choice rather than a full explicit trigger list, and minor overlap with general Next.js skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Next.js 16+ and Turbopack') plus several concrete capabilities ('incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack'), with only minor gaps such as 'dev speed' being a benefit rather than an action.	4 / 5
Completeness	Clearly states what the skill covers ('incremental bundling, FS caching, dev speed') and provides an explicit when clause ('when to use Turbopack vs webpack') acting as trigger guidance, though the 'when' is more about tool selection than a full 'Use when...' trigger list.	4 / 5
Trigger Term Quality	Includes natural terms developers actually say ('Next.js', 'Turbopack', 'webpack', 'bundling', 'dev speed') with good coverage, though a few common synonyms or phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	The Turbopack/bundling niche is mostly distinct with clear triggers, but it carries minor overlap risk with a general Next.js skill.	4 / 5
	Total	16 / 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
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

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.