Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
Vercel production deployment checklist with rollback and promotion procedures.
Install Vercel Prod Checklist
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklist --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .claude/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.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/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .claude/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklistType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .agents/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .agents/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .cursor/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .cursor/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/vercel-prod-checklist--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .gemini/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .gemini/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklistInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .github/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .github/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-prod-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/vercel-prod-checklist .opencode/skills/vercel-prod-checklist && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vercel-prod-checklist" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/vercel-prod-checklist into .opencode/skills/vercel-prod-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-prod-checklist", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vercel-prod-checklist- GitHub stars
- 2.8k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 415 words
- Files
- 4 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Vercel production deployment checklist with rollback and promotion procedures.
- Works in 6 steps: Pre-Deploy Verification → Production Deploy → Domain Configuration → …
- Deploying to production
- SKILL.md covers Overview, Prerequisites, Instructions and Production Checklist, plus 5 more sections
- Calls vercel, curl and npm; reaches api.vercel.com; needs VERCEL_TOKEN and API_SECRET
What it does
Vercel Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Vercel production deployment checklist with rollback and promotion procedures. Use when deploying to production, preparing for launch, or implementing go-live and instant rollback procedures. Trigger with phrases like "vercel production", "deploy vercel prod", "vercel go-live", "vercel launch checklist", "vercel promote".
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/errors.md`, `references/examples.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Deployment and Product launch strategy. It works with Vercel. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Deploying to production
- Preparing for launch
- Implementing go-live and instant rollback procedures
- With phrases like vercel production
Example prompts
- “vercel production”
- “deploy vercel prod”
- “vercel go-live”
- “/vercel-prod-checklist”
Requirements
- Node.js
- A credential in API_SECRET
- A credential in VERCEL_TOKEN
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Bash(vercel:*), Bash(curl:*), Grep
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBash(vercel:*)Bash(curl:*)Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
vercelcurlnpmjqnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.vercel.com
Also links to:
vercel.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
VERCEL_TOKENAPI_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Vercel Prod Checklist loads about 1.8k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 415 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 415 words, ~1,759 tokens.
Download SKILL.mdSave it as
.claude/skills/vercel-prod-checklist/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- vercel-prod-checklist
- description
- Vercel production deployment checklist with rollback and promotion procedures. Use when deploying to production, preparing for launch, or implementing go-live and instant rollback procedures. Trigger with phrases like "vercel production", "deploy vercel prod", "vercel go-live", "vercel launch checklist", "vercel promote".
- allowed-tools
- Read, Bash(vercel:*), Bash(curl:*), Grep
- compatibility
- Designed for Claude Code
- version
- 1.18.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, vercel, deployment, production, checklist
Vercel Prod Checklist
Overview
Complete pre-production checklist for Vercel deployments covering environment variables, domain configuration, performance, security, monitoring, and instant rollback procedures.
Prerequisites
- Staging deployment tested and verified
- Production domain DNS configured
- Production environment variables set
- Monitoring and alerting configured
Instructions
Step 1: Pre-Deploy Verification
# Verify production env vars are set
vercel env ls --environment=production
# Required production variables (example):
# DATABASE_URL — production database
# API_SECRET — production API key (type: sensitive)
# NEXT_PUBLIC_API_URL — public API endpoint
# SENTRY_DSN — error tracking
# Build locally to catch errors before deploying
vercel build --prod
# Run test suite
npm testStep 2: Production Deploy
# Option A: Deploy directly to production
vercel --prod
# Option B: Promote an existing preview deployment
vercel promote https://my-app-git-main-team.vercel.app
# Option C: Deploy via API
curl -X POST "https://api.vercel.com/v13/deployments" \
-H "Authorization: Bearer $VERCEL_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "my-app",
"target": "production",
"gitSource": {
"type": "github",
"repoId": "123456789",
"ref": "main",
"sha": "abc123"
}
}'Step 3: Domain Configuration
# Add production domain
vercel domains add yourdomain.com
# Verify domain DNS
vercel domains inspect yourdomain.com
# DNS setup for apex domain (yourdomain.com):
# A record → 76.76.21.21
# AAAA record → (Vercel provides)
# DNS setup for subdomain (www.yourdomain.com):
# CNAME → cname.vercel-dns.com
# SSL is automatically provisioned after DNS verificationStep 4: Post-Deploy Health Checks
# Verify production is responding
curl -sI https://yourdomain.com | head -5
# Test API endpoints
curl -s https://yourdomain.com/api/health | jq .
# Check SSL certificate
curl -vI https://yourdomain.com 2>&1 | grep "SSL certificate"
# Verify security headers
curl -sI https://yourdomain.com | grep -i "strict-transport\|x-frame\|x-content-type"
# Test from multiple regions (using Vercel's edge)
for region in iad1 sfo1 cdg1 hnd1; do
echo "Region: $region"
curl -s -H "x-vercel-ip-country: US" https://yourdomain.com/api/health
doneStep 5: Instant Rollback Procedure
# If something goes wrong — instant rollback (no rebuild needed)
vercel rollback
# Or rollback to a specific deployment
vercel rollback dpl_xxxxxxxxxxxx
# Or via API
curl -X POST "https://api.vercel.com/v9/projects/my-app/promote" \
-H "Authorization: Bearer $VERCEL_TOKEN" \
-H "Content-Type: application/json" \
-d '{"deploymentId": "dpl_previous_good_deployment"}'
# Verify rollback succeeded
vercel ls --prod
curl -s https://yourdomain.com/api/healthStep 6: Configure Function Regions and Limits
// vercel.json — production optimization
{
"regions": ["iad1"],
"functions": {
"api/**/*.ts": {
"memory": 1024,
"maxDuration": 30
},
"api/heavy-compute.ts": {
"memory": 3008,
"maxDuration": 60
}
}
}Production Checklist
Build & Deploy
-
npm run buildsucceeds locally - All tests passing
- No TypeScript errors (
npx tsc --noEmit) - Preview deployment tested by team
-
vercel --prodor promotion executed
Environment Variables
- All required vars set for Production environment
- Secrets typed as
sensitive(hidden in logs) - No
NEXT_PUBLIC_prefix on secrets - Database URLs point to production instances
Domain & SSL
- Custom domain added and DNS verified
- SSL certificate auto-provisioned and valid
-
wwwsubdomain redirects correctly - HSTS header enabled
Security
- Security headers configured (CSP, X-Frame-Options, etc.)
- Preview deployment protection enabled
- API routes require authentication
- CORS configured for production origins only
Performance
- Function regions set closest to your database
-
maxDurationset appropriately per function - Cache-Control headers configured
- Bundle size within budget (check with
vercel inspect) - Core Web Vitals in green (LCP < 2.5s, CLS < 0.1)
Monitoring
- Error tracking configured (Sentry, Datadog, etc.)
- Vercel Analytics enabled in dashboard
- Runtime logs accessible
- Alert on error rate spikes
Rollback
- Previous production deployment identified for rollback
-
vercel rollbacktested in staging - Team knows rollback procedure
Output
- Production deployment live on custom domain
- Health checks passing
- Security headers verified
- Rollback procedure documented and tested
Show full SKILL.md (162 more words)Show less
Error Handling
| Error | Cause | Solution |
|---|---|---|
DEPLOYMENT_BLOCKED | Branch protection or deployment freeze | Check team settings in dashboard |
| SSL not provisioned | DNS not propagated | Wait for DNS propagation, verify records |
| Env var undefined | Not scoped to Production | Add via vercel env add <key> production |
| Function cold starts in prod | No warm-up traffic | Enable concurrency scaling or use edge functions |
| Rollback fails | Previous deployment expired | Redeploy from known good commit |
Examples
Execute a production readiness check with a tested reversal
Before release, record the exact candidate and prior deployment IDs, verify Production-only variable names and domain configuration, and run authenticated synthetic checks that do not mutate customer data. Promote only through the protected release workflow while watching health and error thresholds. If a threshold fails, roll back to the recorded deployment, verify recovery, and leave the candidate available for diagnosis rather than attempting live fixes under pressure.
Resources
Next Steps
For version upgrades, see vercel-upgrade-migration.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/.curated/vercel-prod-checklist of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/errors.md
- references/examples.md
- references/implementation.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Vercel Prod Checklist 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vercel Prod Checklist this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Use Vercel Actionamondnet/vercel-action | 764 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Deployments Cicdvercel/vercel-plugin | 301 | 1 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Shipping And Launchdzhalaevd/Donatello | 135 | 5 repos | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Deploy Release Testvercel/next.js | 143k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Use Vercel Action
amondnet/vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
Shipping And Launch
dzhalaevd/Donatello
Prepares production launches. An agent skill from dzhalaevd/Donatello.
- Official
Deploy Release Test
vercel/next.js
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.
Env Manager
bobmatnyc/claude-mpm
Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Works with
Categories
Questions about Vercel Prod Checklist
What does Vercel Prod Checklist do?
Vercel production deployment checklist with rollback and promotion procedures. Vercel Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Vercel production deployment checklist with rollback and promotion procedures.
When should I use Vercel Prod Checklist?
Vercel Prod Checklist fits situations like: deploying to production; preparing for launch; implementing go-live and instant rollback procedures; with phrases like vercel production.
How do I install Vercel Prod Checklist in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a claude-code`. Or copy the skill folder (skills/.curated/vercel-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vercel-prod-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Vercel Prod Checklist in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -a codex`. Or copy the skill folder (skills/.curated/vercel-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vercel-prod-checklist in your project. Codex loads it when a task matches its description.
Can I use Vercel Prod Checklist 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 jeremylongshore/tons-of-skills-marketplace --skill vercel-prod-checklist -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-prod-checklist, .gemini/skills/vercel-prod-checklist, .github/skills/vercel-prod-checklist and .opencode/skills/vercel-prod-checklist in your project.
What does Vercel Prod Checklist need to run?
Going by SKILL.md and its folder, Vercel Prod Checklist needs the command-line tools its instructions call (vercel, curl, npm, jq and npx) and credentials named VERCEL_TOKEN and API_SECRET. Our summary lists: Node.js; A credential in API_SECRET; A credential in VERCEL_TOKEN. Its frontmatter pre-approves these tools: Read, Bash(vercel:*), Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.
Does Vercel Prod Checklist access the network?
SKILL.md names 2 domains. In commands or code: api.vercel.com; the agent is likely to contact it when it follows the instructions. As links in the text: vercel.com. This is read from the text; nothing was executed.
Is Vercel Prod Checklist safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vercel Prod Checklist use?
Vercel Prod Checklist 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 Prod Checklist use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 740 tokens, read only when the agent opens those files.
What are the alternatives to Vercel Prod Checklist?
Skills that share tags, products or a category with Vercel Prod Checklist: Vercel (remotion-dev/remotion, 63k stars), Use Vercel Action (amondnet/vercel-action, 764 stars), Deployments Cicd (vercel/vercel-plugin, 301 stars) and Shipping And Launch (dzhalaevd/Donatello, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vercel Prod Checklist?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.