New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vercel Debug Bundle

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Collect Vercel debug evidence for support tickets and troubleshooting.

MITAuto-check passedSales & Support

Install Vercel Debug Bundle

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-debug-bundle -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-debug-bundle --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/vercel-debug-bundle .claude/skills/vercel-debug-bundle && 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-debug-bundle
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
337 words
Files
4 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Collect Vercel debug evidence for support tickets and troubleshooting.

  • Works in 6 steps: Collect Deployment Information → Collect Function Logs → Collect Build Output → …
  • Encountering persistent issues
  • SKILL.md covers Overview, Current State, Prerequisites and Instructions, plus 7 more sections
  • Calls vercel, jq and curl; reaches api.vercel.com and vercel-status.com; needs VERCEL_TOKEN

What it does

Vercel Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect Vercel debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vercel problems. Trigger with phrases like "vercel debug", "vercel support bundle", "collect vercel logs", "vercel diagnostic".

Its SKILL.md is about 1.7k 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 Sales & Support, covering Customer support. 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

  • Encountering persistent issues
  • Preparing support tickets
  • Collecting diagnostic information for Vercel problems
  • With phrases like vercel debug

Example prompts

  • “vercel debug”
  • “vercel support bundle”
  • “collect vercel logs”
  • “/vercel-debug-bundle”

Requirements

  • Node.js
  • A credential in VERCEL_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Bash(vercel:*), Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Collect Deployment Information
  2. Collect Function Logs
  3. Collect Build Output
  4. Collect Environment State (Redacted)
  5. Check Vercel Status Page
  6. Package the Bundle

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:

    • Read
    • Bash(vercel:*)
    • Bash(curl:*)
    • Bash(tar:*)
    • Bash(jq:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • vercel
    • jq
    • curl
    • node
    • npm
    • apt
    • brew

    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
    • vercel-status.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_TOKEN

    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 Debug Bundle loads about 1.7k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 337 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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). 337 words, ~1,679 tokens.

Download SKILL.mdSave it as .claude/skills/vercel-debug-bundle/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
vercel-debug-bundle
description
Collect Vercel debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vercel problems. Trigger with phrases like "vercel debug", "vercel support bundle", "collect vercel logs", "vercel diagnostic".
allowed-tools
Read, Bash(vercel:*), Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep
compatibility
Designed for Claude Code
version
1.18.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, vercel, debugging, support

Vercel Debug Bundle

Overview

Collect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting.

Current State

!vercel --version 2>/dev/null || echo 'Vercel CLI not installed' !node --version 2>/dev/null || echo 'Node.js N/A'

Prerequisites

  • Vercel CLI installed and authenticated
  • Access to the affected deployment
  • jq for JSON processing (recommended)

Instructions

Step 1: Collect Deployment Information
bash
#!/usr/bin/env bash
set -euo pipefail

DEPLOY_URL="${1:-$(vercel ls --json 2>/dev/null | jq -r '.[0].url')}"
BUNDLE_DIR="vercel-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Collecting debug bundle for: $DEPLOY_URL ==="

# Deployment inspection
vercel inspect "$DEPLOY_URL" > "$BUNDLE_DIR/inspect.txt" 2>&1 || true

# Deployment details via API
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \
  | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \
  > "$BUNDLE_DIR/deployment.json" 2>/dev/null || true
Step 2: Collect Function Logs
bash
# Recent function logs (last 100 entries)
vercel logs "$DEPLOY_URL" --output=short --limit=100 \
  > "$BUNDLE_DIR/function-logs.txt" 2>&1 || true

# Function logs via API with filtering
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v2/deployments/$DEPLOY_URL/events?limit=100&direction=backward" \
  | jq '.[] | {timestamp: .created, type, text}' \
  > "$BUNDLE_DIR/events.json" 2>/dev/null || true
Step 3: Collect Build Output
bash
# Build logs
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \
  | jq '.build' > "$BUNDLE_DIR/build-info.json" 2>/dev/null || true

