Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Convert Next.js bundle analyzer data to NDJSON and explore it
OfficialMITAuto-check passed
Install Analyze Bundle
$ npx skills add vercel-labs/dev3000 --skill analyze-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/dev3000 analyze-bundle --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/vercel-labs/dev3000.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/analyze-bundle .claude/skills/analyze-bundle && 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 "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .claude/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundleType 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 vercel-labs/dev3000 --skill analyze-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/dev3000 analyze-bundle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/dev3000.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/analyze-bundle .agents/skills/analyze-bundle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .agents/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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 vercel-labs/dev3000 --skill analyze-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/dev3000 analyze-bundle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/dev3000.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/analyze-bundle .cursor/skills/analyze-bundle && 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 "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .cursor/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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/vercel-labs/dev3000.git --path .agents/skills/analyze-bundle--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 vercel-labs/dev3000 --skill analyze-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/dev3000 analyze-bundle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/dev3000.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/analyze-bundle .gemini/skills/analyze-bundle && 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 "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .gemini/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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 vercel-labs/dev3000 analyze-bundleInstalls 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 vercel-labs/dev3000 --skill analyze-bundle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/dev3000.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/analyze-bundle .github/skills/analyze-bundle && 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 "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .github/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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 vercel-labs/dev3000 --skill analyze-bundle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/dev3000 analyze-bundle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/dev3000.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/analyze-bundle .opencode/skills/analyze-bundle && 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 "analyze-bundle" agent skill from https://github.com/vercel-labs/dev3000/tree/main/.agents/skills/analyze-bundle into .opencode/skills/analyze-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-bundle", 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
analyze-bundle- GitHub stars
- 1.6k
- Token cost
- ~617 tokens
- SKILL.md length
- 108 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Convert Next.js bundle analyzer data to NDJSON and explore it
- SKILL.md covers Analyze artifacts, Output files and Browsing the output
- Calls jq
What it does
Analyze Bundle is an agent skill from vercel-labs/dev3000, published by the product's own GitHub organization. Convert Next.js bundle analyzer data to NDJSON and explore it
Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Next.js. The repository describes itself as: Captures your web app's complete development timeline - server logs, browser events, console messages, network requests, and automatic screenshots - in a unified, timestamped… The licence is MIT.
Example prompts
- “/analyze-bundle”
Requirements
- Pre-approved tools (allowed-tools): Bash(node *), Bash(head:*), Bash(tail:*), Bash(grep:*), Bash(jq:*), Read
What it can do on your machine
Read from SKILL.md and the folder at commit 3b945d7. 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:
Bash(node *)Bash(head:*)Bash(tail:*)Bash(grep:*)Bash(jq:*)Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze Bundle loads about 617 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 108 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 vercel-labs/dev3000 at commit 3b945d7, republished under its MIT licence (© vercel-labs). 108 words, ~617 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-bundle/SKILL.md (or your agent's skills folder).- name
- analyze-bundle
- description
- Convert Next.js bundle analyzer data to NDJSON and explore it
- allowed-tools
- Bash(node *), Bash(head:*), Bash(tail:*), Bash(grep:*), Bash(jq:*), Read
analyze-to-ndjson
Converts Next.js bundle analyzer binary .data files into grep/jq-friendly NDJSON.
Analyze artifacts
This workflow pre-generates analyzer artifacts in:
.next/diagnostics/analyze/ndjson/routes.ndjson.next/diagnostics/analyze/ndjson/sources.ndjson.next/diagnostics/analyze/ndjson/output_files.ndjson.next/diagnostics/analyze/ndjson/module_edges.ndjson.next/diagnostics/analyze/ndjson/modules.ndjson
Focus on reading these files and using their evidence to prioritize changes.
Output files
| File | What's in it |
|---|---|
modules.ndjson | Global module registry (id, ident, path) |
module_edges.ndjson | Module dependency graph (from, to, kind: sync/async) |
sources.ndjson | Per-route source tree with sizes and environment flags |
chunk_parts.ndjson | Granular size data: one line per (source, output_file) pair |
output_files.ndjson | Per-route output files with aggregated sizes |
routes.ndjson | Route-level summaries |
Browsing the output
Route overview
jq -s 'sort_by(-.total_compressed_size)' .next/diagnostics/analyze/ndjson/routes.ndjsonFind large sources
jq -s '
group_by(.full_path)
| map(max_by(.compressed_size))
| sort_by(-.compressed_size)
| .[0:10]
| .[] | {full_path, compressed_size, size, route}
' .next/diagnostics/analyze/ndjson/sources.ndjsonClient-side JS
grep '"client":true' .next/diagnostics/analyze/ndjson/sources.ndjson \
| grep '"js":true' \
| jq -s 'sort_by(-.compressed_size) | .[0:10] | .[] | {full_path, compressed_size}'Module dependencies
grep '"from":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .to
grep '"to":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .from
grep 'react-dom' .next/diagnostics/analyze/ndjson/modules.ndjson | jq '{id, path}'Output files for a route
grep '"route":"/"' .next/diagnostics/analyze/ndjson/output_files.ndjson \
| jq -s 'sort_by(-.total_compressed_size) | .[0:10] | .[] | {filename, total_compressed_size, num_parts}'Directory tree for a route
grep '"route":"/"' .next/diagnostics/analyze/ndjson/sources.ndjson \
| jq 'select(.parent_id == null)'© vercel-labs, 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 .agents/skills/analyze-bundle of vercel-labs/dev3000.
Open the folder on GitHubat commit 3b945d7
Compare with similar skills
Analyze 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze Bundle this skillvercel-labs/dev3000 | 1.6k | — | ~617 | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Sandbox Benchvercel/next.js | 143k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Next Dev Loopvercel/next.js | 143k | 9 repos | ~2.3k | Automated safety check: Pass | MIT | |
| AI SDKvercel-labs/ai-facts | 168 | 21 repos | ~1.2k | Automated safety check: Pass | None | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Sandbox Bench
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
- Official
Next Dev Loop
vercel/next.js
Verify Next.js runtime behavior after editing app code. An agent skill from vercel/next.js.
- Official
AI SDK
vercel-labs/ai-facts
Answer questions about the AI SDK and help build AI-powered features.
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
Chakra UI v3 Builder
chakra-ui/chakra-ui
Builds responsive, accessible Chakra UI v3 components and layouts, sets up Chakra in new or existing projects, and designs themes with tokens, semantic tokens and recipes.
More from vercel-labs/dev3000
Related
Works with
Questions about Analyze Bundle
What does Analyze Bundle do?
Convert Next.js bundle analyzer data to NDJSON and explore it. Analyze Bundle is an agent skill from vercel-labs/dev3000, published by the product's own GitHub organization.
How do I install Analyze Bundle in Claude Code?
Run `npx skills add vercel-labs/dev3000 --skill analyze-bundle -a claude-code`. Or copy the skill folder (.agents/skills/analyze-bundle in vercel-labs/dev3000) into .claude/skills/analyze-bundle in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Bundle in Codex?
Run `npx skills add vercel-labs/dev3000 --skill analyze-bundle -a codex`. Or copy the skill folder (.agents/skills/analyze-bundle in vercel-labs/dev3000) into .agents/skills/analyze-bundle in your project. Codex loads it when a task matches its description.
Can I use Analyze 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 vercel-labs/dev3000 --skill analyze-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/analyze-bundle, .gemini/skills/analyze-bundle, .github/skills/analyze-bundle and .opencode/skills/analyze-bundle in your project.
What does Analyze Bundle need to run?
Going by SKILL.md and its folder, Analyze Bundle needs the command-line tools its instructions call (jq). Its frontmatter pre-approves these tools: Bash(node *), Bash(head:*), Bash(tail:*), Bash(grep:*), Bash(jq:*), Read.
Does Analyze Bundle access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyze 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 Analyze Bundle use?
Analyze Bundle is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze Bundle use?
About 617 tokens (SKILL.md is roughly 2.5k 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 Analyze Bundle?
Skills that share tags, products or a category with Analyze Bundle: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Sandbox Bench (vercel/next.js, 143k stars), Next Dev Loop (vercel/next.js, 143k stars) and AI SDK (vercel-labs/ai-facts, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Bundle?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/dev3000, which has 1,582 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: vercel-labs/dev3000 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.