performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

Quality

83%

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

Quality

Content

77%Weight 40%Scale 1-5

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

The content is highly actionable with an excellent, well-validated workflow and concrete executable examples throughout. Its main weaknesses are verbose editorial prose that could be trimmed and a monolithic structure with a broken external reference.

Suggestions

Trim the rhetorical narrative in Step 4 (e.g. 'Make it pay for itself', 'A regression wearing a win's clothing') to tighten the prose without losing the keep/revert guidance.

Fix or remove the broken 'See Also' reference to ../../references/performance-checklist.md — either create the referenced file or drop the link, since pointing at a non-existent file undermines navigation.

Move the long <picture> image-optimization example into a referenced asset file, keeping a concise inline snippet in SKILL.md to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code and tables, but includes several verbose rhetorical passages (e.g. 'Code you keep, you maintain forever. Make it pay for itself.', 'A regression wearing a win's clothing') and an oversized <picture> image example that could be tightened, matching 'mostly efficient but could be tightened'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready code for N+1 fixes, pagination, image optimization, React.memo/useMemo, lazy loading, and caching, plus specific commands (Lighthouse, web-vitals, bundlesize, lhci) and symptom→cause tables covering common cases.	5 / 5
Workflow Clarity	The MEASURE→IDENTIFY→FIX→VERIFY→GUARD sequence has explicit validation checkpoints, a keep/revert decision table in Verify, feedback loops (re-measure, revert on noise or red tests), and a closing verification checklist.	5 / 5
Progressive Disclosure	The file has clear section structure but is largely monolithic (~390 lines of inline code and tables), and its single 'See Also' reference to ../../references/performance-checklist.md points to a file that does not exist in the bundle, leaving organization incomplete.	3 / 5
	Total	16 / 20 Passed

Description

90%Weight 40%Scale 1-5

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 strong: it explicitly covers both what and when, with rich natural trigger terms and a distinct performance niche. The only weakness is that the action side relies on one verb ('optimizes') applied across domains rather than enumerating several distinct concrete actions.

Dimension	Reasoning	Score
Specificity	The single action verb 'Optimizes' is applied across named domains (frontend, backend, queries, databases) rather than listing multiple distinct concrete actions, matching the anchor that names a domain with 1-2 actions but is not comprehensive in verbs.	3 / 5
Completeness	It clearly states what it does ('Optimizes application performance across frontend, backend, queries, and databases') and explicitly answers when with concrete trigger phrases in a 'Use when' clause.	5 / 5
Trigger Term Quality	The 'Use when' clause covers comprehensive natural terms users would actually say — 'performance regressions', 'Core Web Vitals', 'load times', 'N+1 query patterns', 'profiling', 'bottlenecks' — including synonyms and specific technical phrases.	5 / 5
Distinctiveness Conflict Risk	It occupies a clear performance niche with specific triggers (Core Web Vitals, N+1, profiling, bottlenecks) that are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	18 / 20 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: addyosmani/agent-skills
Path: skills/performance-optimization/SKILL.md
Commit: df1edb2

Reviewed: about 19 hours 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.