CtrlK
BlogDocsLog inGet started
Tessl Logo

offline-fallback

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

63

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

Quality

Content

100%

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: lean, actionable, with a clear sequenced workflow and an explicit verification checklist, deferring full implementation cleanly to a single real reference file. It is an exemplar of progressive disclosure for a single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean — a short rationale, a four-item Quick Reference, and terse Check/Fix/Explain/Code Review sections — with no padding explaining what a service worker or PWA is; it assumes Claude's competence and defers detail to the reference.

3 / 3

Actionability

Quick Reference gives concrete specific steps ("Create a minimal /offline HTML page that works without any network requests", "Pre-cache the offline page during the service worker install event", "Intercept failed navigation requests and serve the offline page instead"); per the rubric's instruction-only guidance, the deferred executable code is not penalized because the guidance itself is actionable.

3 / 3

Workflow Clarity

Quick Reference lays out a clear sequence (create page → pre-cache at install → intercept failed navigations → add user guidance), and the Code Review section provides an explicit verification checklist (pre-cached at install, no external resources, only served for navigation requests).

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals one level deep to a real bundle file ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), which was verified to exist — clean, well-signaled navigation.

3 / 3

Total

12

/

12

Passed

Description

50%

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 functions well as a trigger clause but omits any statement of what the skill does, and it lacks the most natural keyword ("offline"). It is adequate but generic enough to risk overlapping with neighboring PWA skills.

Suggestions

Add an explicit "what" clause naming the concrete deliverable, e.g. "Provides a custom offline fallback page served by a service worker when navigation requests fail."

Include "offline", "offline page", and "offline fallback" among the trigger terms so the skill surfaces for the most common user phrasings.

Narrow the triggers away from the broad "PWA capabilities" umbrella toward offline-specific cues (e.g. "Use when the site needs a graceful offline experience or a fallback for failed navigations") to reduce conflict with other PWA skills.

DimensionReasoningScore

Specificity

Names a domain and some actions ("adding PWA capabilities", "implementing a service worker", "improving the experience for users on unreliable network connections") but never names the skill's concrete capability — providing an offline fallback page — so it is not comprehensive.

2 / 3

Completeness

The "when" is explicit ("Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections"), but the "what" — what the skill actually produces — is only implied, never stated.

2 / 3

Trigger Term Quality

"PWA capabilities" and "service worker" are natural terms a user would say, but the most common trigger — "offline" / "offline page" / "offline fallback" / "flaky connection" — is entirely absent, missing common variations.

2 / 3

Distinctiveness Conflict Risk

"PWA capabilities" and "service worker" are broad domains that would overlap with caching, push, installability, and background-sync skills; the distinctive offline-fallback niche is not singled out.

2 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.