mcpField
V
vercel-deployment

vercel-deployment

github.com/sickn33Cloud & DevOps48.7k1.8k installsUpdated today
Repository

About vercel-deployment

vercel-deployment is a skill for agents handling Next.js deployment work on Vercel. It provides a guided procedure with prerequisites, validation and authorization safeguards.

Key features

  1. 01Next.js 向け Vercel デプロイ手順
  2. 02事前条件とガイド参照の確認
  3. 03環境設定とロールバックの検証
  4. 04本番反映と DNS 変更の承認確認

Use cases

  1. 01Vercel のプレビュー環境を準備
  2. 02本番デプロイの条件を確認
  3. 03環境変数や Edge Function の作業

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill vercel-deployment

After installing, type/vercel-deploymentin Claude Code to confirm it loaded.

Bundled filesreferences/detailed-guide.md

Details

From the project README

Vercel Deployment

Expert knowledge for deploying to Vercel with Next.js

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

Prerequisites

  • Verify the project's Next.js version and available local skills; historical upstream names such as nextjs-app-router may not be installed.

When to Use

  • User mentions or implies: vercel
  • User mentions or implies: deploy
  • User mentions or implies: deployment
  • User mentions or implies: hosting
  • User mentions or implies: production
  • User mentions or implies: environment variables
  • User mentions or implies: edge function
  • User mentions or implies: serverless function

Example

Prepare a preview deployment for the approved Vercel project/team using staging data. Verify build/runtime settings, environment scopes and rollback; production promotion and DNS changes require explicit destination authorization. Report the actual deployment ID and smoke-check result.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported