CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

next-dev-loop

Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.

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

81%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 strong operational skill: concrete commands, hard version gates with refuse conditions, an explicit verification checklist, and recovery loops for stale-session failure modes. The only tightening opportunities are trimming the meta-level feedback-policy section and showing the exact /_next/mcp probe invocation.

DimensionReasoningScore

Conciseness

The body is dense and operational — bash snippets, exact version floors, failure modes, and recovery procedures — with almost no explanation of concepts Claude already knows. Minor over-explanation remains (rationale sentences like 'Runtime introspection stays cheap as the codebase grows; agentic search doesn't' and the somewhat convoluted ~12-line 'Report Next.js friction' policy section), fitting anchor 4 rather than the every-token-earns-its-place lean of anchor 5.

4 / 5

Actionability

Mostly executable: copy-paste session/open commands, a concrete sed recipe for SSE parsing, named probes (tools/list, get_compilation_issues, get_routes), and explicit refuse conditions. Minor gaps keep it from anchor 5 — the /_next/mcp probe describes what to call but shows no exact HTTP command, and agent-browser subcommand usage is delegated to `agent-browser skills get core` and `tools/list` rather than given inline.

4 / 5

Workflow Clarity

The sequence (requires → preflight → loop → teardown) is explicit with validation throughout: preflight refuses on missing versions/webpack with disambiguation steps, the after-the-edit section is a four-item failure-mode checklist, and gotchas contain error-recovery feedback loops (blank snapshot → reopen with same flags → close and reopen; locator timeout → check URL and fresh snapshot before retry). This matches anchor 5's 'explicit validation steps; feedback loops for error recovery; checklists'.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so everything is inline, but the single file is well organized with clear, purposeful sections (requires, preflight, loop, gotchas, reference, teardown) and each section is used directly in the loop. It fits anchor 4 (good structure, content appropriately placed, minor gaps) rather than anchor 5, since the ~60-line gotchas block and the tool reference table are inline in a ~200-line file rather than split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

73%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 specific, honest description with a clear niche and explicit tooling requirements. Its main gaps are the purpose-based rather than situational 'when' clause and missing common synonym triggers like 'dev server' or 'hot reload', plus only one genuinely distinct action verb.

Suggestions

Add concrete situational trigger phrases, e.g. 'Use when the user edits Next.js app code during `next dev` and needs to confirm the change works at runtime' — this would lift completeness from 4 to 5.

Include common user phrasings as triggers: 'dev server', 'hot reload', 'check my change actually works', so the skill fires on natural requests as well as technical ones.

Enumerate the distinct verification actions (compile check, runtime error check, DOM behavior assert, React-level introspection) instead of restating 'verify/confirm' twice, to broaden capability coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Verify Next.js runtime behavior after editing app code") and restates one core action ("confirm a change actually works in a running app"), with the two named tools (/_next/mcp, agent-browser) as mechanisms rather than distinct actions. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several distinct listed actions.

3 / 5

Completeness

Both parts are present: the 'what' ("Verify Next.js runtime behavior... Combines /_next/mcp... with agent-browser") and an explicit use clause ("Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks"). The 'when' is purpose-based rather than concrete situational trigger phrases (e.g., 'after the user edits Next.js app code'), which fits anchor 4 rather than anchor 5.

4 / 5

Trigger Term Quality

It includes solid natural keywords users would say: "Next.js", "next dev", "runtime", "compiles", "type-checks", "running app". A few common variations are missing (e.g., "dev server", "hot reload", "Turbopack", "test my change"), matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — runtime verification of Next.js apps during `next dev` via two named tools — with triggers unlikely to fire for unrelated skills. This matches anchor 5 (clear niche with distinct triggers; minimal conflict risk); nothing pushes it toward the overlap described in anchor 4.

5 / 5

Total

16

/

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-dev-loop/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.