Skip to content
TrustedSkillsbeta
Back to all skills

Next Upgrade

Official
vercel-labs·vlatest·cloud

Official vercel-labs skill covering Vercel, Next.js for agent workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add vercel-labs/openreview --skill next-upgrade -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

vercel-labs

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned vercel-labs/openreview at 672deb21e7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
672deb21e7
Manifest
.agents/skills/next-upgrade/SKILL.md
Scanned
1 file, 45 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, next-upgrade, likely facilitates upgrading Next.js projects or components. While specific details are unavailable, it suggests automated processes related to updating versions and dependencies within a Next.js environment. It aims to streamline the upgrade process and potentially handle compatibility issues.

When to use it

  • You need to update a Next.js project to a newer version of React or Next.js.
  • You are encountering compatibility issues after upgrading a component library used in your Next.js application.
  • You want to automate the process of updating dependencies within a Next.js project.
  • You're looking for assistance with migrating older Next.js codebases to newer standards.

Key capabilities

  • Next.js upgrade automation
  • Dependency management
  • Compatibility handling (implied)

Example prompts

  • "Upgrade my Next.js project to the latest version."
  • "What are the compatibility issues when upgrading from v12 to v14 of Next.js?"
  • "Automate the upgrade process for this component library within my Next.js app."

Tips & gotchas

The skill's effectiveness depends on the complexity of your project and potential conflicts with existing dependencies. Reviewing changelogs and testing thoroughly after using this skill is recommended.