CtrlK
BlogDocsLog inGet started
Tessl Logo

nextjs-turbopack

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

59

Quality

68%

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

Quality

Content

71%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-structured, actionable, and self-contained with a clear decision framework and a valuable middleware-naming guardrail. The main weakness is repeated "check the docs" filler and mild over-explanation that inflates tokens without adding guidance.

Suggestions

Consolidate the repeated "check the official Next.js docs for your version" into a single note rather than restating it in each section.

Replace the explanatory "an incremental bundler written in Rust that significantly speeds up dev startup" with a leaner statement assuming Claude knows Turbopack.

Show a concrete Bundle Analyzer enablement snippet (config flag) instead of deferring entirely to docs, and add useful flags to the bare next dev/build/start commands.

DimensionReasoningScore

Conciseness

Mostly efficient with bullet structure and code, but it repeats "check the official Next.js docs for your version" ~4 times and over-explains what Turbopack is ("an incremental bundler written in Rust"), so it could be tightened.

3 / 5

Actionability

Provides concrete commands (next dev/build/start, --webpack, --no-turbopack) and a clear proxy.ts vs middleware.ts rule, with minor gaps such as the bare commands and the Bundle Analyzer config being deferred to docs.

4 / 5

Workflow Clarity

The "When to Use" section gives clear decision branches (Turbopack default / Webpack legacy / Production check docs) and the middleware directive is unambiguous; no destructive batch operations so the validation cap does not apply, though there is no explicit multi-step sequence.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-organized sections (When to Use, How It Works, Examples, Middleware File Naming, Best Practices) and a single appropriate external docs link, fitting the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

66%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 specific and well-keyworded with a clear niche, but it lacks an explicit "Use when..." trigger clause, capping completeness. Adding a concrete invocation trigger would lift the completeness and trigger-term scores.

Suggestions

Append an explicit trigger clause such as "Use when developing, debugging, or optimizing Next.js 16+ apps, or diagnosing slow dev startup / HMR."

Add natural synonyms users say ("HMR", "hot reload", "build speed") to broaden trigger-term coverage.

Lead with verb-based actions (e.g., "Diagnoses slow dev startup, configures Turbopack vs webpack") instead of noun-phrase topics to sharpen specificity.

DimensionReasoningScore

Specificity

Enumerates several concrete capabilities — "incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack" — naming the domain with multiple specific topics rather than vague language.

4 / 5

Completeness

The "what" is clear, but there is no explicit "Use when..." trigger clause; the "when to use Turbopack vs webpack" phrase is a bundler-choice decision, not skill-invocation guidance, so per the rubric cap completeness stays at 3.

3 / 5

Trigger Term Quality

Includes natural terms users say ("Next.js 16+", "Turbopack", "webpack", "dev speed") with good coverage, though common synonyms like "HMR" or "hot reload" are absent.

4 / 5

Distinctiveness Conflict Risk

The Next.js 16+ / Turbopack bundling niche is mostly distinct with minimal conflict risk, with only minor overlap against a broader general Next.js skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.