performance-optimization

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-sequenced skill body with executable code, numeric budgets, and a measure-verify workflow. Its main gaps are mild verbosity (a persuasive rationalizations section and an over-long HTML example) and broken progressive disclosure: the only reference target does not exist and detailed content stays inline.

Suggestions

Remove or fix the broken "See Also" reference to references/performance-checklist.md — either create the file or delete the pointer, since no bundle files currently exist.

Move the detailed anti-pattern code fixes and the diagnostic decision tree into a reference file to externalize depth and let SKILL.md serve as a lean overview.

Trim the "Common Rationalizations" table and shorten the picture/source HTML example to the minimal responsive pattern to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Most of the body is dense, actionable content (anti-pattern tables, executable fixes, budgets, a verification checklist), but the "Common Rationalizations" table editorializes arguments Claude doesn't need and the ~60-line image-optimization HTML example is padded, fitting anchor 2 ("mostly efficient but includes some unnecessary explanation or could be tightened") rather than the lean anchor 3.	2 / 3
Actionability	It provides copy-paste-ready executable code (N+1 and pagination fixes, caching, React.memo/useMemo, lazy imports), concrete CI commands ("npx bundlesize", "npx lhci autorun"), and specific numeric budgets, matching the anchor-3 "fully executable code/commands; specific examples; copy-paste ready."	3 / 3
Workflow Clarity	The workflow is an explicitly numbered MEASURE → IDENTIFY → FIX → VERIFY → GUARD sequence with a closing Verification checklist (before/after measurements, budget passing, tests still passing), providing the explicit validation steps and feedback loop that anchor 3 requires.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), yet the "See Also" section points to references/performance-checklist.md which does not exist, and large detailed material (the diagnostic tree, full anti-pattern code, the long image HTML) remains inline; this fits anchor 2 ("some structure... content that should be separate is inline") rather than anchor 3 because there are no working one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

90%

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, third-person description with explicit "Use when..." triggers and good natural-term coverage that clearly distinguishes the skill. Its only weakness is a thin action statement — "Optimizes application performance" is generic rather than enumerating concrete capabilities.

Suggestions

Replace or augment the generic verb "Optimizes application performance" with specific concrete actions, e.g. "Profiles bottlenecks, fixes N+1 queries and bundle bloat, and improves Core Web Vitals (LCP/INP/CLS)."

Consolidate the two "Use when..." clauses into a single, tighter trigger sentence to reduce repetition without losing the explicit triggers.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Optimizes application performance") but offers only a single generic action verb; it does not list multiple specific concrete actions like reducing bundle size or optimizing queries, so it stops at the anchor-2 level rather than reaching the multi-action anchor 3.	2 / 3
Completeness	It states what the skill does ("Optimizes application performance") and provides two explicit "Use when..." trigger clauses, satisfying the anchor-3 requirement of clearly answering both what and when with explicit triggers; it is not anchor 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	It covers natural terms a user would say — "performance requirements", "performance regressions", "Core Web Vitals", "load times", "profiling reveals bottlenecks" — with good variation, matching the anchor-3 example of broad natural-term coverage rather than the anchor-2 "some keywords but missing variations".	3 / 3
Distinctiveness Conflict Risk	Triggers tied to Core Web Vitals, load times, profiling, and bottlenecks carve out a clear web/app-performance niche unlikely to fire for unrelated skills, matching the anchor-3 "clear niche with distinct triggers; unlikely to conflict."	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: addyosmani/agent-skills
Commit: 70b7506

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