Tessl • The management layer for AI agent skills

SkillPublic

dce-edge

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXT_RUNTIME vs real feature flag distinction, and forcing flags false for edge in define-env.ts.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 dense, expert-level skill body that is concise and actionable, with clear section structure and concrete verification commands. Its main gap is the absence of an explicit validate-then-fix feedback loop for the risky edge-bundling changes it describes.

Suggestions

Add an explicit validate-fix-retry feedback loop in the Verification section (e.g. 'If the standalone edge test fails on node:* resolution, re-check define-env.ts force-false, then re-run') to support the destructive edge-bundling edits this skill gates.

Show the switcher-module pattern and the define-env force-false expression ('isEdgeServer ? false : flagValue') as copy-paste code blocks rather than prose, to lift actionability to fully executable.

Consider extracting the longer prose sections (Compile-Time Switcher Pattern, app-page.ts gotchas) into a references/ file so the main body stays a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient: it assumes Claude's competence, skipping generic explanations of webpack/DCE, and every sentence carries non-obvious, codebase-specific knowledge that earns its place.	5 / 5
Actionability	Provides concrete executable patterns (the if/else require() code block, exact test commands like 'pnpm test-start-webpack test/e2e/app-dir/app/standalone.test.ts') with minor gaps — some patterns are described rather than shown as copy-paste code (e.g. the switcher module, the define-env force-false expression).	4 / 5
Workflow Clarity	The Verification section gives a clear, ordered sequence with explicit commands and an anti-pattern ('not with NEXT_SKIP_ISOLATE=1'), but there is no explicit validate-fix-retry feedback loop for the destructive edge-bundling edits this skill gates.	4 / 5
Progressive Disclosure	Well-organized into clear topical sections with a Related Skills pointer to sibling skills; no bundle files exist to offload detail, and the single inline example is appropriately brief, so structure is good with only minor room for deeper reference splitting.	4 / 5
	Total	17 / 20 Passed

Description

91%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 highly specific, well-structured description with explicit 'what' and 'when' guidance and concrete trigger files. It is distinctive and action-oriented, with only minor room for broader natural-language trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, specific actions — 'conditional require() calls', 'guarding Node-only imports (node:stream etc.)', 'editing define-env-plugin.ts / app-render / stream-utils', 'forcing flags false for edge in define-env.ts' — with comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers 'what' ('DCE-safe require() patterns and edge runtime constraints') and 'when' with a concrete 'Use when writing conditional require() calls, guarding Node-only imports ... or editing define-env-plugin.ts / app-render / stream-utils for edge builds' trigger clause.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('conditional require() calls', 'edge builds', 'node:stream') and named files, but the terms are fairly codebase-internal and lack common synonyms or broader phrasings a user might naturally say.	4 / 5
Distinctiveness Conflict Risk	Carves a clear, narrow niche (webpack DCE + Next.js edge-runtime require() constraints) with named files and flags unlikely to overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/dce-edge/SKILL.md
Revision: ec8ddcd

Reviewed: 1 month ago

Discovery Implementation Validation

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.

dce-edge

Table of Contents

Is this your skill?