Agent skill

Vercel Deployments

by sickn33 in sickn33/agentic-awesome-skills

Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.

MITAuto-check: notesDevOps & Cloud

Install Vercel Deployments

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill vercel-deployments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills vercel-deployments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vercel-deployments .claude/skills/vercel-deployments && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vercel-deployments
GitHub stars
47k
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
256 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.

  • Tasks that involve Deployment
  • SKILL.md covers When to Use This Skill, Prerequisites, Quick Start and Project Configuration, plus 9 more sections
  • Calls vercel and npm; needs STRIPE_SECRET_KEY and SECRET_KEY
  • Tasks that involve Serverless

What it does

Vercel Deployments is an agent skill from sickn33/agentic-awesome-skills. Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled.

It sits in DevOps & Cloud, covering Deployment, Serverless and LLM guardrails. It works with Vercel and GitHub Actions. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Deployment
  • Tasks that involve Serverless
  • Tasks that involve LLM guardrails

Example prompts

  • “/vercel-deployments”

Requirements

  • Node.js
  • A credential in SECRET_KEY
  • A credential in STRIPE_SECRET_KEY
  • Compatibility (from SKILL.md): Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled.

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • vercel
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use vercel and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • STRIPE_SECRET_KEY
    • SECRET_KEY
    • VERCEL_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled.

    From compatibility in the SKILL.md frontmatter.

Context cost

Vercel Deployments loads about 1.9k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 256 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:56
    vercel env pull .env.local
  • NoteMentions a .env fileSKILL.md:105
    # Pull to local .env.local
  • NoteMentions a .env fileSKILL.md:106
    vercel env pull .env.local

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 256 words, ~1,921 tokens.

