[External Plugin]: Vercel Plugin

[Melkeydev]

Plugin name

vercel-plugin

Short description

Build and deploy web apps and agents. Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel expert.

GitHub repository

https://github.com/vercel/vercel-plugin

Plugin path inside the repository

/

Immutable ref to review

6e51924cb249e2941de005d59f1ac6f768477b98

Version

0.43.0

License identifier

Apache-2.0

Author name

Vercel

Author URL

https://github.com/vercel

Homepage URL

https://vercel.com/docs/agent-resources/vercel-plugin

Keywords

vercel
nextjs
ai-sdk
turborepo
turbopack
workflow
deployment
edge-functions
serverless
ai-gateway

Additional notes for reviewers

Spoke with Harald Kirschner in an internal Slack channel for this

Submission checklist

• The plugin lives in a public GitHub repository.
• The ref I provided is an immutable release tag or full 40-character commit SHA, not a branch.
• This submission follows this repository's contribution, security, and responsible AI policies.
• This plugin is not already listed in the Awesome Copilot marketplace.

[github-actions]

✅ External plugin intake passed

This submission passed automated intake validation and is ready for maintainer review.

• Plugin: vercel-plugin
• Repository: https://github.com/vercel/vercel-plugin
• Ref: 6e51924cb249e2941de005d59f1ac6f768477b98
• Keywords: vercel, nextjs, ai-sdk, turborepo, turbopack, workflow, deployment, edge-functions, serverless, ai-gateway

Canonical external.json payload

{
  "name": "vercel-plugin",
  "description": "Build and deploy web apps and agents. Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel expert.",
  "version": "0.43.0",
  "author": {
    "name": "Vercel",
    "url": "https://github.com/vercel"
  },
  "repository": "https://github.com/vercel/vercel-plugin",
  "homepage": "https://vercel.com/docs/agent-resources/vercel-plugin",
  "license": "Apache-2.0",
  "keywords": [
    "vercel",
    "nextjs",
    "ai-sdk",
    "turborepo",
    "turbopack",
    "workflow",
    "deployment",
    "edge-functions",
    "serverless",
    "ai-gateway"
  ],
  "source": {
    "source": "github",
    "repo": "vercel/vercel-plugin",
    "path": "/",
    "ref": "6e51924cb249e2941de005d59f1ac6f768477b98"
  }
}

Reviewer notes

Spoke with Harald Kirschner in an internal Slack channel for this

[aaronpowell]

@Melkeydev - couple of bits of feedback:

• The path should be / (or left blank) based on the structure of the repo, as it is to the folder in the repo that is the root for the plugin (ie - where Copilot will look for the .github/plugins/plugin.json or .plugin/plugin.json folder). This was a bit ambiguous in the submission process so I've fixed that.
• Right now, CLI has a bug where it doesn't support SHA pinning (VS Code supports it), but it turns out it needs to be a sha property not the ref property. I've got a fix with the team underway for CLI, so if you're ok with the potential issue in CLI we can leave that as is, otherwise you'd need to create a tag in the repo and update the ref to point to it instead.

At the minimum, can you update Plugin path inside the repository in the issue to be blank or / and then comment /rerun-intake and it'll update the JSON to move forward.

[Melkeydev]

/rerun-intake

[Melkeydev]

@Melkeydev - couple of bits of feedback:

• The path should be / (or left blank) based on the structure of the repo, as it is to the folder in the repo that is the root for the plugin (ie - where Copilot will look for the .github/plugins/plugin.json or .plugin/plugin.json folder). This was a bit ambiguous in the submission process so I've fixed that.
• Right now, CLI has a bug where it doesn't support SHA pinning (VS Code supports it), but it turns out it needs to be a sha property not the ref property. I've got a fix with the team underway for CLI, so if you're ok with the potential issue in CLI we can leave that as is, otherwise you'd need to create a tag in the repo and update the ref to point to it instead.

At the minimum, can you update Plugin path inside the repository in the issue to be blank or / and then comment /rerun-intake and it'll update the JSON to move forward.

hey I comment with /rerun-intake but I dont think it triggered the job!

[aaronpowell]

/rerun-intake

[aaronpowell]

/approve

[github-actions]

✅ External plugin approved

A maintainer approved vercel-plugin, and the submission issue has been closed.

• Catalog action: added
• Source repository: vercel/vercel-plugin
• PR against staged: [external-plugin] Add vercel-plugin #1829