implementing-real-user-monitoring

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".

Quality

50%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/performance/real-user-monitoring/skills/implementing-real-user-monitoring/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly defines its scope (Real User Monitoring), lists specific capabilities (Core Web Vitals, page load times, custom performance events), and provides explicit trigger guidance with example phrases. It uses proper third-person voice and occupies a distinct niche that minimizes conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'capture actual user performance data', 'Core Web Vitals', 'page load times', 'tracking custom performance events'. These are concrete, domain-specific capabilities.	3 / 3
Completeness	Clearly answers both 'what' (implement RUM to capture user performance data including Core Web Vitals and page load times) and 'when' (explicit 'Use when' clause plus 'Trigger with phrases like' providing concrete trigger examples).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'RUM', 'Core Web Vitals', 'page load times', 'user experience monitoring', 'custom performance events', 'setup RUM', 'track Core Web Vitals', 'monitor real user performance'. Good coverage of terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Clearly occupies a distinct niche around Real User Monitoring specifically. The terms 'RUM', 'Core Web Vitals', and 'real user performance' are highly specific and unlikely to conflict with general monitoring or analytics skills.	3 / 3
	Total	12 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads like a marketing overview or README rather than actionable instructions for Claude. It is almost entirely descriptive meta-content (what the skill does, when to use it, how it works) without any concrete implementation guidance—no code examples, no specific API calls, no platform-specific configuration steps. The content fails on all dimensions: it's verbose, non-actionable, lacks workflow rigor, and has no progressive disclosure structure.

Suggestions

Replace the descriptive sections (Overview, How It Works, When to Use, Examples descriptions) with actual executable code snippets for at least one RUM platform (e.g., a complete web-vitals + Google Analytics implementation)

Add concrete, copy-paste ready JavaScript code for Core Web Vitals tracking using the `web-vitals` library, including installation commands and integration patterns

Define a clear multi-step workflow with validation checkpoints, e.g., 'After adding the tracking script, verify data appears in the platform dashboard within 5 minutes' or 'Check browser console for tracking errors'

Remove all meta-sections that describe what the skill does (Claude can infer this) and replace with platform-specific implementation guides, potentially split into separate reference files for each RUM platform

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive sections explaining what the skill does, when to use it, and how it works—all meta-information Claude doesn't need. The 'Overview', 'How It Works', 'When to Use This Skill', 'Examples', and 'Integration' sections are padding that describe rather than instruct. Concepts like Core Web Vitals, RUM platforms, and privacy compliance are things Claude already knows.	1 / 3
Actionability	Despite being a technical implementation skill, there is zero executable code anywhere. The 'Examples' section promises code snippets but delivers none. Instructions are entirely abstract ('Implement tracking code in application frontend') with no concrete commands, code blocks, or copy-paste ready snippets.	1 / 3
Workflow Clarity	The 'Instructions' section lists 6 high-level steps with no specifics, no validation checkpoints, and no feedback loops. For a skill involving JavaScript integration and platform configuration, there are no concrete verification steps to confirm the implementation works correctly.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files, no bundle structure, and no separation of concerns. The 'Resources' section lists generic topic names without actual links or file references. All content is inline but lacks the depth that would justify being inline.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.