CtrlK
BlogDocsLog inGet started
Tessl Logo

web-performance-audit

Web performance audits with Core Web Vitals, bottleneck identification, optimization recommendations. Use for page load times, performance reviews, UX optimization, or encountering LCP, FID, CLS issues, resource blocking, render delays.

92

1.20x
Quality

90%

Does it follow best practices?

Impact

96%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A concise, actionable single-file skill with executable web-vitals and Lighthouse code and a useful audit checklist. Its main gaps are the absence of explicit validation/feedback checkpoints in the audit workflow and no progressive disclosure into separate reference files.

Suggestions

Add an explicit validation/re-measure checkpoint to the audit workflow (e.g., 'After applying optimizations, re-run Core Web Vitals and confirm the metric moved into the Good range before declaring the issue resolved').

Split the Lighthouse automation and performance-budget material into a referenced file (e.g., REFERENCE.md) and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

Tie the generic optimization bullets ('Implement code splitting', 'Add service worker caching') to concrete commands or short code snippets so they instruct rather than describe.

DimensionReasoningScore

Conciseness

Lean and assumption-respecting: it gives Core Web Vitals thresholds, executable code, and a checklist without explaining what a Core Web Vital is or how the libraries work. Not a level-2 because there is no padded concept explanation to tighten.

3 / 3

Actionability

Provides copy-paste-ready executable code for web-vitals collection and Lighthouse automation, plus a concrete performance-budget JSON and an audit checklist. Not a level-2 because the examples are complete and runnable rather than pseudocode.

3 / 3

Workflow Clarity

The Audit Checklist sequences the audit (measure baseline, run Lighthouse, analyze RUM, set budget, configure monitoring) but has no explicit validation checkpoints or fix-then-retry feedback loops. Not a level-3 because validation/feedback steps are absent; not a level-1 because a real ordered sequence exists.

2 / 3

Progressive Disclosure

Well-organized into clear sections, but everything is inline in a single ~90-line file with no external references or signaled deeper-dive files. Not a level-3 because it exceeds the simple-skill (<50 line) exemption and offers no one-level-deep references; not a level-1 because it is structured, not a monolithic wall of text.

2 / 3

Total

10

/

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, third-person description that states concrete capabilities and gives explicit 'Use for' trigger guidance with natural keywords including the CWV acronyms. It clearly communicates both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Web performance audits', 'bottleneck identification', 'optimization recommendations' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (audits, bottleneck ID, optimization recommendations) and when via a 'Use for ...' clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural user phrasing ('page load times', 'performance reviews', 'UX optimization') plus the actual acronym triggers users say ('LCP, FID, CLS issues', 'resource blocking', 'render delays').

3 / 3

Distinctiveness Conflict Risk

Web performance auditing with Core Web Vitals acronyms is a clear niche with distinct triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
Reviewed

Table of Contents

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.