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—it repeats the skill name as its own trigger term and provides no concrete actions, use cases, or distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of similar frontend development skills. The description needs a complete rewrite with specific capabilities and explicit trigger guidance.
Suggestions
Add concrete actions the skill performs, e.g., 'Monitors and analyzes Core Web Vitals metrics including LCP, CLS, FID, and INP. Identifies performance bottlenecks 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 Core Web Vitals, page performance, Lighthouse scores, LCP, CLS, FID, INP, site speed, or web performance optimization.'
Remove the duplicate trigger term ('web vitals monitor' listed twice) and expand with varied natural language terms users would actually say, such as 'page speed', 'performance audit', 'slow website', 'loading time'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Web Vitals Monitor') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'measures', 'tracks', 'reports', or 'optimizes'. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'web vitals monitor' repeated twice. It misses natural user phrases like 'Core Web Vitals', 'LCP', 'CLS', 'FID', 'INP', 'page speed', 'performance metrics', 'Lighthouse', or 'site performance'. | 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 technical content. It repeatedly references 'web vitals monitor' without ever defining what web vitals are, which metrics to track (LCP, FID, CLS, INP, TTFB), how to measure them, or providing any code examples using the web-vitals library or Performance Observer API. It provides zero value to Claude.
Suggestions
Add concrete, executable code examples for measuring Core Web Vitals (e.g., using the `web-vitals` npm library or `PerformanceObserver` API) with specific metrics like LCP, CLS, INP, and TTFB.
Replace the meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') with actual implementation guidance: how to instrument a page, collect metrics, set thresholds, and report results.
Include a clear workflow: 1) Install/import measurement tools, 2) Instrument specific metrics, 3) Set performance budgets/thresholds, 4) Validate against targets, 5) Report or alert on regressions.
Add specific threshold values for each Core Web Vital (e.g., LCP < 2.5s = good, CLS < 0.1 = good) and concrete debugging steps when thresholds are exceeded.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('web vitals monitor') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific APIs (e.g., web-vitals library), no metrics definitions (LCP, FID, CLS), no implementation steps. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The 'step-by-step guidance' is merely claimed in a bullet point but never delivered. There are no sequences, validation checkpoints, or any procedural content. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive wall of boilerplate with no meaningful structure, no references to detailed resources, and no navigation to deeper content. Section headers exist but contain no substantive information. | 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
c8a915c
- 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.