Implement Real User Monitoring (RUM) to capture actual user performance data including Core Web Vitals and page load times. Use when setting up user experience monitoring or tracking custom performance events. Trigger with phrases like "setup RUM", "track Core Web Vitals", or "monitor real user performance".
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: implementing-real-user-monitoring description: Implement Real User Monitoring (RUM) to capture actual user performance data including Core Web Vitals and page load times. Use when setting up user experience monitoring or tracking custom performance events. Trigger with phrases like "setup RUM", "track Core Web Vitals", or "monitor real user performance". version: 1.0.0 allowed-tools: Read, Write, Edit, Grep, Glob, Bash(npm:), Bash(rum:) license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
- performance
- monitoring
- real-user compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
Real User Monitoring
Implement Real User Monitoring (RUM) to capture Core Web Vitals, page load times, and custom performance events using Google Analytics, Datadog RUM, or New Relic.
Overview
This skill streamlines the process of setting up Real User Monitoring (RUM) for web applications. It guides you through the essential steps of choosing a platform, defining metrics, and implementing the tracking code to capture valuable user experience data.
How It Works
- Platform Selection: Helps you consider available RUM platforms (e.g., Google Analytics, Datadog RUM, New Relic).
- Instrumentation Design: Guides you in defining the key performance metrics to track, including Core Web Vitals and custom events.
- Tracking Code Implementation: Assists in implementing the necessary JavaScript code to collect and transmit performance data.
When to Use This Skill
This skill activates when you need to:
- Implement Real User Monitoring on a website or web application.
- Track Core Web Vitals (LCP, FID, CLS) to improve user experience.
- Monitor page load times (FCP, TTI, TTFB) for performance optimization.
Examples
Example 1: Setting up RUM for a new website
User request: "setup RUM for my new website"
The skill will:
- Guide the user through selecting a RUM platform.
- Provide code snippets for implementing basic tracking.
Example 2: Tracking custom performance metrics
User request: "I want to track how long it takes users to complete a purchase"
The skill will:
- Help define a custom performance metric for purchase completion time.
- Generate JavaScript code to track the metric.
Best Practices
- Privacy Compliance: Ensure compliance with privacy regulations (e.g., GDPR, CCPA) when collecting user data.
- Sampling: Implement sampling to reduce data volume and impact on performance.
- Error Handling: Implement robust error handling to prevent tracking code from breaking the website.
Integration
This skill can be used in conjunction with other monitoring and analytics tools to provide a comprehensive view of application performance.
Prerequisites
- Access to web application frontend code in ${CLAUDE_SKILL_DIR}/
- RUM platform account (Google Analytics, Datadog, New Relic)
- Understanding of Core Web Vitals metrics
- Privacy compliance documentation (GDPR, CCPA)
Instructions
- Select appropriate RUM platform for requirements
- Define key metrics to track (Core Web Vitals, custom events)
- Implement tracking code in application frontend
- Configure data sampling and privacy settings
- Set up dashboards for metric visualization
- Define alerts for performance degradation
Output
- RUM implementation code snippets
- Platform configuration documentation
- Custom event tracking examples
- Dashboard definitions for key metrics
- Privacy compliance checklist
Error Handling
If RUM implementation fails:
- Verify platform API credentials
- Check JavaScript bundle integration
- Validate metric collection permissions
- Review privacy consent configuration
- Ensure network connectivity for data transmission
Resources
- Core Web Vitals measurement guide
- RUM platform documentation
- Privacy compliance best practices
- Performance monitoring strategies
More by jeremylongshore
View allgenerating-docker-compose-files: This skill enables Claude to generate Docker Compose configurations for multi-container applications. It leverages best practices for production-ready deployments, including defining services, networks, volumes, health checks, and resource limits. Claude should use this skill when the user requests a Docker Compose file, specifies application architecture involving multiple containers, or mentions needs for container orchestration, environment variables, or persistent data management in a Docker environment. Trigger terms include "docker-compose", "docker compose file", "multi-container", "container orchestration", "docker environment", "service definition", "volume management", "network configuration", "health checks", "resource limits", and ".env files".
managing-environment-configurations: This skill enables Claude to manage environment configurations and secrets across different deployments using the environment-config-manager plugin. It is invoked when the user needs to generate, update, or retrieve configuration settings for various environments (e.g., development, staging, production). Use this skill when the user explicitly mentions "environment configuration," "secrets management," "deployment configuration," or asks to "generate config files". It helps streamline DevOps workflows by providing production-ready configurations based on best practices.
Automatically manages PostgreSQL backups with pgBackRest and Wasabi S3 storage when working with FairDB databases Activates when you request "fairdb backup manager" functionality.
generating-smart-commits: This skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.