# List all functions in the deployment
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \
  | jq '.routes, .functions' > "$BUNDLE_DIR/routes-functions.json" 2>/dev/null || true
Step 4: Collect Environment State (Redacted)
bash
# Environment variable names only (no values)
vercel env ls > "$BUNDLE_DIR/env-vars-list.txt" 2>&1 || true

# Project configuration (redacted)
if [ -f "vercel.json" ]; then
  cp vercel.json "$BUNDLE_DIR/vercel.json"
fi

# Package versions
if [ -f "package.json" ]; then
  jq '{name, version, dependencies, devDependencies, engines}' package.json \
    > "$BUNDLE_DIR/package-summary.json" 2>/dev/null || true
fi

# Node.js and CLI versions
{
  echo "node: $(node --version 2>/dev/null || echo 'N/A')"
  echo "npm: $(npm --version 2>/dev/null || echo 'N/A')"
  echo "vercel: $(vercel --version 2>/dev/null || echo 'N/A')"
  echo "os: $(uname -a)"
  echo "date: $(date -u +%Y-%m-%dT%H:%M:%SZ)"
} > "$BUNDLE_DIR/environment.txt"
Step 5: Check Vercel Status Page
bash
# Vercel platform status
curl -s "https://www.vercel-status.com/api/v2/summary.json" \
  | jq '{status: .status.description, components: [.components[] | {name, status}]}' \
  > "$BUNDLE_DIR/platform-status.json" 2>/dev/null || true
Step 6: Package the Bundle
bash
# Create archive — excludes secrets
tar czf "${BUNDLE_DIR}.tar.gz" "$BUNDLE_DIR"
echo "Debug bundle created: ${BUNDLE_DIR}.tar.gz"
echo "Contents:"
ls -la "$BUNDLE_DIR"/

Bundle Contents Reference

FileContents
inspect.txtDeployment inspection output
deployment.jsonDeployment state, target, errors
function-logs.txtRecent function invocation logs
events.jsonDeployment event timeline
build-info.jsonBuild configuration and output
routes-functions.jsonRoute and function mapping
env-vars-list.txtEnvironment variable names (no values)
vercel.jsonProject configuration
package-summary.jsonDependencies and versions
environment.txtSystem info (Node, CLI, OS)
platform-status.jsonVercel platform status at time of capture

Support Ticket Template

Subject: [Project: my-app] FUNCTION_INVOCATION_TIMEOUT on /api/endpoint

Environment:
- Plan: Pro
- Framework: Next.js 14
- Region: iad1
- Node.js: 18.x

Issue:
[Describe the error, when it started, and the user impact]

Steps to Reproduce:
1. Deploy commit abc123
2. Send POST to /api/endpoint with body > 1MB
3. Function times out after 60s

Expected: 200 response within 5s
Actual: 504 after 60s

Deployment URL: https://my-app-xxx.vercel.app
Debug bundle: [attached]

Output

  • vercel-debug-YYYYMMDD-HHMMSS.tar.gz archive
  • All secrets redacted (env var values never captured)
  • Platform status snapshot included
  • Ready to attach to Vercel support ticket

Error Handling

ErrorCauseSolution
vercel inspect failsDeployment deleted or token expiredUse API directly with curl
jq: command not foundjq not installedapt install jq or brew install jq
Empty function logsFunction not invoked or log retention expiredCheck Observability tab in dashboard
VERCEL_TOKEN not setNot authenticated for API callsExport token or run vercel login

Examples

Prepare a support bundle that is safe to share

Copy the deployment ID, timestamps, status-page snapshot, and a redacted request trace into a new temporary directory. Before archiving, scan the bundle for tokens, cookies, email addresses, and raw request bodies; replace values with stable placeholders so support can correlate events without receiving secrets. Encrypt or use the approved support attachment channel, set an expiry for the local bundle, and confirm the original deployment is still retained for follow-up.

Resources

Next Steps

For rate limit issues, see vercel-rate-limits.

