web-vitals-monitor
Web Vitals Monitor - Auto-activating skill for Frontend Development. Triggers on: web vitals monitor, web vitals monitor Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill web-vitals-monitorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lists no concrete capabilities, and offers no guidance on when Claude should select this skill. The description would be indistinguishable from any generic frontend performance tool.
Suggestions
Add specific actions the skill performs, e.g., 'Measures Core Web Vitals (LCP, CLS, FID/INP), analyzes performance bottlenecks, generates optimization recommendations'
Include a 'Use when...' clause with natural trigger terms like 'page speed', 'core web vitals', 'performance audit', 'slow loading', 'layout shift'
Add file types or contexts that trigger this skill, e.g., 'when analyzing Lighthouse reports, performance traces, or optimizing React/Vue components for speed'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Web Vitals Monitor') without describing any concrete actions. There are no specific capabilities listed like 'measure LCP', 'track CLS', or 'analyze performance metrics'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('web vitals monitor' repeated twice) and miss natural variations users would say like 'page speed', 'core web vitals', 'LCP', 'CLS', 'FID', 'performance metrics', or 'site performance'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Web Vitals' is a specific domain, the lack of detail means it could overlap with general performance monitoring or frontend development skills. The category mention helps slightly but doesn't establish a clear niche. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a generic template with no actual content about web vitals monitoring. It lacks any concrete information about Core Web Vitals (LCP, FID, CLS, INP, TTFB), measurement tools (web-vitals library, Lighthouse, CrUX), or implementation patterns. The content is entirely boilerplate that could apply to any skill topic.
Suggestions
Add executable code examples showing how to measure Core Web Vitals using the web-vitals library or Performance API
Include specific metrics (LCP, CLS, INP, TTFB) with target thresholds and what they measure
Provide concrete monitoring setup steps: install library, configure reporting, interpret results
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about web vitals monitoring. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually monitor web vitals (no Core Web Vitals metrics, no measurement code, no tools mentioned). | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content only lists vague capabilities without any sequence of actions, validation steps, or concrete process for monitoring web vitals. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.