CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/browser-caching/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured overview with excellent progressive disclosure to a real reference file, and its Quick Reference bullets carry genuine specifics. However, the Check/Fix/Explain sections are vague one-liners with no executable guidance or validation method inline, so the body alone leaves Claude without concrete steps.

Suggestions

Inline one copy-paste-ready header example in the Fix section (e.g., 'Cache-Control: public, max-age=31536000, immutable' for hashed assets) so the body is actionable without opening the reference.

Make the Check section concrete: name the verification method (DevTools Network tab response headers, Lighthouse 'Serve static assets with an efficient cache policy' audit) instead of 'verify that proper cache headers are set'.

Delete the opening sentence explaining how caching benefits repeat visits — it is a concept Claude already knows and adds token cost without new information.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, but the intro sentence 'Proper caching eliminates redundant downloads on repeat visits—returning users see near-instant page loads' explains a concept Claude already knows, and phrasing like 'Verify that proper cache headers are set for static resources to enable browser caching' is circular.

4 / 5

Actionability

The Quick Reference bullets are concrete ('immutable caching for hashed assets (1 year max-age)', 'short cache + revalidation for HTML'), but the Check and Fix sections are one-line directions with no code, commands, or header examples in the body ('Configure appropriate Cache-Control and ETag headers for different resource types') — all executable detail is delegated to the reference file.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present, but validation checkpoints are implicit: 'Verify that proper cache headers are set' names no method or tool, even though the frontmatter description mentions DevTools/Lighthouse and the reference file has a 'Verifying Cache Headers' section the body never points to.

3 / 5

Progressive Disclosure

A short, well-organized overview with a clearly signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and references/rule.md exists as a real file with the promised content (code examples, Nginx/Express configs, verification steps).

5 / 5

Total

15

/

20

Passed

Description

75%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 solid description with an explicit 'Use when' trigger clause, tool-specific verification guidance, and a clear caching niche. Its main weaknesses are an incomplete statement of capability (verification is described but the cache-header configuration the skill delivers is not) and the awkward leaked rule-name phrasing 'related to Enable browser caching'.

Suggestions

State the full capability explicitly, e.g., 'Configure Cache-Control, ETag, and stale-while-revalidate headers for static assets' — the current description only covers the audit/verify half of the skill.

Replace the rule-name leak 'rendering delays related to Enable browser caching' with natural language like 'when repeat visits are slow or assets re-download', which is what a user would actually say.

Add common trigger synonyms such as 'page speed', 'cache headers', or 'assets re-downloaded on every visit' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Concrete actions with named tools are present ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes'), but the fix-side capability (configuring Cache-Control/ETag headers) is never stated, leaving minor gaps versus the comprehensive coverage of anchor 5.

4 / 5

Completeness

Both parts are present: an explicit 'Use when auditing slow page loads, heavy assets, or rendering delays…' trigger clause and a what ('Verify the actual bottleneck… before recommending changes'), but the 'what' could be more explicit and comprehensive about what the skill actually does beyond verification.

4 / 5

Trigger Term Quality

Natural phrases users would say appear ('slow page loads', 'heavy assets', 'rendering delays', 'browser caching'), but common variations like 'page speed', 'site is slow on repeat visits', or 'cache headers' are missing.

4 / 5

Distinctiveness Conflict Risk

The scope is niched to browser caching with a distinct verification-first framing, but the broad triggers 'slow page loads, heavy assets, or rendering delays' overlap other frontend performance skills (image optimization, bundling), giving minor conflict risk.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/browser-caching/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.