CtrlK
BlogDocsLog inGet started
Tessl Logo

performance

Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable, well-structured skill body with executable code throughout and sound progressive disclosure. The main weaknesses are a verbose Early Hints passage and a broken cross-skill reference.

Suggestions

Tighten the Early Hints paragraph: move the vendor case-study caveat and MDN/Cloudflare rationale into a one-line note or the MEASUREMENT reference, reducing padding that drags conciseness down.

Fix or remove the broken ../core-web-vitals/SKILL.md link (and the duplicate LCP link on line 78) so progressive-disclosure navigation is fully valid.

Add an explicit 'if the re-run shows no improvement (or a regression), revert and re-diagnose' retry step to the workflow to push workflow_clarity toward 5.

DimensionReasoningScore

Conciseness

Most sections are lean with executable, self-explanatory code, but the Early Hints paragraph is a dense explanatory wall and a few prose blocks over-explain vendor caveats, fitting 'mostly efficient with some unnecessary explanation that could be tightened'.

3 / 5

Actionability

It provides copy-paste-ready code across the common cases (preconnect, preload, speculation rules, code splitting, picture/srcset, fonts, cache headers, service worker, layout batching, debounce, rAF, view transitions, facade), matching the fully-executable anchor.

5 / 5

Workflow Clarity

The 'How it works' section gives a clear sequenced 4-step evidence-led process with a re-measure checkpoint and an explicit static-inspection branch, but lacks an explicit 'measure -> fix -> re-measure' retry loop, sitting between anchors 4 and 5.

4 / 5

Progressive Disclosure

The body is a well-structured overview with clearly signaled, one-level-deep references to real bundle files (MEASUREMENT.md, RUM.md), but the ../core-web-vitals/SKILL.md cross-link does not exist and the body is fairly long, keeping it just below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

86%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 with excellent trigger-term coverage and a clear what/when structure in third person. The only weakness is that it states one general action rather than enumerating several concrete capabilities.

Suggestions

Replace the single verb 'Optimize' with a short list of concrete actions (e.g. 'Diagnose slow loads, reduce page weight, prioritize critical resources, and tune Core Web Vitals') to lift specificity from 3 toward 5.

Add an explicit capability noun or two (e.g. 'audits', 'budgets') so the 'what' reads as multiple deliverables rather than one outcome.

DimensionReasoningScore

Specificity

It names the domain ('Optimize web performance') and one concrete action ('optimize') plus outcomes ('faster loading', 'better user experience'), but does not enumerate multiple concrete actions, fitting the 'domain and 1-2 concrete actions' anchor rather than the multi-action level above.

3 / 5

Completeness

It explicitly answers both what ('Optimize web performance for faster loading and better user experience') and when ('Use when asked to...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It lists six natural, user-spoken phrases ('speed up my site', 'optimize performance', 'reduce load time', 'fix slow loading', 'improve page speed', 'performance audit') with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The 'web performance' niche with distinct natural-language triggers is mostly distinct with minimal conflict risk, but a possible sibling 'core-web-vitals' skill creates minor overlap, so it sits between anchors 4 and 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
addyosmani/web-quality-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.