vercel-speed-audit

What This Skill Does

The vercel-speed-audit skill provides a systematic framework for analyzing and optimizing Vercel deployment pipelines. It moves beyond generic advice by offering a triage-based checklist that scales with your project's current build performance. Whether you are dealing with massive build times in a monorepo or trying to shave seconds off a static site deployment, this skill acts as an architectural consultant that identifies bottlenecks such as barrel file overhead, dependency bloat, and inefficient caching strategies.

Installation

To integrate this skill into your OpenClaw environment, run the following command in your terminal: clawhub install openclaw/skills/skills/brennerspear/vercel-speed-audit

Use Cases

• Project Onboarding: Automate the configuration of build settings for new repositories to ensure optimal performance from the first commit.
• Performance Regression Troubleshooting: When build times spike unexpectedly, use the skill to audit recent changes against the checklist of high-impact optimizations.
• Cost & Resource Management: Determine if moving to a Pro plan is justified by identifying which high-impact features (like Turbo Build Machines or Concurrent Builds) would solve your current pipeline bottlenecks.
• Incident Response: Utilize the instant rollback checklist to ensure that your team can recover from production failures without waiting for a fresh, long build process.

Example Prompts

1. "Run a Vercel speed audit on this project. I'm seeing 90-second build times and I want to know where to start."
2. "I'm setting up a new Next.js project. Can you provide the checklist for initial Vercel configuration to ensure maximum build speed?"
3. "My project is auth-gated and uses SvelteKit. Which items from the vercel-speed-audit checklist should I ignore and which are most important?"

Tips & Limitations

• Triage is Key: Do not attempt all ten optimizations simultaneously. Follow the provided triage decision tree to focus on the highest ROI tasks based on your current build duration.
• Dashboard Dependency: Note that the most impactful features (Turbo Build Machines, Concurrent Builds, and Prioritized Builds) require a Pro plan and must be toggled manually via the Vercel Dashboard, as they are not accessible via CLI.
• ISR Limitations: If your application relies on per-user authentication, skip the ISR (#9) recommendations to avoid caching sensitive data for the wrong users.
• Codebase Complexity: The barrel file audit (#6) is most effective for large, component-heavy libraries. In smaller projects, the impact may be negligible.