Download SKILL.mdSave it as .claude/skills/vercel-deployments/SKILL.md (or your agent's skills folder).
name
vercel-deployments
description
Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.
compatibility
Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled.
category
devops
risk
critical
source
https://github.com/BagelHole/DevOps-Security-Agent-Skills
source_repo
BagelHole/DevOps-Security-Agent-Skills
source_type
community
date_added
2026-09-20
license
MIT
license_source
https://github.com/BagelHole/DevOps-Security-Agent-Skills/blob/main/LICENSE
metadata.author
devops-skills
metadata.version
1.0

Vercel Deployments

Ship web apps quickly with preview environments and managed edge infrastructure.

When to Use This Skill

Use this skill when:

  • Deploying Next.js, SvelteKit, Nuxt, or static sites
  • Setting up preview environments for every PR
  • Configuring edge functions and serverless APIs
  • Managing environment variables across preview/production
  • Setting up custom domains and redirects

Prerequisites

  • Node.js 18+
  • Vercel account (free tier works for personal projects)
  • Git repository (GitHub, GitLab, or Bitbucket)

Quick Start

bash
# Install CLI
npm i -g vercel

# Login and link project
vercel login
vercel link

# Deploy to preview
vercel

# Deploy to production
vercel --prod

# Pull environment variables locally
vercel env pull .env.local

Project Configuration

json
// vercel.json
{
  "framework": "nextjs",
  "buildCommand": "npm run build",
  "outputDirectory": ".next",
  "installCommand": "npm ci",
  "regions": ["iad1", "sfo1", "cdg1"],
  "headers": [
    {
      "source": "/api/(.*)",
      "headers": [
        { "key": "Cache-Control", "value": "no-store" },
        { "key": "X-Content-Type-Options", "value": "nosniff" }
      ]
    },
    {
      "source": "/(.*)",
      "headers": [
        { "key": "X-Frame-Options", "value": "DENY" },
        { "key": "Strict-Transport-Security", "value": "max-age=63072000; includeSubDomains" }
      ]
    }
  ],
  "redirects": [
    { "source": "/blog/:slug", "destination": "/posts/:slug", "permanent": true }
  ],
  "rewrites": [
    { "source": "/api/v1/:path*", "destination": "https://api.example.com/:path*" }
  ]
}

Environment Variables

bash
# Add environment variables
vercel env add DATABASE_URL production
vercel env add DATABASE_URL preview
vercel env add NEXT_PUBLIC_API_URL production

# List all env vars
vercel env ls

# Pull to local .env.local
vercel env pull .env.local

# Remove an env var
vercel env rm SECRET_KEY production
Environment Separation Pattern
bash
# Production — real credentials
vercel env add DATABASE_URL production <<< "postgresql://prod-host:5432/app"
vercel env add STRIPE_SECRET_KEY production

# Preview — staging/test credentials
vercel env add DATABASE_URL preview <<< "postgresql://staging-host:5432/app"
vercel env add STRIPE_SECRET_KEY preview   # Use test mode key

# Development — local values
vercel env add DATABASE_URL development <<< "postgresql://localhost:5432/app"

Edge Functions

typescript
// app/api/geo/route.ts — Edge API route (Next.js App Router)
import { NextRequest } from 'next/server';

export const runtime = 'edge';

export function GET(request: NextRequest) {
  const country = request.geo?.country || 'US';
  const city = request.geo?.city || 'Unknown';

  return Response.json({
    country,
    city,
    region: request.geo?.region,
    timestamp: new Date().toISOString(),
  });
}
typescript
// middleware.ts — Edge middleware for auth/redirects
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';

export function middleware(request: NextRequest) {
  // Block non-US traffic from admin
  if (request.nextUrl.pathname.startsWith('/admin')) {
    if (request.geo?.country !== 'US') {
      return NextResponse.redirect(new URL('/blocked', request.url));
    }
  }

  // Add security headers
  const response = NextResponse.next();
  response.headers.set('X-Request-Id', crypto.randomUUID());
  return response;
}

export const config = {
  matcher: ['/admin/:path*', '/api/:path*'],
};

GitHub Actions Integration

yaml
# .github/workflows/preview.yml
name: Vercel Preview
on: pull_request

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'

      - run: npm ci
      - run: npm run lint
      - run: npm run test

      - name: Deploy to Vercel Preview
        id: deploy
        run: |
          npm i -g vercel
          URL=$(vercel --token ${{ secrets.VERCEL_TOKEN }} --yes)
          echo "url=$URL" >> "$GITHUB_OUTPUT"

      - name: Comment PR with preview URL
        uses: actions/github-script@v7
        with:
          script: |
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: `Preview deployed: ${{ steps.deploy.outputs.url }}`
            });

CLI Commands Reference

bash
# Deployments
vercel                          # Deploy to preview
vercel --prod                   # Deploy to production
vercel rollback                 # Rollback last production deploy
vercel promote <url>            # Promote preview to production

# Domains
vercel domains add example.com
vercel domains ls
vercel certs ls

# Logs
vercel logs <deployment-url>
vercel logs <deployment-url> --follow

# Project management
vercel project ls
vercel project rm <name>

# Inspect deployment
vercel inspect <deployment-url>

Production Guardrails

  • Require preview checks before merge (GitHub branch protection)
  • Separate preview and production environment variables — never share API keys
  • Use branch protection with required deployment status checks
  • Monitor function duration and cold start behavior in Vercel Analytics
  • Set spend limits in Vercel dashboard to prevent cost surprises
  • Enable Vercel Firewall for DDoS and bot protection
  • Use vercel.json headers for security (CSP, HSTS, X-Frame-Options)

Monitoring & Analytics

bash
# Enable Speed Insights in Next.js
npm install @vercel/speed-insights

# Enable Web Analytics
npm install @vercel/analytics
typescript
// app/layout.tsx
import { Analytics } from '@vercel/analytics/react';
import { SpeedInsights } from '@vercel/speed-insights/next';

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Analytics />
        <SpeedInsights />
      </body>
    </html>
  );
}

Troubleshooting

