browser-caching

Use when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/browser-caching/SKILL.md

Quality

Content

57%

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

The body is a clean, well-structured overview that correctly defers detailed code to a one-level reference, but it stays at strategy-level guidance without executable config or an in-body validation checkpoint, leaving it actionable-but-incomplete.

Suggestions

Add one minimal executable example in the body (e.g. a one-line Cache-Control header for hashed assets) so the Fix section is actionable without forcing a file open.

Surface a post-fix validation step in the body (e.g. 'Confirm headers in DevTools Network tab') rather than burying it in the reference.

Trim the opening 'why it matters' sentence and the redundant 'Explain' directive to avoid restating caching concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (terse Quick Reference bullets and one-line Check/Fix sections), but the opening 'why it matters' sentence and the meta 'Explain how browser caching reduces server requests' instruction restate concepts Claude already knows.	2 / 3
Actionability	The Quick Reference gives some concrete strategy specifics (immutable caching, '1 year max-age', stale-while-revalidate), but the Fix section ('Configure appropriate Cache-Control and ETag headers') is abstract and all executable config is deferred to the reference, leaving the body incomplete.	2 / 3
Workflow Clarity	A Check -> Fix -> Explain -> Code Review sequence is present, but the body lacks an explicit post-fix validation checkpoint (the verify-in-DevTools step lives only in the reference), so checkpoints are implicit.	2 / 3
Progressive Disclosure	The body is a clear overview with a single well-signaled one-level-deep reference ('see references/rule.md'), and the executable code/framework configs are appropriately split into that existing file.	3 / 3
	Total	9 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a clear explicit 'Use when' trigger and decent natural symptom keywords, but it frames the skill around auditing/verifying rather than stating the concrete caching-header action, and its broad performance triggers risk overlap with sibling performance skills.

Suggestions

State the core action concretely, e.g. 'Configures Cache-Control and ETag headers for static assets', so the 'what' matches the skill's actual capability.

Replace the rule-title artifact 'Enable browser caching' with natural phrasing and add common variations like 'cache static assets' or 'repeat-visit performance'.

Tighten the trigger to caching-specific signals (e.g. 'repeat visits are slow', 'assets re-download') to reduce overlap with other performance skills.

Dimension	Reasoning	Score
Specificity	It names the domain (browser caching) and actions like 'auditing slow page loads' and 'Verify the actual bottleneck', but never states the skill's core concrete action (configuring Cache-Control/ETag headers), so it is not comprehensive.	2 / 3
Completeness	An explicit 'Use when...' trigger answers the 'when', and 'Verify the actual bottleneck... before recommending changes' answers the 'what', satisfying both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	Natural symptom terms like 'slow page loads', 'heavy assets', 'rendering delays', and 'Lighthouse' are present, but the awkward rule-title phrase 'Enable browser caching' and the absence of common variations like 'cache static assets' or 'make my site faster' limit coverage.	2 / 3
Distinctiveness Conflict Risk	It targets a specific niche (browser caching) but the broad performance-symptom triggers ('slow page loads', 'heavy assets', 'rendering delays') could overlap with other performance skills, and the description itself flags the need to verify the real bottleneck.	2 / 3
	Total	9 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/browser-caching/SKILL.md
Commit: 48405aa

Reviewed: about 9 hours 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.