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.
36
Quality
3%
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
7%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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The repeated trigger term and boilerplate category mention provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs, such as 'Measures Core Web Vitals (LCP, FID, CLS), analyzes performance bottlenecks, and suggests optimizations'
Include a 'Use when...' clause with natural trigger terms like 'page speed', 'performance metrics', 'Core Web Vitals', 'LCP', 'CLS', 'loading performance'
Remove the redundant duplicate trigger term and replace with varied, user-natural phrases like 'slow page load', 'performance audit', 'lighthouse scores'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill 'Web Vitals Monitor' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., measure, analyze, report, optimize). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. It only states it's part of Frontend Development category without explaining functionality or use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'web vitals monitor' repeated twice, which is redundant and lacks natural variations users might say like 'performance metrics', 'LCP', 'CLS', 'page speed', or 'core web vitals'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Web Vitals' is a specific domain, the lack of detail about what actions it performs could cause overlap with other frontend performance or monitoring skills. The category mention provides some context but is insufficient. | 2 / 3 |
Total | 5 / 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 that provides no actual guidance on web vitals monitoring. It contains only generic boilerplate text that could apply to any skill topic, with no specific information about Core Web Vitals (LCP, FID, CLS), measurement tools, or implementation approaches. The content fails all dimensions by being both verbose and completely non-actionable.
Suggestions
Add executable code examples showing how to measure Core Web Vitals using the web-vitals library or Performance API
Include specific metrics (LCP, FID, CLS, INP, TTFB) with target thresholds and what they measure
Provide concrete commands or integration steps for common frameworks (React, Vue) and monitoring tools
Remove all generic boilerplate and replace with actual technical guidance specific to web vitals monitoring
| 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 | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, examples, or related files that would provide actual web vitals monitoring guidance. | 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
994edc4
- 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.