internal-dev-workbench
Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated `<branch>.<name>.localhost` URLs for the Next.js workbench and the observability UI, plus a Claude statusline that surfaces those URLs. Use only when the user asks for a "portless dev session", a "tmux dev layout for workflow", "worktree-isolated dev URLs", or wants to wire workflow dev URLs into the Claude statusline. Do not activate for the generic "start the dev server" / "run pnpm dev" task.
Install
With your agent
Install OMGSkills skill "vercel/workflow:internal-dev-workbench" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/vercel/workflow /tmp/workflow && ln -s /tmp/workflow/skills/internal-dev-workbench ~/.claude/skills/internal-dev-workbenchFrom README
internal-dev-workbench Bootstraps an opinionated 3-pane tmux session for end-to-end Workflow SDK development. Each pane is launched through portless so URLs are stable and worktree-scoped (e.g. https:// .turbopack.localhost), letting multiple worktrees run concurrently without port conflicts. A companion statusline script surfaces the active URLs in Claude Code's prompt. This is opt-in contributor tooling. The repo's standard dev path (pnpm dev from a workbench, no portless) is unaffected. Prerequisites tmux installed portless installed globally (npm i -g portless or via Homebrew). Verify with portless --version. Repo bootstrapped: pnpm && pnpm build. The first run on a fresh worktree must complete both before any dev server can start (the workbench apps depend on built workspace packages; without pnpm build you get MODULENOTFOUND for workflow).
More skills
authoring-skills
How to create and maintain agent skills in .agents/skills/.
backport-pr
Backport a merged Next.js pull request from canary to a previous release branch such as next-16-2.
create-pr
Used to create Git branches, commits, pushes, and GitHub pull requests for Next.js.