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

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/real-user-monitoring/skills/implementing-real-user-monitoring/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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 but lacks executable substance: it describes rather than instructs, omits validation checkpoints, and its bundle listings reference files that do not exist. Actionability is the primary weakness.

Suggestions

Add concrete, copy-paste-ready code for at least one platform (e.g., a web-vitals/Datadog snippet) and reference the bundled setup_rum.py with an example invocation, so guidance is executable rather than descriptive.

Insert validation checkpoints into the Instructions workflow (e.g., verify the snippet loads, confirm events appear in the platform dashboard) with a fix-and-retry loop before declaring the setup complete.

Reconcile the bundle READMEs with the actual files present: either add validate_rum_config.py, deploy_rum_snippet.sh, and example_rum_snippet.html, or remove them from the listings, and link the body explicitly to the files that do exist.

Dimension	Reasoning	Score
Conciseness	Sections like Overview, How It Works, When to Use, Best Practices, Integration, and Resources restate well-known concepts (Core Web Vitals, GDPR/CCCPA compliance, sampling) Claude already knows, but the document is not a wall of definitional padding; it is mostly efficient with some unnecessary explanation, matching level 2 rather than the lean level 3 or the verbose level 1.	2 / 3
Actionability	The body contains no executable code or commands anywhere — it only describes ('Provide code snippets', 'Generate JavaScript code', 'Implement tracking code in application frontend'), matching the level 1 anchor 'describes rather than instructs'; it is not level 2 because there is no concrete guidance at all, only abstract direction.	1 / 3
Workflow Clarity	The Instructions section provides a numbered 6-step sequence and Error Handling offers troubleshooting, but there are no validation checkpoints and deploying tracking snippets is a risky change lacking a validate-fix-retry loop; per the rubric, missing validation in such contexts caps clarity at level 2.	2 / 3
Progressive Disclosure	The body has organized sections but never links to specific bundle files, and the bundle READMEs advertise nonexistent files (validate_rum_config.py, deploy_rum_snippet.sh, example_rum_snippet.html), so references are present but not clearly signaled and organization is incomplete — level 2 rather than the well-signaled one-level-deep level 3.	2 / 3
	Total	7 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 well-constructed: third-person voice, concrete capabilities, explicit 'Use when' and trigger-phrase guidance, and a distinct niche. It hits all four anchors at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person ('capture actual user performance data including Core Web Vitals and page load times', 'tracking custom performance events'), matching the 'multiple specific concrete actions' anchor rather than the vague level 1 or partial level 2.	3 / 3
Completeness	Explicitly answers both what ('capture...data including Core Web Vitals and page load times') and when via an explicit 'Use when...' clause plus a 'Trigger with phrases like...' list, matching the level 3 anchor with explicit triggers.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('setup RUM', 'track Core Web Vitals', 'monitor real user performance') give good coverage of terms a user would actually say, matching the level 3 anchor rather than level 2's 'some relevant keywords but missing common variations'.	3 / 3
Distinctiveness Conflict Risk	RUM and Core Web Vitals form a clear niche with distinct, specific triggers unlikely to fire for unrelated skills, matching the level 3 'clear niche with distinct triggers' anchor.	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
Path: plugins/performance/real-user-monitoring/skills/implementing-real-user-monitoring/SKILL.md
Commit: bddba3c

Reviewed: about 22 hours 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.