mcpbeat

Deploying To Production

zhanlincui/deploying-to-production

Automate creating a GitHub repository and deploying a web project to Vercel. Use when the user asks to deploy a website/app to production, publish a project, or set up GitHub + Vercel deployment.

325 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
2
copies elsewhere
how many repositories repackaged it
176
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/ZhanlinCui/Agent-Skills-Hunter --skill deploying-to-production

The instruction itself

7 sections, as written by the author

Deploying to Production

Use this workflow when a user says "deploy this website/app" or similar. Follow the checklist in order and do not skip steps.

Deployment Workflow

  • [ ] Step 1: Run build and verify no errors
  • [ ] Step 2: Create GitHub repository
  • [ ] Step 3: Push code to GitHub
  • [ ] Step 4: Deploy to Vercel
  • [ ] Step 5: Verify deployment

Step 1: Run build

Run:

npm run build

If build fails, read the errors, fix issues, and run again. Only proceed when build succeeds.

Step 2: Create GitHub repository

Create a new GitHub repository for the project. If the repo already exists, confirm whether to reuse or create a new one.

Step 3: Push code to GitHub

Initialize git if needed, add remote, and push the default branch. Confirm the repository contains the expected code.

Step 4: Deploy to Vercel

Deploy the GitHub repo to Vercel. Capture the deployment URL.

Step 5: Verify deployment

Verify the live deployment by opening the URL or checking a response. If verification fails, diagnose and redeploy.

Repackaged in 2 other repositories

same content, different owner
aiskillstore/marketplace open on GitHub →
ComeOnOliver/skillshub open on GitHub →

How to use it

Copy the folder

Take zhanlincui/deploying-to-production from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.