← Search

The Next.js edit/verify dev loop
Developer tools 🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it 📌 Pinned version: commit 5da8ef1
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: Next.js 16.3+ with Turbopack…

The Next.js edit/verify dev loop

Confirm every app change actually works at runtime by cross-checking Next.js's /_next/mcp view with a real browser

At a glance
What
Confirm every app change actually works at runtime by cross-checking Next.js's /_next/mcp view with a real browser
Cost
Free
Needs
Next.js 16.3+ with Turbopack; agent-browser >= 0.31.1 on PATH; a running next dev
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Next.js Dev Loop is a free Muse skill that confirms every app change actually works at runtime by cross-checking Next.js's own view with a real browser. After every code change, it checks the running app, not just compilation, comparing the Next.js view, with routes, RSC, server actions and logs, against a real Chrome view, with DOM, console and network.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit 5da8ef1
🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Next.js 16.3+ with Turbopack; agent-browser >= 0.31.1 on PATH; a running next dev Install "The Next.js edit/verify dev loop" for me. Give my agent the Next.js edit/verify rhythm — preflight the /_next/mcp endpoint and the agent-browser session once per run, then after every edit check the four failure modes: compiles, runs without errors, behaves as intended, React-level behavior Repository: https://raw.githubusercontent.com/vercel/next.js/5da8ef12bc6b4156dd490e58e3878e06fd7f4472/skills/next-dev-loop/SKILL.md Pinned version: install the code at commit 5da8ef12bc6b4156dd490e58e3878e06fd7f4472 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the vercel-next.js-next-dev-loop skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "vercel-next.js-next-dev-loop". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. upgrade Next.js to 16.3+ with Turbopack, install agent-browser >= 0.31.1, and start next dev before the loop). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 5da8ef1 · 2026-10-13
🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
5da8ef1 · 2026-10-13
Sandbox install test
Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.