Agent skill · Audited from source
next-upgrade
skill · vercel-labs/openreviewLicence not declaredAudited 22 Oct 2026 · source d14db90215ea
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d14db90215ea and found no filesystem, network or shell access and no hard-coded secrets. What it does: Upgrade Next.js to the latest version following official migration guides and codemods
Cite
Cite this page
ModelsAtlas. “next-upgrade (vercel-labs/openreview)”. Retrieved 22 Oct 2026. https://modelsatlas.com/skills/vercel-labs/next-upgrade
Trust audit
Audit 0.4.1 · source read 22 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 1 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass, no license.
Findings (1)
LOWInventory / provenanceinv.no_license
- Why
- no LICENSE file and no repo licence
- Fix
- add a licence
Audit 0.4.1 · source sha d14db90215ea · 22 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishervercel-labs GitHub organizationOwner of the repository this skill is read from
- Source foldervercel-labs/openreview/.agents/skills/next-upgradeThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdictd14db90215eaA new audit runs when the source changes
- Repository statusNot archivedLast push 229 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Upgrade Next.js to the latest version following official migration guides and codemods
---
name: next-upgrade
description: Upgrade Next.js to the latest version following official migration guides and codemods
argument-hint: "[target-version]"
---
# Upgrade Next.js
Upgrade the current project to the latest Next.js version following official migration guides.
## Instructions
1. **Detect current version**: Read `package.json` to identify the current Next.js version and related dependencies (React, React DOM, etc.)
2. **Fetch the latest upgrade guide**: Use WebFetch to get the official upgrade documentation:
- Codemods: https://nextjs.org/docs/app/guides/upgrading/codemods
- Version-specific guides (adjust version as needed):
- https://nextjs.org/docs/app/guides/upgrading/version-16
- https://nextjs.org/docs/app/guides/upgrading/version-15
- https://nextjs.org/docs/app/guides/upgrading/version-14
3. **Determine upgrade path**: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15).
4. **Run codemods first**: Next.js provides codemods to automate breaking changes:
```bash
npx @next/codemod@latest <transform> <path>
```
Common transforms:
- `next-async-request-api` - Updates async Request APIs (v15)
- `next-request-geo-ip` - Migrates geo/ip properties (v15)
- `next-dynamic-access-named-export` - Transforms dynamic imports (v15)
5. **Update dependencies**: Upgrade Next.js and peer dependencies together:
```bash
npm install next@latest react@latest react-dom@latest
```
6. **Review breaking changes**: Check the upgrade guide for manual changes needed:
- API changes (e.g., async params in v15)
- Configuration changes in `next.config.js`
- Deprecated features being removed
7. **Update TypeScript types** (if applicable):
```bash
npm install @types/react@latest @types/react-dom@latest
```
8. **Test the upgrade**:
- Run `npm run build` to check for build errors
- Run `npm run dev` and test key functionalityExcerpt, first 2,004 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit d14db90
npm install next@latest react@latest react-dom@latest npm install @types/react@latest @types/react-dom@latest
git clone https://github.com/vercel-labs/openreview git -C openreview checkout d14db90215ea
Commands as the repository documents them: shown, never run by us. Our verdict covers commit d14db90215ea only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
d14db90215ea
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/vercel-labs/next-upgrade/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
vercel-labs/openreview
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
vercel-labs/openreview
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
vercel/vercel
Deploy, manage, inspect, and troubleshoot Vercel projects from the command line. Use for Vercel deployments, Vercel Toolbar comments, build failures, projects and teams, environment variables, domains and DNS, logs,…
vercel/eve
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
vercel/ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
vercel/workflow
Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for…
Add this badge to your README
[](https://modelsatlas.com/skills/vercel-labs/next-upgrade/)
<a href="https://modelsatlas.com/skills/vercel-labs/next-upgrade/"><img src="https://modelsatlas.com/skills/vercel-labs/next-upgrade/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about next-upgrade
What does the next-upgrade skill do?
Is next-upgrade safe to install?
What can next-upgrade access on my machine?
How current is this page?
Sources
- github.com/vercel-labs/openreview/tree/main/.agents/skills/next- — the audited source at commit d14db90215ea and every finding aboveObserved · 22 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the next-upgrade skill do?
- Is next-upgrade safe to install?
- What can next-upgrade access on my machine?