What problem does it solve? Setting up a repository that depends on Vercel-linked resources often fails because developers run database migrations or dev servers before linking the project and pulling environment variables. This Skill enforces the correct bootstrap order so linking, env provisioning, and first-run commands happen safely. ## Core Features & Use Cases - Ordered Bootstrap Workflow: Verifies Vercel CLI authentication, links the project via vercel link, provisions Postgres through the Neon integration, and pulls env vars before any db:push or dev command runs. - Environment Verification: Compares required keys from .env.example, .env.sample, or .env.template against .env.local by name only, never exposing secret values. - Secure Secret Handling: Generates a high-entropy AUTH_SECRET, stores it in Vercel, and refreshes local env without printing the value. - Use Case: After cloning a Next.js repo with Drizzle and Neon, run the bootstrap flow to link the Vercel project, add the Neon integration, pull env vars, verify keys, then run db:push, db:seed, and dev with a structured result summary. ## Quick Start Ask the agent to bootstrap this repository by linking it to my Vercel project, provisioning the database, pulling environment variables, and starting the dev server in the correct order.