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

88%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 a high-quality, actionable performance guide with executable examples, an explicit validation-driven workflow, and clear structure. Its only notable gap is conciseness via redundant closing sections and heavy inlining of detail that progressive disclosure would push into separate bundle reference files.

Suggestions

Consolidate the Common Rationalizations, Red Flags, and Verification sections, which restate workflow guidance; link to a checklist reference file instead to recover tokens.

Move the longer per-anti-pattern code examples (responsive <picture>, cache layers) into a bundle reference file under references/ and keep SKILL.md as an overview with the workflow and shorter examples, improving progressive_disclosure toward anchor 5.

Verify the referenced `../../references/performance-checklist.md` resolves at the plugin level, or relocate it into the skill's own references/ directory so the reference target is part of the bundle.

Dimension	Reasoning	Score
Conciseness	It never explains basics Claude already knows (no "what a PDF is"-style padding) and assumes competence throughout, which is efficient. The demerit is that three closing sections (Common Rationalizations, Red Flags, Verification) restate guidance already covered in the workflow steps and could be consolidated, keeping it just below the lean anchor 5.	4 / 5
Actionability	It provides extensive copy-paste-ready, executable code and commands across the common cases: N+1 fixes, pagination, EXPLAIN ANALYZE, CREATE INDEX, pool sizing, responsive <picture>, React.memo/useMemo, lazy imports, caching, Cache-Control headers, and CI commands (bundlesize, lhci). This matches anchor 5 (fully executable, covers common cases).	5 / 5
Workflow Clarity	The 5-step workflow (MEASURE→IDENTIFY→FIX→VERIFY→GUARD) is explicitly sequenced with a dedicated validation step (Step 4) containing a keep/revert decision table, an error-recovery feedback loop (revert and re-measure; return to Step 1 when a guard fires), and a verification checklist. Because validation is central rather than missing, the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	The body is well-organized with clear section headers, a single clearly-signaled one-level-deep reference ("See `../../references/performance-checklist.md`" in See Also), and no nested reference chains. It stays at anchor 4 rather than 5 because the ~490-line SKILL.md inlines substantial detail that could be split into bundle reference files, and no actual bundle files exist in references/scripts/assets.	4 / 5
	Total	18 / 20 Passed

Description

78%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: third-person voice, a clear "what", and an explicit multi-trigger "Use when" clause that satisfies completeness. Its main weakness is specificity, since the verb "Optimizes" is generic and the scope areas are domains rather than concrete actions.

Suggestions

Replace or augment the generic verb "Optimizes" with 2-3 concrete actions (e.g., "Profiles, fixes N+1 queries, reduces bundle size, and adds indexes") to lift specificity toward anchor 4-5.

Add a few natural synonyms users say ("slow", "latency", "p95", "throughput") to round out trigger-term coverage toward anchor 5.

Dimension	Reasoning	Score
Specificity	It names the domain and four scope areas ("across frontend, backend, queries, and databases"), but the core action "Optimizes" is generic rather than a list of concrete actions like profile, index, or split bundles. It sits at the anchor-3 level (domain + minimal actions) rather than anchor 4, which expects several specific actions.	3 / 5
Completeness	It explicitly answers both what ("Optimizes application performance across frontend, backend, queries, and databases") and when ("Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement...") with concrete trigger phrases, matching the anchor-5 example pattern exactly.	5 / 5
Trigger Term Quality	It includes natural developer phrases ("Core Web Vitals", "load times", "N+1 query patterns", "performance regressions", "profiling") that users would actually say. Coverage is good but a few natural synonyms (latency, slow, throughput, p95) are missing, placing it just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Triggers like "N+1 query patterns" and "Core Web Vitals" mark a clear performance niche with distinct signals, but the broad scope (frontend, backend, queries, databases) creates minor overlap risk with more specialized tuning skills. It is mostly distinct rather than fully minimal-conflict, so anchor 4 fits better than 5.	4 / 5
	Total	16 / 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: 48cb116

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