Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
$ npx skills add vercel-labs/openreview --skill next-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/openreview next-best-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/next-best-practices .claude/skills/next-best-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .claude/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel-labs/openreview --skill next-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/openreview next-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/next-best-practices .agents/skills/next-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .agents/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/openreview --skill next-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/openreview next-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/next-best-practices .cursor/skills/next-best-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .cursor/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel-labs/openreview.git --path .agents/skills/next-best-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel-labs/openreview --skill next-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/openreview next-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/next-best-practices .gemini/skills/next-best-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .gemini/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel-labs/openreview next-best-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel-labs/openreview --skill next-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/next-best-practices .github/skills/next-best-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .github/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/openreview --skill next-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/openreview next-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/openreview.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/next-best-practices .opencode/skills/next-best-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "next-best-practices" agent skill from https://github.com/vercel-labs/openreview/tree/main/.agents/skills/next-best-practices into .opencode/skills/next-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-best-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
next-best-practicesNext.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Next Best Practices is an agent skill from vercel-labs/openreview, published by the product's own GitHub organization. Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files (for example `async-patterns.md`, `bundling.md` and `data-patterns.md`).
It sits in Development, covering Error handling. It works with Next.js, Vercel and React. The repository describes itself as: An open-source, self-hosted AI code review bot powered by Vercel.
Read from SKILL.md and the folder at commit 672deb2. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Next Best Practices loads about 1k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 375 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Without a licence we can't republish the file, so here is its outline and opening line. It has 375 words (~1,001 tokens).
“Apply these rules when writing or reviewing Next.js code.”
SKILL.md and 19 other files in .agents/skills/next-best-practices of vercel-labs/openreview.
Open the folder on GitHubat commit 672deb2
We found 18 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 18 other GitHub owners. This page covers the copy in vercel-labs/openreview, which our catalogue first saw on October 7, 2026.
Next Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Next Best Practices this skillvercel-labs/openreview | 1.7k | 18 repos | ~1k | Automated safety check: Pass | None | |
| React Refactor Tournamentragnar-pwninskjold/tech-snacks | 137 | — | ~1.3k | Automated safety check: Pass | MIT | |
| React Performanceaffaan-m/ECC | 276k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Vercel React Best Practicessanity-io/sanity | 6.4k | 129 repos | ~1.6k | Automated safety check: Pass | MIT | |
| React Best Practicesryokun6/ryos | 1.3k | — | ~2k | Automated safety check: Pass | MIT | |
| Vercel React Best Practicesgambitph/Stackable | 351 | — | ~2k | Automated safety check: Pass | MIT |
ragnar-pwninskjold/tech-snacks
Review React/Next.js code against the real vercel-react-best-practices skill, backlog the performance findings keyed to actual rule ids + impact tiers, rank the most over-subscribed tiers, then fix…
affaan-m/ECC
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).
sanity-io/sanity
React and Next.js performance optimization guidelines from Vercel Engineering.
ryokun6/ryos
React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).
gambitph/Stackable
React performance optimization guidelines from Vercel Engineering.
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
React and Next.js performance optimization from Vercel Engineering.
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
vercel-labs/openreview
A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.
vercel-labs/openreview
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
vercel-labs/openreview
Upgrade Next.js to the latest version following official migration guides and codemods
Categories
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling. Next Best Practices is an agent skill from vercel-labs/openreview, published by the product's own GitHub organization.
Next Best Practices fits situations like: tasks that involve Error handling.
Run `npx skills add vercel-labs/openreview --skill next-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/next-best-practices in vercel-labs/openreview) into .claude/skills/next-best-practices in your project. Claude Code loads it when a task matches its description.
Run `npx skills add vercel-labs/openreview --skill next-best-practices -a codex`. Or copy the skill folder (.agents/skills/next-best-practices in vercel-labs/openreview) into .agents/skills/next-best-practices in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel-labs/openreview --skill next-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/next-best-practices, .gemini/skills/next-best-practices, .github/skills/next-best-practices and .opencode/skills/next-best-practices in your project.
SKILL.md names no scripts, command-line tools or credentials: Next Best Practices is instructions for the agent only. Our summary lists: Node.js; Docker.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
No licence was found for Next Best Practices or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Next Best Practices: React Refactor Tournament (ragnar-pwninskjold/tech-snacks, 137 stars), React Performance (affaan-m/ECC, 276k stars), Vercel React Best Practices (sanity-io/sanity, 6.4k stars) and React Best Practices (ryokun6/ryos, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/openreview, which has 1,695 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on March 6, 2026.
Source: vercel-labs/openreview on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
