CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

high-perf-browser

Optimize web performance through network protocols, resource loading, and browser rendering internals. Use when the user mentions "page load speed", "Core Web Vitals", "HTTP/2", "resource hints", "network latency", "render blocking", "TCP optimization", "service worker", or "critical rendering path". Also trigger when diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes. Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection. For UI visual performance, see refactoring-ui. For font loading, see web-typography.

Quality

86%

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

71%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-structured framework skill with excellent progressive disclosure into six verified reference files and largely executable, concrete guidance. Its main weakness is token efficiency: redundant 'Why it works' explanations of concepts Claude already knows plus author-biography padding dilute an otherwise dense body.

Suggestions

Cut the per-section "Why it works" paragraphs (or reduce each to one non-obvious insight) — Claude already knows that CSS is render-blocking and how HTTP/2 multiplexing works; keep only the counterintuitive specifics.

Remove the "About the Author" section and trim "Further Reading" to a single line — biographical and bibliographic padding adds tokens without improving task execution.

Drop the duplicate navigation: either the per-section "See: references/..." links or the consolidated "Reference Files" section, keeping one clear path to each reference file.

DimensionReasoningScore

Conciseness

The Key insights and Code applications tables are dense and earn their tokens, but the six per-section "Why it works" paragraphs re-explain concepts Claude already knows (e.g., "CSS is render-blocking: the browser will not paint until all CSS is parsed", "HTTP/2 solves multiplexing"), and the "About the Author" and "Further Reading" sections are non-actionable padding. This is more than the 'minor instances' of anchor 4 but not the pervasive padding of anchor 2.

3 / 5

Actionability

Mostly executable guidance with copy-paste-ready snippets ("<link rel=\"preconnect\" href=\"https://cdn.example.com\">", "Cache-Control: max-age=31536000, immutable", "Alt-Svc: h3=\":443\"", "new EventSource('/api/updates')") and concrete diagnostic thresholds, but a few entries are advisory only ("CSS and fonts at highest priority" gives no syntax; "Cache static shell; network-first for dynamic content" describes rather than shows), fitting anchor 4.

4 / 5

Workflow Clarity

The Quick Diagnostic table supplies explicit checkpoints (question, threshold, corrective action) and the Scoring section defines a review procedure, giving clear validation-style checkpoints. However, the steps are not explicitly sequenced into an ordered measure-diagnose-fix workflow, so it falls short of anchor 5's 'clear sequence with feedback loops'.

4 / 5

Progressive Disclosure

A clear overview where each of the six domains links a real one-level-deep reference file with topic signaling ("See: references/network-fundamentals.md for TCP congestion control..."), all six referenced files verified present with no nested references, and a consolidated Reference Files index for navigation — matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

95%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 capabilities, provides a rich set of natural trigger terms, and cleanly disambiguates adjacent skills. The only soft spot is that the opening capability statement is broader domain framing than a list of discrete concrete actions.

DimensionReasoningScore

Specificity

Lists several concrete actions ("diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes"), but the headline capability statement ("Optimize web performance through network protocols, resource loading, and browser rendering internals") is broad domain framing rather than discrete concrete actions, matching anchor 4 rather than 5.

4 / 5

Completeness

Explicitly answers both what ("Optimize web performance... Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection") and when ("Use when the user mentions... Also trigger when...") with concrete trigger phrases, exactly matching the anchor 5 example pattern.

5 / 5

Trigger Term Quality

Nine quoted natural trigger phrases ("page load speed", "Core Web Vitals", "HTTP/2", "resource hints", "network latency", "render blocking", "TCP optimization", "service worker", "critical rendering path") plus four additional trigger scenarios give comprehensive coverage of terms users would naturally say.

5 / 5

Distinctiveness Conflict Risk

The web performance/networking niche is distinct and the description actively defuses overlap by routing adjacent topics elsewhere ("For UI visual performance, see refactoring-ui. For font loading, see web-typography."), minimizing conflict risk beyond anchor 4's 'minor overlap'.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/high-perf-browser/SKILL.md

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.