nextjs-turbopack

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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-structured and appropriately lean for a simple informational skill, but its guidance is largely advisory and repeatedly defers to external docs rather than providing concrete, executable instructions.

Suggestions

Replace the 'see Next.js docs' deferrals with a concrete config snippet for enabling the Bundle Analyzer and for disabling Turbopack (--webpack / --no-turbopack) so guidance is copy-paste ready.

Add a short diagnostic workflow for slow dev (e.g. confirm Turbopack is active -> check the .next cache isn't being cleared -> isolate the slow module) with a verification step, raising workflow clarity.

De-duplicate the 'incremental bundler' definition and consolidate the repeated 'check the docs for your version' notes into a single version-disclaimer line.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but could be tightened: "an incremental bundler written in Rust" restates the "Incremental bundler for Next.js dev" point under How It Works, and "check the official Next.js docs for your version" is repeated across several bullets.	2 / 3
Actionability	It lists real commands (`next dev`, `next build`, `next start`) but they are trivial, and the remaining guidance defers to external docs ("see Next.js docs", "enable via config or experimental flag") without a concrete, copy-paste config snippet.	2 / 3
Workflow Clarity	Content is organized into sections, but there is no sequenced multi-step workflow with validation checkpoints (e.g. for diagnosing slow dev or trimming a production bundle), and it is not a single unambiguous action that would warrant a 3 for a simple skill.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files and no need for external references, and the body is well-organized into clearly labeled sections (When to Use, How It Works, Examples, Best Practices), meeting the simple-skill criterion for a top score.	3 / 3
	Total	9 / 12 Passed

Description

72%

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 to a clear niche and uses natural trigger terms, but it lacks an explicit 'Use when...' clause telling Claude when to invoke the skill, which caps its completeness.

Suggestions

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

Lead with concrete actions a user would invoke (e.g. 'Diagnose slow dev startup, inspect production bundles, switch Turbopack/webpack') rather than feature nouns like 'incremental bundling, FS caching'.

Reduce technical jargon ('FS caching', 'incremental bundling') in favor of user-facing phrasing like 'file-system caching for faster restarts'.

Dimension	Reasoning	Score
Specificity	It names the domain and some capabilities ("incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack") but these are features rather than a comprehensive list of concrete actions a user would invoke, matching the level-2 anchor.	2 / 3
Completeness	It states what the skill covers but has no "Use when..." clause or equivalent explicit trigger guidance for the skill itself ("when to use Turbopack vs webpack" is content guidance, not a skill trigger), so completeness is capped at 2.	2 / 3
Trigger Term Quality	It covers natural terms users would actually say — "Next.js 16+", "Turbopack", "webpack", "dev speed" — giving good coverage of the relevant trigger vocabulary.	3 / 3
Distinctiveness Conflict Risk	The Next.js 16+ / Turbopack bundling niche is clearly distinct with specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
Commit: 4130457

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.