performance-optimization

Web performance optimization including bundle analysis, lazy loading, caching strategies, and Core Web Vitals

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/performance-optimization/SKILL.md

Quality

Content

80%

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

The content is concise and highly actionable with strong executable examples, but it presents everything inline with no progressive disclosure to deeper references and only an implicit validation workflow via its checklist.

Suggestions

Add explicit validation checkpoints to the checklist, e.g., "Measure LCP/INP/CLS before and after each change; revert if a metric regresses."

Consider splitting detailed recipe sections (image optimization, virtualization, caching) into one-level-deep reference files linked from a concise overview to improve progressive disclosure.

Add a brief "Measure first" step pointing to web-vitals/Lighthouse so the workflow opens with a baseline rather than jumping straight to optimizations.

Dimension	Reasoning	Score
Conciseness	The body is lean — mostly executable code with terse comments and tight bullet thresholds ("LCP < 2.5s", "INP < 200ms"); it assumes Claude's competence and avoids explaining what Core Web Vitals or caching are, so every token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready code (lazy imports, vite manualChunks, next/image, web-vitals handlers) and concrete commands ("npx vite-bundle-visualizer", "npx source-map-explorer dist/assets/*.js"), matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	A closing checklist gives a sequence of items to apply/verify, but there are no explicit measure-before/after validation checkpoints or error-recovery feedback loops, so the sequence is present but checkpoints remain implicit.	2 / 3
Progressive Disclosure	The skill is a single ~190-line monolithic file with well-organized sections but no external references or split-out deeper material; content that could live in separate references (detailed code recipes) is inline, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and occupies a clear niche, but it lacks an explicit "Use when..." trigger clause and only provides single phrasings of its trigger terms rather than covering common user variations.

Suggestions

Add an explicit "Use when..." clause, e.g., "Use when the user reports a slow site, asks to improve page speed or Lighthouse scores, or mentions Core Web Vitals (LCP/INP/CLS)."

Broaden trigger terms with natural variations users say: "page speed", "Lighthouse", "LCP", "CLS", "INP", "slow loading".

Keep the existing concrete action list but pair it with the trigger guidance so both 'what' and 'when' are explicit.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "bundle analysis, lazy loading, caching strategies, and Core Web Vitals" — matching the anchor for listing several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "lazy loading", "caching strategies", and "Core Web Vitals" are natural, but it offers only one phrasing each and omits common variations users say (e.g., "page speed", "Lighthouse", "LCP/CLS/INP", "slow site"), matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	"Web performance optimization" with these specific sub-techniques is a clear niche with distinct triggers, unlikely to be confused with other skills.	3 / 3
	Total	10 / 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: rohitg00/awesome-claude-code-toolkit
Path: skills/performance-optimization/SKILL.md
Commit: ebdf1d5

Reviewed: 2 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.