IssueSolution
Build failsCheck vercel logs, verify Node.js version in engines field
Env vars missingRun vercel env pull, check variable scope (preview vs production)
Edge function timeoutEdge has 30s limit; move heavy work to serverless (no runtime = 'edge')
Cold starts slowUse edge runtime where possible, reduce bundle size
Domain not workingCheck DNS propagation, verify vercel domains configuration
  • github-actions (github-actions) — Automated deployment gates
  • cloudflare-pages (cloudflare-pages) — Alternative edge hosting
  • ssl-tls-management (ssl-tls-management) — Custom certificate setup

Limitations

  • Infrastructure commands can disrupt services: confirm target host/scope and have backups/snapshots before mutating state.
  • Docs-only import: upstream scripts and templates not bundled.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/vercel-deployments of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Vercel Deployments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vercel Deployments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vercel Deployments this skillsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: NotesMIT
Vercel DeploymentsBagelHole/DevOps-Security-Agent-Skills1.1k—~1.8kAutomated safety check: NotesMIT
Use Vercel Actionamondnet/vercel-action764—~2.7kAutomated safety check: PassMIT
Deployments Cicdvercel/vercel-plugin3011 repos~3kAutomated safety check: PassCustom licence
Deploy Release Testvercel/next.js143k—~1.2kAutomated safety check: PassMIT
Deploy Setupgarrytan/gstack136k—~11kAutomated safety check: NotesMIT

Similar skills

  • Vercel Deployments

    BagelHole/DevOps-Security-Agent-Skills

    Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.

    1.1k GitHub stars~1.8k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check: notes
  • Use Vercel Action

    amondnet/vercel-action

    Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.

    764 GitHub stars~2.7k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Deployments Cicd

    vercel/vercel-plugin

    Official

    Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.

    301 GitHub starsUsed in 1 repo~3k tokens
    DevOps & CloudAuto-check passed
  • Deploy Release Test

    vercel/next.js

    Official

    Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.

    143k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Deploy Setup

    garrytan/gstack

    Detects where an app deploys, its production URL and health checks, then saves the deploy configuration in CLAUDE.md for /land-and-deploy.

    136k GitHub stars~11k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • CI/CD Pipeline Principles

    irahardianto/awesome-agv

    Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.

    157 GitHub stars~2.7k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Categories

Questions about Vercel Deployments

What does Vercel Deployments do?

Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails. Vercel Deployments is an agent skill from sickn33/agentic-awesome-skills. Deploy frontend and full-stack apps on Vercel with previews, edge functions, environment promotion, and production guardrails.

When should I use Vercel Deployments?

Vercel Deployments fits situations like: tasks that involve Deployment; tasks that involve Serverless; tasks that involve LLM guardrails.

How do I install Vercel Deployments in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill vercel-deployments -a claude-code`. Or copy the skill folder (skills/vercel-deployments in sickn33/agentic-awesome-skills) into .claude/skills/vercel-deployments in your project. Claude Code loads it when a task matches its description.

How do I install Vercel Deployments in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill vercel-deployments -a codex`. Or copy the skill folder (skills/vercel-deployments in sickn33/agentic-awesome-skills) into .agents/skills/vercel-deployments in your project. Codex loads it when a task matches its description.

Can I use Vercel Deployments in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill vercel-deployments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vercel-deployments, .gemini/skills/vercel-deployments, .github/skills/vercel-deployments and .opencode/skills/vercel-deployments in your project.

What does Vercel Deployments need to run?

Going by SKILL.md and its folder, Vercel Deployments needs the command-line tools its instructions call (vercel and npm) and credentials named STRIPE_SECRET_KEY, SECRET_KEY and VERCEL_TOKEN. Our summary lists: Node.js; A credential in SECRET_KEY; A credential in STRIPE_SECRET_KEY. Compatibility (from SKILL.md): Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled..

Does Vercel Deployments access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vercel Deployments safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vercel Deployments use?

Vercel Deployments is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vercel Deployments use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vercel Deployments?

Skills that share tags, products or a category with Vercel Deployments: Vercel Deployments (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars), Use Vercel Action (amondnet/vercel-action, 764 stars), Deployments Cicd (vercel/vercel-plugin, 301 stars) and Deploy Release Test (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vercel Deployments?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.