session-timeout-recovery

Use when reviewing authenticated user flows or long forms. Check both client and server behavior: warning timing, dialog accessibility, autosave frequency, timeout extension, and post-login state restoration.

Quality

76%

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/session-timeout-recovery/SKILL.md

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 clean, well-structured overview that delegates implementation detail to one real reference file, giving strong progressive disclosure. It is weaker on actionability and workflow clarity, since fixes stay high-level and the guidance is organized by mode rather than as a sequenced, validated workflow.

Suggestions

Add one or two concrete code snippets or specific patterns inline (e.g., a setTimeout-based warning dialog, a fetch draft-persistence call) instead of deferring all implementation detail to references/rule.md.

Sequence Check -> Fix -> Explain as explicit numbered steps with a verification checkpoint, e.g., "After fixing, re-test the flow as a keyboard-only user to confirm the warning is announced and state restores."

Collapse the Quick Reference bullets into the Check paragraph (or vice versa) to remove the redundancy and reclaim token budget.

Dimension	Reasoning	Score
Conciseness	The body is lean and well sectioned, but the Quick Reference bullets largely restate the Check paragraph, and the Explain section restates WCAG alignment Claude already knows.	4 / 5
Actionability	Concrete review checklist items appear ("Verify users are told the timeout duration, warned before expiry..."), but the Fix guidance is high-level ("Add an accessible timeout warning") with all code and examples deferred to references/rule.md.	3 / 5
Workflow Clarity	Sections are organized by mode (Check/Fix/Explain/Code Review) rather than as a sequenced workflow, and there are no explicit validation or verification checkpoints.	3 / 5
Progressive Disclosure	A concise overview in SKILL.md points via a single well-signaled, one-level-deep pointer ("see `references/rule.md`") to implementation details; the referenced file exists.	5 / 5
	Total	15 / 20 Passed

Description

88%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 clearly and explicitly answers both what to check and when to use the skill, with a comprehensive list of concrete behaviors to verify across client and server. Trigger terms are natural and largely complete, with only minor synonym and overlap-risk gaps.

Dimension	Reasoning	Score
Specificity	"Check both client and server behavior: warning timing, dialog accessibility, autosave frequency, timeout extension, and post-login state restoration" lists multiple specific concrete checks with comprehensive coverage of the domain.	5 / 5
Completeness	"Use when reviewing authenticated user flows or long forms" gives an explicit when, and "Check both client and server behavior: ..." gives a concrete what, satisfying both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "authenticated user flows", "long forms", "timeout extension", "autosave", and "post-login" give good coverage, but common synonyms such as "session expiry" or "login timeout" are missing.	4 / 5
Distinctiveness Conflict Risk	The session-timeout/accessibility niche is mostly distinct with specific triggers, but "reviewing authenticated user flows or long forms" has minor overlap risk with general auth or form-accessibility review skills.	4 / 5
	Total	18 / 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/session-timeout-recovery/SKILL.md
Commit: 30756a7

Reviewed: 19 days 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.