vercel-observability — Claude Code skill: what it does, how to install
Equips coding assistants to monitor Core Web Vitals, inspect runtime logs, and configure alert thresholds on Vercel. Ideal for debugging live production issues.
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a claude-codeWhat vercel-observability does
The skill supplies context for handling telemetry on Vercel infrastructure. It guides the model through enabling Web Analytics for visitor counts, collecting Core Web Vitals with Speed Insights, and inspecting production logs. When request latency spikes, the agent references tracing rules to isolate backend bottlenecks.
Companion skills are completely optional. Packages covering deployment rollbacks or serverless function runtimes can complement the setup, but the core telemetry rules work alone. You get targeted guidance for logging and operational alerts without cluttering the prompt.
What it helps with
- track Core Web Vitals using Speed Insights
- debug runtime exceptions within Vercel logs
- measure application traffic via Web Analytics
- set operational alert thresholds for downtime
Example prompts for the agent
- Help me add Speed Insights to my Vercel project to monitor Core Web Vitals.
- Check our Vercel runtime logs to find why the checkout endpoint failed.
- Configure alert thresholds for server errors on our Vercel deployment.
How to install vercel-observability
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a claude-code2Manually: put the files in place
~/.claude/skills/vercel-observability/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vercel-observability/
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a codex2Manually: put the files in place
.agents/skills/vercel-observability/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a cursor2Manually: put the files in place
.cursor/skills/vercel-observability/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bobmatnyc/claude-mpm-skills vercel-observability2Manually: put the files in place
.github/skills/vercel-observability/SKILL.md1Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a gemini-cli2Platform CLI
gemini skills install https://github.com/bobmatnyc/claude-mpm-skills --path toolchains/platforms/deployment/vercel-observabilityManually: put the files in place
.devin/skills/vercel-observability/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vercel-observability
How do I install vercel-observability in Claude Code?
Run npx skills add bobmatnyc/claude-mpm-skills --skill vercel-observability -a claude-code. The file will be placed in ~/.claude/skills/vercel-observability/SKILL.md.
What does vercel-observability do?
It provides procedural guidance for tracking performance, reading runtime logs, and setting alerts across Vercel deployments.
Do I need other Vercel skills for this to work?
No, companion skills like vercel-functions-runtime are strictly optional. This skill operates independently without extra dependencies.
Source text
SKILL.md · MIT
---
name: vercel-observability
description: Vercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel.
user-invocable: false
disable-model-invocation: true
progressive_disclosure:
entry_point:
summary: "Vercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel."
when_to_use: "When working with vercel-observability or related functionality."
quick_start: "1. Review the core concepts below. 2. Apply patterns to your use case. 3. Follow best practices for implementation."
---
# Vercel Observability Skill
---
progressive_disclosure:
entry_point:
summary: "Vercel observability: analytics, Speed Insights, logs, tracing, alerts, and performance monitoring."
when_to_use:
- "When monitoring application performance"
- "When debugging production issues"
- "When setting alerts for availability and errors"
quick_start:
- "Enable Web Analytics"
- "Enable Speed Insights"
- "Review logs and tracing"
- "Configure alerts"
token_estimate:
entry: 90-110
full: 3600-4700
---
## Overview
Vercel observability covers analytics, performance insights, and debugging tools for production workloads.
## Web Analytics
- Enable analytics for traffic and usage insights.
## Speed Insights
- Measure Core Web Vitals and performance metrics.
- Track real-world performance changes.
## Logs and Tracing
- Use logs for runtime errors and behavior.
- Use tracing for request performance and diagnostics.
## Alerts
- Configure alerts for operational thresholds.
## Complementary Skills
When using this skill, consider these related skills (if deployed):
- **vercel-deployments-builds**: Deployment visibility and rollback.
- **vercel-functions-runtime**: Function logs and runtime debugging.
- **vercel-networking-domains**: CDN and routing performance.
*Note: Complementary skills are optional. This skill is fully functional without them.*
## Resources
**Vercel Docs**:
- Analytics: https://vercel.com/docs/analytics
- Speed Insights: https://vercel.com/docs/speed-insights
- Logs: https://vercel.com/docs/logs
- Tracing: https://vercel.com/docs/tracing
- Alerts: https://vercel.com/docs/alerts
- Observability: https://vercel.com/docs/observability
© bobmatnyc · MIT · bobmatnyc/claude-mpm-skills
