offline-fallback

Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections.

Quality

65%

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/offline-fallback/SKILL.md

Quality

Content

78%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 lean, well-organized overview that appropriately delegates all code examples and framework guidance to a single, real, clearly signaled reference file one level deep. The main improvement opportunities are removing the slight duplication between the intro, Quick Reference, and Fix sections, and surfacing a one-line verification method inline.

Suggestions

Merge the Quick Reference bullets with the Fix section (or vice versa) — bullets 1-3 restate the Fix content almost verbatim.

Add one line to the Check section naming the concrete verification, e.g. "In DevTools, set Network to Offline and navigate to an uncached page" rather than deferring it entirely to the reference.

Trim the intro's why-it-matters prose to one sentence; the 'reinforces trust / surfaces cached content' rationale is duplicated in the reference's Why It Matters section.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what a service worker is), but the intro paragraph and Quick Reference bullets 1-3 partially restate the Fix section, leaving minor instances that could be trimmed.	4 / 5
Actionability	Concrete specifics throughout ("Pre-cache the offline page during the service worker install event", "only served for navigation requests (not sub-resources)") with full executable code delegated to the real, clearly signaled references/rule.md; minor gaps remain since the body has no inline snippet or verification method.	4 / 5
Workflow Clarity	The Quick Reference gives a clear sequence (create page → pre-cache at install → intercept failed navigations → include user guidance) plus a Check step, and the operation is neither destructive nor batch, so no cap applies; the method for verifying offline behavior (DevTools Offline, Lighthouse) is deferred to the reference rather than stated here.	4 / 5
Progressive Disclosure	A well-sectioned under-50-line overview with a single one-level-deep reference: references/rule.md exists, is clearly signaled at the end of the body, is self-contained (no nested references), and appropriately holds all code and framework-specific guidance.	5 / 5
	Total	17 / 20 Passed

Description

52%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 trigger-focused description with clear "use when" clauses and natural keywords, but it never states what the skill does and misses the core "offline" vocabulary that users would most naturally say when needing this skill. Restructuring to pair a concrete capability statement with the existing trigger clauses would fix both weaknesses.

Suggestions

Add a 'what' clause before the triggers, e.g. "Provides an offline fallback page pattern (self-contained HTML plus service worker pre-caching and navigation-fallback logic). Use when..."

Include the skill's core vocabulary in the triggers: "offline page", "offline support", or "site fails to load offline" alongside the existing PWA/service-worker phrases.

Replace the generic "improving the experience for users on unreliable network connections" with a more specific capability such as "serving a custom offline fallback for failed navigation requests".

Dimension	Reasoning	Score
Specificity	"Implementing a service worker" is a concrete action, but "adding PWA capabilities" and "improving the experience for users on unreliable network connections" are generic phrasing, so the description names the domain with only 1-2 concrete actions and is not comprehensive.	3 / 5
Completeness	The description is entirely trigger clauses ("Use when adding PWA capabilities, implementing a service worker, or improving the experience...") with no statement of what the skill actually does (create and serve an offline fallback page), matching the "only 'when' present without 'what'" anchor.	2 / 5
Trigger Term Quality	Includes natural phrases users would say ("PWA capabilities", "service worker", "unreliable network connections"), but omits the most natural trigger for this skill — "offline" — along with "offline page" and "caching", so keyword coverage is good with a notable term missing.	4 / 5
Distinctiveness Conflict Risk	The service worker/PWA niche is mostly distinct with specific triggers, but "adding PWA capabilities" broadly overlaps with related PWA skills (manifests, installability, caching strategies), creating minor conflict risk.	4 / 5
	Total	13 / 20 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/offline-fallback/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.