Bootstrap
Orchestrate first-time or repair setup for Vercel-linked repos: link project, install integrations, pull env, then run db and dev commands in a safe order.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill bootstrapWhat is this skill?
- Orchestrates linking, integration install, env pull, and first db/dev commands in documented safe order
- Detects setup via .env templates, package.json scripts, drizzle/prisma, and auth import patterns
- Chains to vercel-storage when legacy @vercel/postgres or @vercel/kv patterns appear
- Priority 8 metadata signals high relevance during repo setup and repair
- Aligns with Vercel and Next.js getting-started documentation sitemap
Adoption & trust: 229 installs on skills.sh; 187 GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Azure Deploymicrosoft/azure-skills
Azure Preparemicrosoft/azure-skills
Azure Storagemicrosoft/azure-skills
Azure Validatemicrosoft/azure-skills
Appinsights Instrumentationmicrosoft/azure-skills
Azure Resource Lookupmicrosoft/azure-skills
Journey fit
Primary fit
Bootstrapping managed databases, auth, and Vercel env is core build-time integration work before you can run or ship the app locally and in preview. Integrations subphase covers vercel link, integration add/install, env pull, and ordered db:* and dev scripts tied to Neon, Drizzle, Prisma, and auth stacks.
Common Questions / FAQ
Is Bootstrap safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Bootstrap
# Project Bootstrap Orchestrator Execute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete. ## Rules - Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified. - Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources. - Use provider CLIs only as fallback when Vercel integration flow is unavailable. - Never echo secret values in terminal output, logs, or summaries. ## Preflight 1. Confirm Vercel CLI is installed and authenticated. ```bash vercel --version vercel whoami ``` 2. Confirm repo linkage by checking `.vercel/project.json`. 3. If not linked, inspect available teams/projects before asking the user to choose: ```bash vercel teams ls vercel projects ls --scope <team> vercel link --yes --scope <team> --project <project> ``` 4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`. 5. Create local env file if missing: ```bash cp .env.example .env.local ``` ## Resource Setup: Postgres ### Preferred path (Vercel-managed Neon) 1. Read integration setup guidance: ```bash vercel integration guide neon ``` 2. Add Neon integration to the Vercel scope: ```bash vercel integration add neon --scope <team> ``` 3. Verify expected environment variable names exist in Vercel and pull locally: ```bash vercel env ls vercel env pull .env.local --yes ``` ### Fallback path 1 (Dashboard) 1. Provision Neon through the Vercel dashboard integration UI. 2. Re-run `vercel env pull .env.local --yes`. ### Fallback path 2 (Neon CLI) Use Neon CLI on