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.

84

1.20x
Quality

76%

Does it follow best practices?

Impact

96%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/web-performance-audit/skills/web-performance-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized, mostly executable audit skill with lean code examples and a sensible checklist. The main weakness is workflow clarity: the checklist lacks explicit validation checkpoints and a measure-optimize-re-measure feedback loop.

Suggestions

Add an explicit feedback loop to the audit checklist, e.g. 'Optimize the largest bottleneck -> re-measure Core Web Vitals -> confirm improvement before moving on'.

Insert a validation step after measurement, such as comparing each metric against the Good thresholds in the table before deciding what to optimize.

Move the optimization strategies (or the Lighthouse automation snippet) into a reference file and keep SKILL.md as a concise overview that links to it.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (it does not explain what LCP/CLS are), but the Lighthouse boilerplate code block is somewhat long and could be trimmed; not quite level-5 lean.

4 / 5

Actionability

Provides copy-paste-ready web-vitals and Lighthouse code plus concrete optimization lists and a budget JSON example, but no CLI command for running audits and the budget example is not tied to an enforcement tool, leaving minor gaps.

4 / 5

Workflow Clarity

The audit checklist provides a rough sequence (baseline -> Lighthouse -> RUM -> identify issues -> set budget -> monitor), but there are no explicit validation checkpoints or measure-optimize-re-measure feedback loops; checkpoints are only implicit.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections with no nested references and no bundle files present, but at ~90 lines it is a single monolithic file that could split optimization strategies or budget details into reference files.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that explicitly states both capabilities and use-when triggers with natural keyword coverage. It is held back from a perfect score by slightly generic action verbs and the broad 'UX optimization' phrasing that creates minor overlap risk.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ('audits', 'bottleneck identification', 'optimization recommendations'), but the actions are somewhat generic and not as comprehensive as a level-5 list.

4 / 5

Completeness

Clearly answers 'what' (audits, bottleneck identification, optimization recommendations) and explicitly answers 'when' with concrete trigger phrases via the 'Use for...' clause.

5 / 5

Trigger Term Quality

Good coverage of natural terms and user-said phrases ('page load times', 'performance reviews', 'UX optimization', 'LCP, FID, CLS issues', 'resource blocking', 'render delays'), though a few natural terms (e.g., INP, 'page speed') are missing.

4 / 5

Distinctiveness Conflict Risk

Core Web Vitals and LCP/FID/CLS triggers carve a clear niche with minimal conflict risk, but the broad 'UX optimization' phrase introduces minor overlap with general web-dev skills.

4 / 5

Total

17

/

20

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.