Deploy To Vercel
Skill Verifiziert AktivDeploy a Next.js application to Vercel. Covers project linking, environment variables, preview deployments, custom domains, and production deployment configuration. Use when deploying a Next.js app for the first time, setting up preview deployments for pull requests, configuring custom domains, or managing environment variables in a production Vercel deployment.
To provide a guided and robust process for deploying Next.js applications to Vercel, covering all essential configuration and deployment steps.
Funktionen
- Deploys Next.js applications to Vercel
- Configures project linking and environment variables
- Supports preview deployments for pull requests
- Facilitates custom domain configuration
- Recommends GitHub integration for CI/CD
Anwendungsfälle
- Deploying a Next.js app for the first time
- Setting up preview deployments for pull requests
- Configuring custom domains for a Vercel deployment
- Managing environment variables for production and preview environments
Nicht-Ziele
- Deploying applications other than Next.js
- Managing Vercel account billing or advanced project settings beyond deployment configuration
- Troubleshooting Vercel CLI installation issues beyond basic permission errors
Documentation
- info:Configuration & parameter referenceWhile the skill outlines steps and provides examples, it does not explicitly document all potential Vercel CLI parameters or environment variables with their defaults and precedence orders. It implicitly relies on Vercel CLI's own documentation and user knowledge.
Execution
- info:ValidationThe skill relies on the Vercel CLI and npm to handle validation of inputs and outputs. There are no explicit schema validations within the skill's script itself.
Scope
- info:Dry-run previewThe Vercel CLI offers preview deployments and `vercel --dry-run` is not explicitly mentioned or implemented within the skill's steps, but preview deployments serve a similar purpose for inspecting changes before production.
Installation
/plugin install agent-almanac@pjt222-agent-almanacQualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Azure Deploy
100Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
Firebase Hosting Basics
99Skill for working with Firebase Hosting (Classic). Use this when you want to deploy static web apps, Single Page Apps (SPAs), or simple microservices. Do NOT use for Firebase App Hosting.
Firebase App Hosting Basics
99Deploy and manage web apps with Firebase App Hosting. Use this skill when deploying Next.js/Angular apps with backends.
Secrets Management
100Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Learn Site Structure
100Authoritative reference for how docs in this repo (and 5 other Netdata-org repos) become published pages on `learn.netdata.cloud`. Covers the `<repo>/docs/.map/map.yaml` source-of-truth (the actual lever -- filesystem path is irrelevant for routing), the live `ingest/ingest.py` orchestrator in the learn repo (NOT the legacy `ingest.js`), frontmatter injection, slug rules, sidebar autogeneration, MDX escape rules, versioning, the 4-mechanism redirect stack, the 6 source repositories, the every-3-hours CI ingest, Netlify deploy, and the `part_of_learn=True` opt-in for files hand-authored in the learn repo. Use when adding/moving/renaming/deleting a docs page; when a page on Learn looks wrong; when wondering whether to edit a doc here or in the learn repo; when reading `ingest.py`, `sidebars.js`, `docusaurus.config.js`, `static.toml`, `LegacyLearnCorrelateLinksWithGHURLs.json`, `netlify.toml`, the `<!--startmeta` blocks in `.mdx` files, or the workflows `ingest.yml` and `daily-learn-link-check.yml`.