CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards against regression. Use when asked to grow a static shell, fix a slow first paint or non-instant navigation, diagnose which Suspense boundary blocks useful UI, or add instant() regression coverage. Requires Next.js 16.3+ with Cache Components already adopted.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 workflow architecture is excellent — a gated P→G loop with trustworthy-RED verification, parity, differential testing, and a PR checklist — and the in-body guidance is specific rather than abstract. However, the skill leans on three bundled files that are not present in the bundle, leaving its central executable artifact (the instant() test) unspecified, and the body carries noticeable duplication that inflates token cost.

Suggestions

Ship the referenced bundle files (`rig-template.md`, `test-template.md`, `reference/red-test-robustness.md`) or inline a minimal executable `instant()` test example so the skill's central artifact actually exists for the reader.

Deduplicate: state the rig-agnosticism (verdict comes from the build, not the platform) and the "ruler, not a stopwatch" point once in phase A, and consolidate the three next-partial-prefetching-optimizer handoff mentions into the "After optimization" section.

Tighten the meta sections ("What is invariant, and what is yours", "Reporting to the user") to their decision-relevant core — each currently spends many lines restating points made elsewhere in the body.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but noticeably repetitive and tightenable: the rig-agnosticism point appears twice nearly verbatim ("a local `next build && next start`, a CI/staging container, and a per-push preview deploy are equally valid rigs" vs. phase A's restatement "the verdict comes from the build, not the platform"), "a ruler, not a stopwatch" is stated twice, and the `next-partial-prefetching-optimizer` handoff appears three times. Meta sections ("What is invariant, and what is yours", "Reporting to the user") could be condensed. Not 4 because the redundancy exceeds minor instances; not 2 because there is no explanation of concepts Claude already knows and the content is high-signal.

3 / 5

Actionability

The body supplies concrete commands (`npm ls next @next/playwright`, `npx @next/codemod upgrade`, the `rg` partialPrefetching check), complete config snippets (`exposeTestingApiInProductionBuild: process.env.EXPOSE_TESTING_API === '1'`), and a blocker-to-pattern decision table — but the executable core is delegated to `test-template.md`, `rig-template.md`, and `reference/red-test-robustness.md`, none of which exist in the bundle, and no `instant()` test example appears inline. That missing key executable detail places it at 3 rather than 4; it is well above 2 given the in-body specificity.

3 / 5

Workflow Clarity

Phases P→G are clearly sequenced with explicit validation gates and feedback loops: "C-gate: do not start optimizing until the RED is verified trustworthy" with a two-branch resolution, "D-gate: phase D is complete when the locked test from phase C passes GREEN under the lock", the parity checklist (E), the revert/re-apply differential (F), a PR checklist, and an explicit stop condition ("the locked test from C is GREEN on the rig, the differential (F) holds, and every item above is checked"). This matches the 5 anchor's checklists, checkpoints, and error-recovery loops.

5 / 5

Progressive Disclosure

In-body structure is good with clearly signaled one-level-deep references and a "Files" section describing each one, but all three referenced files (`rig-template.md`, `test-template.md`, `reference/red-test-robustness.md`) are absent from the bundle (no references/, scripts/, or assets/ directories exist), so the disclosure structure is broken in practice. Not 4 because missing referenced files is a major, not minor, organization gap; not 2 because references are clearly signaled rather than buried and nothing is nested two-plus levels.

3 / 5

Total

14

/

20

Passed

Description

92%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 strong description: third-person, concrete about what the skill does, with an explicit and well-phrased "Use when" clause covering four distinct triggers and a stated version prerequisite. The only gap is a few missing natural synonyms (e.g., loading skeletons, slow page loads) that some users would say instead of "first paint" or "non-instant navigation".

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: "Optimize the meaningful UI available immediately from a Next.js route", "Encode the goal as a failing @next/playwright instant() e2e and work it to green", "guards against regression", and "diagnose which Suspense boundary blocks useful UI". It names the domain and covers the full capability surface (both navigation types, the TDD loop, diagnosis, regression guarding), so it matches the 5 anchor rather than 4, where minor coverage gaps would remain.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the optimize/encode/work-to-green/ship-regression-guard workflow, and the "when" is a concrete "Use when asked to grow a static shell, fix a slow first paint or non-instant navigation, diagnose which Suspense boundary blocks useful UI, or add instant() regression coverage" clause, plus an explicit prerequisite ("Requires Next.js 16.3+ with Cache Components already adopted"). The when-clause is explicit and specific, matching the 5 anchor rather than 4.

5 / 5

Trigger Term Quality

Good natural-phrasing coverage: "grow a static shell", "fix a slow first paint or non-instant navigation", "diagnose which Suspense boundary blocks useful UI", "add instant() regression coverage" — phrases a user would plausibly say. Not 5 because common variations like "loading skeleton", "page is slow to load", or "spinner shows too long" are missing; not 3 because both casual and technical trigger phrasings are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche: Next.js 16.3+ Cache Components instant-navigation optimization keyed to @next/playwright instant(), with explicit boundary against sibling skills ("hand off to next-partial-prefetching-optimizer"). Triggers like "static shell", "instant()", and "Suspense boundary" are unlikely to fire a different skill, so minimal conflict risk (5, not 4's "minor overlap risk").

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vercel/next.js

Path

skills/next-cache-components-optimizer/SKILL.md

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.