skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
oakoss/agent-skills95 installs

vercel-deployment

Vercel deployment configuration, preview environments, and edge functions. Covers vercel.json and vercel.ts configuration, rewrites, redirects, headers, environment variables across production/preview/development, custom domains, DNS setup, edge and serverless functions, Vercel CLI, GitHub Actions CI/CD, and monorepo deployments. Use when deploying to Vercel, configuring builds, setting up preview branches, managing environment variables, configuring custom domains, or using edge/serverless functions. Use for vercel, deploy, preview, edge-function, serverless, vercel-json, environment-variables, domains, monorepo.

How do I install this agent skill?

npx skills add https://github.com/oakoss/agent-skills --skill vercel-deployment
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides comprehensive documentation and configuration guidance for deploying applications to the Vercel platform. It covers project configuration, routing, environment variables, and CI/CD integration using official Vercel tools and best practices. No security issues were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    4/5 files flagged

What does this agent skill do?

Vercel Deployment

Overview

Vercel is a cloud platform for deploying frontend frameworks and serverless functions with automatic CI/CD, preview deployments, and edge infrastructure. Projects are configured via vercel.json (or programmatic vercel.ts), the Vercel dashboard, or the Vercel CLI.

When to use: Static sites, SSR frameworks (Next.js, SvelteKit, Nuxt), serverless API routes, edge functions, preview environments per pull request, monorepo deployments.

When NOT to use: Long-running backend processes (use containers), WebSocket servers (use dedicated infrastructure), heavy compute workloads (use cloud VMs), applications requiring persistent file system access.

Quick Reference

PatternTool / APIKey Points
Project configvercel.json or vercel.tsRoot of project, controls builds/routing/functions
Rewritesrewrites arrayRoutes request to destination, URL unchanged
Redirectsredirects arrayChanges URL, permanent: true for 301
Headersheaders arrayCustom response headers per path pattern
Clean URLscleanUrls: trueStrips .html extensions
Trailing slashtrailingSlash: falseConsistent URL format
Environment varsDashboard or vercel envScoped to production, preview, development
Custom domainsProject Settings > DomainsA record for apex, CNAME for subdomains
Preview deploysAutomatic per PREach push gets unique URL
Edge functionsexport const runtime = 'edge'V8 isolates, low latency, limited Node.js APIs
Serverless functionsapi/ directory or framework routesNode.js runtime, full API access
Deploy via CLIvercel or vercel --prodPreview by default, --prod for production
Promote deployvercel promote <url>Promote existing preview to production
MonorepoRoot directory setting per projectOne repo, multiple Vercel projects
GitHub integrationAutomatic on pushZero-config CI/CD with preview per branch
Programmatic configvercel.ts with @vercel/configTyped, dynamic configuration alternative
Fluid computeEnabled by default for new projectsMulti-request workers, 300s default duration
Rolling releasesIncremental rollout with monitoringGradual traffic shift with auto-rollback triggers
Firewall rulesvercel.json WAF configurationBlock threats via dashboard, API, or config file

Common Mistakes

MistakeCorrect Pattern
Using .env.production for preview-specific valuesUse Vercel environment variables scoped to preview environment
Expecting VERCEL_URL to include protocolPrepend https:// manually; use VERCEL_PROJECT_PRODUCTION_URL for stable production URL
Adding only apex domain without wwwAdd both yourdomain.com and www.yourdomain.com to avoid 404 on one
Using Node.js APIs in edge functionsEdge runtime uses V8 only; fs, path, process are unavailable
Exceeding 1024 static redirectsUse bulkRedirects property for large redirect sets (CSV/JSON/JSONL)
Creating QueryClient or fetching in edge without streamingUse streaming responses for long operations in edge functions
Setting maxDuration above plan limitFluid compute default: 300s; Hobby: 60s, Pro: 300s, Enterprise: 900s max
Conflicting DNS records for custom domainRemove duplicate A records; keep only the Vercel-pointing record
Not awaiting build in CI before deployUse vercel build then vercel deploy --prebuilt for reliable CI deploys
Ignoring monorepo root directory settingSet root directory per project in Vercel dashboard for correct builds

Delegation

  • Infrastructure review: Use Task agent to audit deployment configuration
  • Environment debugging: Use Explore agent to trace environment variable issues
  • CI/CD pipeline review: Use code-reviewer agent for GitHub Actions workflow review

References

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/oakoss/agent-skills/vercel-deployment">View vercel-deployment on skillZs</a>