This skill reads more like a high-level overview or blog summary than actionable guidance for Claude. It lacks concrete configuration examples, executable code, and specific diagnostic workflows, repeatedly deferring to 'check the docs.' The content doesn't add much beyond what Claude would already know about Next.js and Turbopack.

Suggestions

Add concrete, executable examples: a `next.config.ts` snippet enabling/disabling Turbopack, a bundle analyzer configuration example, and specific CLI flags with expected output.

Replace vague 'see Next.js docs' references with either inline specifics or links to well-defined reference files (e.g., [BUNDLE_ANALYSIS.md] or [MIGRATION.md]).

Add a diagnostic workflow with explicit steps: e.g., 1. Check Turbopack is active (look for specific log output), 2. Verify cache exists in `.next`, 3. Clear cache and measure cold start, 4. Compare with `--webpack` flag.

Remove explanatory content Claude already knows (what Turbopack is, that Rust is fast) and focus on project-specific configuration patterns and troubleshooting decision trees.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary filler. Phrases like 'an incremental bundler written in Rust that significantly speeds up dev startup and hot updates' explain things Claude already knows, and the 'How It Works' section partially repeats the intro. The best practices are somewhat generic.	2 / 3
Actionability	The skill is vague and descriptive rather than instructive. It repeatedly defers to 'see Next.js docs for your version' instead of providing concrete configuration examples, specific flags, or executable code. The 'Examples' section just lists three basic CLI commands with no meaningful context, and there's no actual config file example, no turbopack config snippet, no bundle analyzer setup code.	1 / 3
Workflow Clarity	There's a loose sequence implied (dev → analyze → optimize) but no explicit multi-step workflow with validation checkpoints. The troubleshooting guidance ('if dev is slow, ensure you're on Turbopack') is too vague to be actionable. For a skill about diagnosing slow dev startup, there should be concrete diagnostic steps.	2 / 3
Progressive Disclosure	The content is organized into reasonable sections (When to Use, How It Works, Examples, Best Practices), but it's a flat document with no references to external files for deeper topics like bundle analysis configuration or migration from webpack. The repeated 'see Next.js docs' references are vague external pointers rather than structured one-level-deep references.	2 / 3
	Total	7 / 12 Passed

Description

32%

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 identifies a clear technology niche (Next.js 16+ with Turbopack) and lists relevant topic areas, but it reads more like a topic list than an actionable skill description. It lacks a 'Use when...' clause, concrete actions, and sufficient trigger term coverage to reliably distinguish it from related skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about configuring Turbopack, migrating from webpack, or optimizing Next.js build/dev performance.'

Replace topic keywords with concrete actions, e.g., 'Configures Turbopack for Next.js 16+ projects, enables incremental bundling and filesystem caching, diagnoses slow dev builds, and guides migration from webpack to Turbopack.'

Include additional natural trigger terms users might say, such as 'slow builds', 'next dev --turbo', 'bundler config', 'build optimization', or 'turbopack setup'.

Dimension	Reasoning	Score
Specificity	Names the domain (Next.js 16+ and Turbopack) and some relevant concepts (incremental bundling, FS caching, dev speed, Turbopack vs webpack), but these are more like topic areas than concrete actions. It doesn't list specific actions like 'configure Turbopack', 'migrate from webpack', or 'optimize build performance'.	2 / 3
Completeness	It partially addresses 'what' (topics around Turbopack and Next.js 16+) but there is no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also more topical than actionable, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Next.js', 'Turbopack', 'webpack', 'bundling', 'dev speed', and 'FS caching' that users might mention. However, it misses common variations like 'build performance', 'slow builds', 'next dev', 'turbo', or 'bundler configuration' that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Next.js 16+' and 'Turbopack' specifically narrows the scope, but it could overlap with a general Next.js skill or a webpack skill. The 'Turbopack vs webpack' comparison adds some distinctiveness, but without clearer boundaries it remains somewhat ambiguous.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Reviewed

2 months ago

Table of Contents

Discovery Implementation Validation