web-performance-audit
Web performance audits with Core Web Vitals, bottleneck identification, optimization recommendations. Use for page load times, performance reviews, UX optimization, or encountering LCP, FID, CLS issues, resource blocking, render delays.
79
68%
Does it follow best practices?
Impact
96%
1.20xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/web-performance-audit/skills/web-performance-audit/SKILL.mdQuality
Discovery
100%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 is a strong skill description that concisely covers specific capabilities, includes a comprehensive set of natural trigger terms spanning both technical and plain-language variations, and clearly delineates both what the skill does and when to use it. The description uses proper third-person voice and maintains a clear, distinct niche around web performance optimization.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Web performance audits with Core Web Vitals', 'bottleneck identification', 'optimization recommendations'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (web performance audits, bottleneck identification, optimization recommendations) and 'when' with an explicit 'Use for...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'page load times', 'performance reviews', 'UX optimization', 'LCP', 'FID', 'CLS', 'resource blocking', 'render delays'. These cover both technical acronyms and plain-language phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on web performance and Core Web Vitals specifically. The technical trigger terms like LCP, FID, CLS, and 'resource blocking' make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a decent reference sheet for web performance concepts and includes some executable code examples, but it reads more like a cheat sheet than an actionable workflow guide. It lacks a clear sequenced audit process with validation steps, and the optimization strategies are too generic—listing things Claude already knows without providing concrete implementation guidance.
Suggestions
Add a clear numbered workflow for conducting an audit: measure baseline → identify bottlenecks → implement fixes → validate improvements → set monitoring, with explicit validation checkpoints between steps.
Replace the generic optimization bullet lists with concrete, executable examples (e.g., actual webpack config for code splitting, actual nginx config for brotli compression, specific CLI commands).
Remove the Core Web Vitals thresholds table and generic strategy lists that Claude already knows, and focus token budget on project-specific patterns and decision trees for diagnosing specific bottleneck types.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some information Claude already knows (e.g., the Core Web Vitals thresholds table, generic optimization strategies like 'minify CSS/JS'). The timeline estimates (1-2 days, 1-2 weeks) are filler for a skill meant to guide Claude's actions. | 2 / 3 |
Actionability | Provides executable code for measurement (web-vitals, Lighthouse) and a concrete performance budget JSON, but the optimization strategies section is a vague bullet-point list without concrete implementation code or commands. The checklist items like 'Analyze real user metrics (RUM)' lack specific tooling or steps. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for conducting an audit. The checklist at the end is a flat list without ordering dependencies, validation checkpoints, or feedback loops. For a performance audit involving potentially destructive changes (architecture improvements, caching strategies), there's no verify-then-proceed pattern. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, but everything is inline in a single file with no references to supporting documents. The optimization strategies section could benefit from being split into detailed guides. However, for a skill of this length (~80 lines), the structure is adequate though not optimal. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.