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.

60

Quality

71%

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 ./.kiro/skills/nextjs-turbopack/SKILL.md

The canonical home for this skill is nextjs-turbopack in affaan-m/ECC

SKILL.md
Quality
Evals
Security

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.

The body is well-structured and self-contained with concrete commands, but it leans on repeated 'see the docs' hedges and omits the actual Bundle Analyzer config, slightly weakening actionability and conciseness. No bundle files exist to reference.

Suggestions

Replace repeated 'check the official Next.js docs for your version' hedges with a single version-note line to reduce repetition and reclaim tokens.

Add the actual Bundle Analyzer config snippet (e.g. the `experimental.bundleAnalyzer` or next.config block) instead of deferring to 'see Next.js docs'.

De-duplicate the 'Turbopack is default in dev' point between the 'When to Use' and 'How It Works' sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining basic concepts, but the hedge 'check the official Next.js docs for your version' repeats ~4 times and the 'When to Use' and 'How It Works' sections overlap on the 'default in dev' point, so it could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste commands (`next dev`, `next build`, `next start`) and explicit flags (`--webpack`, `--no-turbopack`), but the Bundle Analyzer guidance ('enable via config or experimental flag (see Next.js docs)') omits the actual config snippet, leaving a minor gap.

4 / 5

Workflow Clarity

This is a reference/instructional skill with no destructive or batch workflow, so no validation checkpoints are required; the content is clearly sequenced into well-labeled sections, though there is no multi-step process with explicit checkpoints to push it to 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is self-contained with well-organized sections (When to Use, How It Works, Examples, Middleware, Best Practices), meeting the 'under 50 lines with no need for external references' exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

78%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 concise, specific, and clearly niched to Next.js 16+/Turbopack with a present (if narrow) trigger clause. It avoids fluff and third-person voice is maintained throughout.

Suggestions

Broaden the 'when' guidance beyond the Turbopack-vs-webpack choice, e.g. 'Use when developing or debugging Next.js 16+ apps, diagnosing slow dev startup/HMR, or choosing Turbopack vs webpack.'

Add a few natural synonyms/extensions (e.g. 'HMR', 'hot reload', 'next dev') to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (Next.js 16+, Turbopack) plus several concrete capabilities — 'incremental bundling, FS caching, dev speed' and 'when to use Turbopack vs webpack' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor.

4 / 5

Completeness

Clearly states what the skill covers and includes an equivalent trigger clause ('when to use Turbopack vs webpack'), so it is not capped at 3, though the 'when' is narrower than a broad 'Use when developing Next.js apps' trigger.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('Next.js', 'Turbopack', 'webpack', 'bundling', 'caching', 'dev speed') with good but not exhaustive coverage of synonyms/extensions, matching the 'good keyword coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Next.js 16+ and Turbopack' framing carves a clear niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.