© 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-debug-bundle 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 Debug Bundle 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 Debug Bundle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vercel Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT
Supporthaacked/dotfiles134—~2.9kAutomated safety check: PassNone
Company Brain Company QAtopoteretes/cognee32k—~750Automated safety check: NotesApache-2.0
Shopify Admin Address Correction40RTY-ai/shopify-admin-skills194—~1.5kAutomated safety check: PassMIT
Support Ticket Triagezapier/gtm-cheat-codes342—~670Automated safety check: PassMIT
Customer Servicevivy-yi/xiaohongshu-skills481—~6.7kAutomated safety check: PassNone

Similar skills

  • Support

    haacked/dotfiles

    Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.

    134 GitHub stars~2.9k tokensUpdated today
    Sales & SupportAuto-check passed

  • Company Brain Company QA

    topoteretes/cognee

    Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together.

    32k GitHub stars~750 tokensUpdated today
    Sales & SupportAuto-check: notes

  • Shopify Admin Address Correction

    40RTY-ai/shopify-admin-skills

    Update the shipping address on an unfulfilled order before it ships.

    194 GitHub stars~1.5k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • Support Ticket Triage

    zapier/gtm-cheat-codes

    Official

    Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.

    342 GitHub stars~670 tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed

  • Customer Service

    vivy-yi/xiaohongshu-skills

    A skill your agent uses when handling customer inquiries on Xiaohongshu, responding to product questions, managing complaints and returns, building customer relationships through service, or…

    481 GitHub stars~6.7k tokensUpdated 8 mo ago
    Sales & SupportAuto-check passed

  • Experience Portal Create

    forcedotcom/sf-skills

    Create / provision / set up a NEW Digital Experience (Communities) / Experience Cloud site — employee service, IT support, help desk, HR, customer, and partner portals — via the headless-360 MCP…

    1.1k GitHub stars~7.2k tokensUpdated today
    Sales & SupportAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing 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.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • 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.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • 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.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Vercel Debug Bundle

What does Vercel Debug Bundle do?

Collect Vercel debug evidence for support tickets and troubleshooting. Vercel Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect Vercel debug evidence for support tickets and troubleshooting.

When should I use Vercel Debug Bundle?

Vercel Debug Bundle fits situations like: encountering persistent issues; preparing support tickets; collecting diagnostic information for Vercel problems; with phrases like vercel debug.

How do I install Vercel Debug Bundle in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/vercel-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vercel-debug-bundle in your project. Claude Code loads it when a task matches its description.

How do I install Vercel Debug Bundle in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/vercel-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vercel-debug-bundle in your project. Codex loads it when a task matches its description.

Can I use Vercel Debug Bundle 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-debug-bundle -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-debug-bundle, .gemini/skills/vercel-debug-bundle, .github/skills/vercel-debug-bundle and .opencode/skills/vercel-debug-bundle in your project.

What does Vercel Debug Bundle need to run?

Going by SKILL.md and its folder, Vercel Debug Bundle needs the command-line tools its instructions call (vercel, jq, curl, node, npm and apt) and credentials named VERCEL_TOKEN. Our summary lists: Node.js; A credential in VERCEL_TOKEN. Its frontmatter pre-approves these tools: Read, Bash(vercel:*), Bash(curl:*), Bash(tar:*), Bash(jq:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Vercel Debug Bundle access the network?

SKILL.md names 3 domains. In commands or code: api.vercel.com and vercel-status.com; the agent is likely to contact these when it follows the instructions. As links in the text: vercel.com. This is read from the text; nothing was executed.

Is Vercel Debug Bundle 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 Debug Bundle use?

Vercel Debug Bundle 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 Debug Bundle use?

About 1.7k tokens (SKILL.md is roughly 6.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 647 tokens, read only when the agent opens those files.

What are the alternatives to Vercel Debug Bundle?

Skills that share tags, products or a category with Vercel Debug Bundle: Support (haacked/dotfiles, 134 stars), Company Brain Company QA (topoteretes/cognee, 32k stars), Shopify Admin Address Correction (40RTY-ai/shopify-admin-skills, 194 stars) and Support Ticket Triage (zapier/gtm-cheat-codes, 342 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vercel Debug Bundle?

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.