perf-web-optimization

Optimize web performance: bundle size, images, caching, lazy loading, and overall page speed. Use when site is slow, reducing bundle size, fixing layout shifts, improving Time to Interactive, or optimizing for Lighthouse scores. Triggers on: web performance, bundle size, page speed, slow site, lazy loading. Do NOT use for Core Web Vitals-specific fixes (use core-web-vitals), running Lighthouse audits (use perf-lighthouse), or Astro-specific optimization (use perf-astro).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference with excellent progressive disclosure and token efficiency. Its only gap is that the stated five-step workflow is asserted but not actually operationalized with measurement/validation checkpoints.

Suggestions

Flesh out the 'Measure → Identify → Prioritize → Implement → Verify' workflow: add a concrete Verify step such as 'Re-run the audit and confirm LCP/INP/CLS moved into the Good column before finishing.'

Add a feedback loop for the Prioritize→Implement cycle, e.g. 'If a quick win does not move the target metric, revert it and try the next highest-impact item.'

Tie each Quick Win section back to the metric it moves (images→LCP, third-party scripts→INP) so the Prioritize step is actionable rather than implied.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient: a metrics table, copy-paste code blocks, and checklists with no explanatory padding of concepts Claude already knows (e.g., it never defines what LCP or CLS is).	3 / 3
Actionability	Fully executable, copy-paste-ready guidance throughout — concrete HTML for images/fonts/scripts, working bash bundle-analyzer commands, JS code-splitting patterns, and exact Cache-Control header values.	3 / 3
Workflow Clarity	A sequence is named ("Measure → Identify → Prioritize → Implement → Verify") but it is never elaborated and the Verify step has no checkpoint or feedback loop, so validation remains implicit rather than actionable.	2 / 3
Progressive Disclosure	Clear overview body with well-signaled, one-level-deep references to real bundle files (core-web-vitals.md, bundle-optimization.md, image-optimization.md) listed under "Detailed Examples"; content appropriately split with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

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.

A strong, specific description that clearly states capabilities, includes natural trigger terms, answers both what and when, and explicitly distinguishes itself from sibling performance skills. No verbosity or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "bundle size, images, caching, lazy loading, and overall page speed" — rather than vague language, matching the level-3 anchor.	3 / 3
Completeness	Explicitly answers both what ("Optimize web performance: bundle size, images, caching, lazy loading...") and when ("Use when site is slow..." plus a "Triggers on:" clause), satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Good coverage of natural terms a user would say: "site is slow", "page speed", "slow site", "bundle size", "lazy loading", alongside "Triggers on:" phrasing; not just jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche with explicit disambiguation — "Do NOT use for Core Web Vitals-specific fixes (use core-web-vitals), running Lighthouse audits (use perf-lighthouse), or Astro-specific optimization (use perf-astro)" — making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 9026164

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.