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.
Scanned 5/30/2026
Install to Claude Code
npx -y skills add aiskillstore/marketplace --skill deploying-to-production --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Deploying To Production?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-deploying-to-production)More formats (shields.io, HTML) on the badges page.
---
name: deploying-to-production
description: 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.
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.