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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

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

The body is well-sectioned and has a clear high-level workflow, but it lacks any executable code or commands and never points to the bundled scripts/references that would make it actionable. Tightening the prose and surfacing the existing bundle files would substantially improve it.

Suggestions

Add concrete, copy-paste-ready tracking snippets (e.g. a web-vitals + platform SDK example) instead of describing the implementation abstractly, and reference scripts/setup_rum.py by name in the Instructions.

Insert explicit validation checkpoints into the workflow (e.g. 'Verify the snippet loads and emits events before configuring dashboards') so the sequence has feedback loops.

Replace the generic Overview/How It Works prose and the best-practices boilerplate with brief pointers, and link the real bundle files (references/, scripts/, assets/) so progressive disclosure is one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly organized but padded with conceptual filler ('This skill streamlines the process...', 'Helps you consider available RUM platforms') and generic best-practice prose Claude already knows; it could be tightened. Not score 3 because several sections restate obvious context rather than earning their tokens.	2 / 3
Actionability	Despite the skill's purpose being tracking-code implementation, the body contains zero executable code or commands; 'Instructions' are abstract ('Implement tracking code in application frontend') and Examples describe rather than instruct. Not score 2 because there is no concrete code, command, or pseudocode block at all.	1 / 3
Workflow Clarity	A six-step sequence exists (select platform → define metrics → implement → configure → dashboards → alerts) but there are no validation checkpoints or feedback loops; the Error Handling section is generic troubleshooting rather than integrated validate-then-proceed steps. Not score 3 because checkpoints are missing; not score 1 because the sequence is explicit and ordered.	2 / 3
Progressive Disclosure	Bundle files exist (scripts/setup_rum.py, references/, assets/) but the body never signals or links them, leaving a monolithic inline document; bundle READMEs even reference files that do not exist (validate_rum_config.py, deploy_rum_snippet.sh, example_rum_snippet.html). Not score 3 because references are not clearly signaled from the body; not score 1 because the body is section-organized rather than a true wall of nested pointers.	2 / 3
	Total	7 / 12 Passed

Description

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.

The description is strong: it names concrete capabilities, supplies natural trigger phrases, and explicitly covers both what the skill does and when to use it in a concise, third-person voice. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'capture actual user performance data including Core Web Vitals and page load times' and 'tracking custom performance events' — matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what (implement RUM to capture Core Web Vitals, load times, custom events) and when ('Use when setting up user experience monitoring...') with explicit triggers, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Provides natural phrases users would actually say — 'setup RUM', 'track Core Web Vitals', 'monitor real user performance' — giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear RUM/Core Web Vitals niche with distinct triggers unlikely to fire for unrelated skills; written in third person so no voice penalty applies.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days 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.