web-performance-optimization
Optimizes web application performance through code splitting, lazy loading, caching strategies, and Core Web Vitals monitoring. Use when improving page load times, implementing service workers, or reducing bundle sizes.
88
82%
Does it follow best practices?
Impact
96%
1.15xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 clearly communicates specific capabilities (code splitting, lazy loading, caching strategies, Core Web Vitals monitoring) and provides explicit trigger guidance via a 'Use when' clause. The trigger terms are natural and cover the vocabulary developers would use when seeking performance optimization help. The description is concise, uses third person voice, and carves out a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: code splitting, lazy loading, caching strategies, Core Web Vitals monitoring, service workers, and reducing bundle sizes. | 3 / 3 |
Completeness | Clearly answers both 'what' (optimizes web performance through code splitting, lazy loading, caching, Core Web Vitals monitoring) and 'when' (explicit 'Use when improving page load times, implementing service workers, or reducing bundle sizes'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'page load times', 'bundle sizes', 'service workers', 'code splitting', 'lazy loading', 'Core Web Vitals', and 'web application performance' — these cover common terms developers use when seeking performance optimization help. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on web performance optimization with specific techniques like code splitting, service workers, and Core Web Vitals creates a clear niche that is unlikely to conflict with general web development or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong, executable code examples across multiple performance optimization techniques, making it highly actionable. However, it suffers from some verbosity (repeated INP/FID notes, generic best practices list, well-known resource URLs) and lacks a cohesive workflow that sequences the optimization process with measurement-validation feedback loops. The progressive disclosure to reference files is well-structured but the main file retains too much low-value content.
Suggestions
Remove the generic 'Best Practices' bullet list and 'Resources' section — Claude already knows these concepts and can find these URLs.
Add a sequenced workflow section (e.g., 1. Measure baseline with Lighthouse, 2. Identify bottleneck, 3. Apply relevant optimization, 4. Re-measure to verify improvement) with explicit validation checkpoints.
Remove the duplicate INP/FID explanation — mention it once in the performance targets table note and remove the inline comment in the code.
Move the Tools section into the reference files or inline tool usage into the workflow steps where they're actually needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes unnecessary sections like 'Best Practices' (a generic bullet list Claude already knows), 'Resources' with well-known URLs, and verbose comments in the Core Web Vitals section explaining what sendToAnalytics does. The note about INP replacing FID is repeated twice. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready — React lazy loading, webpack config, service worker, nginx compression, and PerformanceObserver monitoring. Each section provides concrete, working code rather than pseudocode or abstract descriptions. | 3 / 3 |
Workflow Clarity | The skill presents individual techniques clearly but lacks a sequenced workflow for how to approach performance optimization (e.g., measure first, then optimize, then verify). The checklist at the end is helpful but there are no validation checkpoints or feedback loops — no guidance on measuring before/after or verifying that optimizations actually improved metrics. | 2 / 3 |
Progressive Disclosure | References to compression-monitoring.md and typescript-advanced.md are well-signaled and one level deep, which is good. However, the main file is quite long (~180 lines of content) with sections like Best Practices, Resources, and Tools that add bulk without much value. The 'When to Use' section and performance targets table could arguably stay, but the generic best practices list and external resource links bloat the overview. | 2 / 3 |
Total | 9 / 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.