Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/next-dev-loop
Verify Next.js runtime behavior after editing app code.
Passed 16 of 18 test cases with the skill, and 5 of 18 without it.
and 17 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before calling agent-browser subcommands for React inspection, should I guess the subcommands from memory or fetch the official CLI documentation? What is the command to fetch it?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running agent-browser skills get core to fetch the usage guide | Missed | Passed |
The instructions your model reads when the skill loads.
The edit/verify rhythm during next dev — make a change, then
confirm it actually works at runtime, not only that the types or
the build are happy.
You verify through two views of the same running app:
/_next/mcp — an HTTP endpoint Next.js exposes about itself.
Knows framework-specific things: routes, segments, RSC, server
actions, server logs, and errors as Next.js saw them. Call
tools/list for the current surface.agent-browser — a CLI that drives a real Chrome. Knows
framework-agnostic browser things: DOM, console, network, React
fiber, vitals. Before driving it, run agent-browser skills get core
once for the version-matched usage guide — don't guess subcommands
from memory.The two views cross-check each other.
/_next/mcp plus the
proactive compile check via get_compilation_issues.agent-browser >= 0.31.1 — React introspection, worktree-scoped
session id, idempotent --restore, and launch flag reconciliation.These are hard floors, not soft preferences. If anything is missing, tell the user how to upgrade and stop. Don't fall back to grepping source or to a weaker probe — this skill assumes both views are live at the versions above.
pnpm next upgrade (or npx next upgrade).
Docs: https://nextjs.org/docs/app/getting-started/upgrading
(version-16 guide:
https://nextjs.org/docs/app/guides/upgrading/version-16)agent-browser: npm i -g agent-browser@latest.
If the CLI isn't on PATH, install it before continuing — preflight
expects to invoke it directly.test cases passed, vs 5 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.