CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

back-forward-cache

Use when reviewing navigation performance, browser lifecycle events, or resume-from-memory behavior. Check the actual browser lifecycle and restore path, not only static code patterns.

Quality

72%

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/back-forward-cache/SKILL.md
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.

The skill body is a tight, well-structured overview with concrete lifecycle-API guidance and an exemplary one-level reference to the detailed rule file. Its main costs are a small amount of redundant and explanatory material — the bfcache concept intro and overlap between the Check and Code Review sections — plus a few directions that remain abstract.

Suggestions

Delete or compress the opening paragraph explaining what bfcache is; Claude already knows this, and the Quick Reference carries the substance.

Merge the 'Check' and 'Code Review' sections, which cover the same listener/stale-state ground, into one section to remove redundancy.

Make the verification step concrete (e.g. name the DevTools bfcache blocker inspection or the pageshow.persisted test) and add a re-check step after fixes to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the opening paragraph explains what back/forward cache is ('the entire page is resumed from memory instead of being rebuilt from the network') — a concept Claude already knows — and the 'Check' and 'Code Review' sections repeat overlapping guidance about unload/beforeunload listeners and stale state. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is noticeably better than the padded level 2 but not the near-lean level 4.

3 / 5

Actionability

The Quick Reference gives concrete, API-level directives ('Never add an `unload` listener', 'Refresh time-sensitive state when `pageshow.persisted` is `true`', 'Keep `beforeunload` conditional and remove it when there are no unsaved changes'), which for an instruction-only skill is mostly executable guidance. It falls short of 5 because some directions stay abstract ('resource lifecycles that break when the page is resumed') and the DevTools verification step is not made concrete, with the executable code deferred to the reference file.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent review workflow with a verification checkpoint ('Verify eligibility in DevTools instead of assuming a page is cacheable'). This matches 'clear sequence with most checkpoints present; minor validation gaps' — there is no explicit feedback loop (e.g. re-check after fixing), which keeps it below 5.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) and ends with a clearly signaled, one-level-deep pointer to 'references/rule.md' for 'full implementation details, code examples, and framework-specific guidance'. The referenced file exists and is not itself a chain of further references, matching the anchor for a clear overview with well-signaled one-level-deep references.

5 / 5

Total

16

/

20

Passed

Description

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

The description has an explicit and well-scoped 'Use when' trigger clause and names a distinctive domain, but the capability statement is thin and it omits the most natural trigger terms (bfcache, back/forward cache). It is a solid, above-midpoint description with clear room to sharpen both the what and the keywords.

Suggestions

Add the terms users actually say — 'bfcache' and 'back/forward cache' — to the trigger clause, e.g. 'Use when reviewing bfcache / back/forward cache eligibility, navigation performance, or browser lifecycle events.'

Enumerate the concrete actions instead of the generic 'Check the actual browser lifecycle and restore path', e.g. 'Flag unload and unconditional beforeunload listeners, verify pageshow.persisted state refresh, and check bfcache eligibility in DevTools.'

State the deliverable explicitly (e.g. 'reports and fixes bfcache blockers in route code') so the 'what' is as concrete as the 'when'.

DimensionReasoningScore

Specificity

The description names the domain ('navigation performance, browser lifecycle events, or resume-from-memory behavior') and one concrete action ('Check the actual browser lifecycle and restore path, not only static code patterns'), which matches the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It does not list several specific actions such as flagging unload listeners or verifying pageshow.persisted handling, so it is not a 4.

3 / 5

Completeness

Both parts are present: an explicit when ('Use when reviewing navigation performance, browser lifecycle events, or resume-from-memory behavior') and a what ('Check the actual browser lifecycle and restore path, not only static code patterns'). It falls short of 5 because the 'what' is a single generic clause rather than concrete enumerated capabilities with trigger phrases.

4 / 5

Trigger Term Quality

Phrases like 'navigation performance', 'browser lifecycle events', and 'resume-from-memory behavior' are relevant, but the canonical terms a user would naturally say — 'bfcache', 'back/forward cache', 'pageshow' — are absent. This matches the anchor for some relevant keywords while missing common variations or synonyms, and is above the generic one-or-two-keyword level.

3 / 5

Distinctiveness Conflict Risk

'Browser lifecycle events' and 'resume-from-memory behavior' carve out a fairly distinct niche with clear triggers, though 'navigation performance' is broad enough to overlap with general performance-auditing skills. This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the fully distinct anchor at 5.

4 / 5

Total

14

/

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/back-forward-cache/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.