implementing-real-user-monitoring
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill implementing-real-user-monitoringImplement 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".
60%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 96 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'implementing-real-user-monitoring' | Pass |
description_field | 'description' field is valid (309 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
20%This skill content is primarily descriptive rather than instructive, explaining what RUM is and what the skill does rather than providing actionable implementation guidance. It lacks any executable code examples despite being a technical implementation skill, and contains significant redundancy across multiple sections that describe the same concepts. The content would benefit from being condensed to essential guidance with concrete, copy-paste ready code snippets.
Suggestions
- Replace the abstract 'Examples' section with actual executable JavaScript code for implementing Core Web Vitals tracking (e.g., using web-vitals library or Performance API)
- Remove redundant sections ('Overview', 'How It Works', 'When to Use') and consolidate into a brief intro followed immediately by implementation code
- Add concrete code snippets for at least one RUM platform (e.g., Datadog RUM initialization, custom event tracking)
- Include a validation step in the workflow showing how to verify RUM data is being collected correctly (e.g., checking network requests, platform dashboard verification)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what RUM is, what Core Web Vitals are, how platforms work). Multiple redundant sections ('Overview', 'How It Works', 'When to Use') that repeat similar information. The 'Examples' section describes what the skill will do rather than providing actual code. | 1 / 3 |
Actionability | No executable code provided despite being a technical implementation skill. Examples describe what 'the skill will do' abstractly rather than providing concrete JavaScript snippets for RUM implementation. Instructions are high-level bullet points without specific commands or copy-paste ready code. | 1 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack validation checkpoints. No feedback loops for verifying RUM implementation is working correctly. Error Handling section exists but provides only a checklist of things to check rather than a clear diagnostic workflow. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but is monolithic - everything is in one file with no references to external detailed documentation. The Resources section lists topics but provides no actual links or file references. Content that could be split (platform-specific implementations, detailed code examples) is either missing or would bloat this file. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (RUM implementation, Core Web Vitals, page load times), explicit 'Use when' guidance, and concrete trigger phrases. The technical specificity around Real User Monitoring creates a distinct niche that minimizes conflict with other performance-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement Real User Monitoring (RUM)', 'capture actual user performance data', 'Core Web Vitals', 'page load times', 'tracking custom performance events'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (implement RUM, capture user performance data, Core Web Vitals, page load times) AND when ('Use when setting up user experience monitoring or tracking custom performance events') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'setup RUM', 'track Core Web Vitals', 'monitor real user performance', 'user experience monitoring', 'custom performance events'. Includes both technical terms (RUM, Core Web Vitals) and natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Real User Monitoring and Core Web Vitals. The specific technical domain (RUM, performance monitoring from user perspective) distinguishes it from general performance testing or synthetic monitoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.