CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

v8-jit

V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure allocation, array packing, and profiling with --trace-opt / --trace-deopt.

Quality

84%

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

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.

A technically strong, actionable pattern reference with concrete code, runnable profiling commands, and a useful review checklist. Its weaknesses are structural: everything lives inline in one large file with no progressive disclosure, the profile→fix→re-verify loop is implicit, and one closure example is not self-contained.

Suggestions

Split the Profiling and Verification material (V8 flags, % natives, Next.js profiling commands) into a references/profiling.md file and keep a one-line pointer plus the single most-used command in SKILL.md, shrinking the main file considerably.

Add an explicit re-verification step after applying optimizations, e.g. "re-run `node --trace-deopt` on the same workload and confirm the deopt no longer appears", turning the checklist into a closed validate→fix→re-verify loop.

Fix the closure-hoisting example so it is self-contained — define `stream` in `handleRequest` (e.g. take it as a parameter) so the code runs as written.

DimensionReasoningScore

Conciseness

The body is dense and applied — GOOD/BAD code pairs, rules lists, real-codebase examples, and useful myth-busting ("String concatenation in loops is usually fine in modern V8") — but the "Background: V8's Tiered Compilation" section and the hidden-class intro partly restate concepts Claude already knows. Mostly efficient with minor over-explanation that could be trimmed fits 4; 3 would require several padded sections, 5 no padding at all.

4 / 5

Actionability

Concrete, mostly executable guidance throughout: copy-paste-ready TypeScript GOOD/BAD pairs and runnable profiling commands ("node --trace-deopt $(which jest) --runInBand test/path/to/test.ts"). Minor gaps keep it at 4 — e.g. the closure-hoisting example calls `requestIdByStream.set(stream, req.id)` with `stream` never defined in scope, and the StreamProcessor "BEST" example shows no wiring. 3 would require pseudocode or missing key details; 5 requires no gaps.

4 / 5

Workflow Clarity

The "Checklist for Hot Path Code Reviews" gives a concrete validation instrument, and the profiling section provides verification commands (trace-opt/trace-deopt/cpu-prof), so a workable review-then-verify sequence exists. However, the fix→re-profile feedback loop is only implicit — there is no explicit "re-run the trace to confirm the deopt is gone" step — which fits 4 (clear sequence, most checkpoints, minor validation gaps) rather than 5.

4 / 5

Progressive Disclosure

A single ~430-line monolith with good section headers but no bundle files: the profiling flags, % natives, and string/Map sections are self-contained reference material that clearly belongs in separate files per the rubric's structure. Some structure but content that should be separate is inline matches 3; it is not 2 (headers and navigation exist) and not 4 (nothing is split out, so an interested reader must consume everything at full depth).

3 / 5

Total

15

/

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: explicit what and when, concrete capability list, good natural trigger terms tied to Next.js module names, and a well-defined niche. The only weakness is that a few natural user phrasings (performance tuning, deoptimization, benchmarking) are absent.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — "hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure allocation, array packing, and profiling with --trace-opt / --trace-deopt" — alongside "writing or reviewing hot-path code", giving comprehensive coverage of the skill's scope. It clearly matches the 5 anchor (multiple specific concrete actions, comprehensive) rather than 4, which would require minor coverage gaps.

5 / 5

Completeness

It explicitly answers both what ("V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals") and when ("Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path") with concrete trigger phrases, in third-person voice. This matches the 5 anchor exactly; 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Natural trigger terms are present and strong — "V8 JIT optimization patterns", "high-performance JavaScript", "hot-path code in app-render, stream-utils, routing, caching, or any per-request code path" — but a few natural phrasings users might say are missing (e.g. "performance tuning", "deoptimization", "benchmarking", "slow request handling"). Good keyword coverage with a few natural terms missing fits 4; it is not the comprehensive-with-synonyms coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — V8 JIT performance for Next.js server internals — with module-level triggers (app-render, stream-utils, routing, caching) that would not plausibly fire for other skills. Minimal conflict risk matches the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

vercel/next.js

Path

.agents/skills/v8-jit/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.