vercel-observability
Vercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel.
Works with
---
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.
license: MIT
---
# 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/observabilityMore Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
