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.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/web-vitals-monitor/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder that provides no meaningful information about what the skill does or when it should be used. It repeats the skill name as its only trigger term and lacks any concrete actions, natural keywords, or explicit usage guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Measures and monitors Core Web Vitals metrics including LCP, CLS, FID, and INP. Generates performance reports and suggests optimizations for page load speed.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about page performance, core web vitals, lighthouse scores, LCP, CLS, FID, INP, page speed, or load time optimization.'
Remove the duplicate trigger term and expand with varied natural language phrases users would actually say, such as 'performance audit', 'slow page load', 'web performance metrics', or 'site speed'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Web Vitals Monitor') and its category ('Frontend Development') but lists no concrete actions like measuring LCP, CLS, FID, or generating performance reports. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is limited to a redundant trigger phrase with no explicit 'Use when...' guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'web vitals monitor' repeated twice. It misses natural user phrases like 'page speed', 'core web vitals', 'LCP', 'CLS', 'FID', 'INP', 'performance metrics', 'lighthouse', or 'page load time'. | 1 / 3 |
Distinctiveness Conflict Risk | Being categorized under 'Frontend Development' with no specific actions or distinct triggers means it could easily conflict with any other frontend performance or monitoring skill. Nothing distinguishes it clearly. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual instructional content about web vitals monitoring. It contains no code examples, no specific guidance on metrics like LCP, FID, CLS, or INP, no tool recommendations, and no actionable steps. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable code examples for measuring Core Web Vitals (e.g., using the `web-vitals` library, PerformanceObserver API, or Lighthouse CI integration).
Define a clear workflow for diagnosing and improving specific metrics (LCP, CLS, INP) with validation steps such as running Lighthouse audits before and after changes.
Replace the generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) with actual technical content: specific thresholds, common causes of poor scores, and fix patterns.
Include framework-specific examples (React, Vue) for monitoring web vitals in production, such as reporting to analytics endpoints or integrating with Next.js built-in reporting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'web vitals monitor' excessively, and contains zero domain-specific information about Web Vitals (LCP, FID, CLS, etc.). | 1 / 3 |
Actionability | There is no concrete code, no commands, no specific examples, and no executable guidance whatsoever. The content only describes what the skill would do in abstract terms without actually providing any instructions for monitoring web vitals. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but never provides any. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
13d35b8
- 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.