REPO PACKAGE
vercel-labs openreview
COMMUNITY7skills
5ready to use
LABSCO SUMMARY
The seven skills are next-best-practices (file conventions, RSC boundaries, data patterns), next-cache-components (Next.js 16's Cache Components, cacheLife, cacheTag), next-upgrade (version upgrades via official codemods), vercel-composition-patterns and vercel-react-best-practices (React composition and performance guidance from Vercel Engineering), vercel-react-native-skills (React Native and Expo performance), and web-design-guidelines (a UI review against Vercel's own Web Interface Guidelines). None of the seven mentions OpenReview, pull requests, or code review directly — they're the same reference material the bot's Claude-powered reviewer consults when it comments on a diff.
This serves two different readers. One wants an automated GitHub reviewer: deploy the app to Vercel, register a GitHub App with contents/issues/PR read-write access, and mention @openreview in a PR comment to trigger a review, fix, and push. The other just wants these seven skills as a standalone Next.js and React reference and never needs to run the bot at all — six of the seven need nothing beyond the skill file itself, and one needs a local tool already installed.
READ THE FULL ANALYSIS
The bot itself is explicitly beta. The README calls it an internal project built to help the Vercel team test their own technologies together and says plainly to expect rough edges and breaking changes — a caveat about the review workflow, not about the seven skills sitting inside it.
Running the bot costs more than reading the skills. It needs a Vercel deployment, an Anthropic API key, a registered GitHub App with a private key and webhook secret, and optionally a Redis URL for persistent state — without Redis it falls back to in-memory, which does not survive a restart. None of that is required to copy a skill file into your own project instead.
WHAT'S INSIDE
7 showing · 7 totalReady to use
Nothing else to set up — install it and go.
7 of 7
SETUP
Showing all 7 skills
next-best-practices
The rules a Next.js project is meant to follow, gathered in one place, so new code can be written and reviewed against them instead of from memory.
next-cache-components
Parts of a Next.js 16 page can be built once and served instantly while the rest is fetched fresh for each visitor — this is how you decide which parts are which, how long the saved ones last, and when they get thrown away.
next-upgrade
Brings an old Next.js project up to the current release, following the official migration guide for each version in between so nothing that changed along the way gets missed.
vercel-composition-patterns
When a component has sprouted a dozen true/false options, this is the way out: smaller parts that whoever uses the component puts together themselves.
vercel-react-best-practices
Fifty-eight rules from Vercel's engineers on what makes a React or Next.js app slow — requests that queue behind each other, JavaScript nobody needed, screens redrawing for nothing — and the fix for each one.
vercel-react-native-skills
What separates a React Native phone app that feels native from one that obviously doesn't — long lists that scroll smoothly, animations that don't stutter, and the platform's real menus and modals instead of imitations.
web-design-guidelines
Reads the code behind a page and lists where it breaks Vercel's published guidelines for how a web interface should look and behave, naming the exact file and line.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (7 skills)
npx skills add vercel-labs/openreviewSINGLE SKILLOr install a single skill
npx skills add vercel-labs/openreview --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.