CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

77%

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

Quality

Content

70%

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 review skill that uses progressive disclosure effectively and routes detail to a real reference file. The recurring weakness is repetition across sections and guidance that stays somewhat abstract without the referenced detail.

Suggestions

Collapse the overlap between Quick Reference, Check, and Code Review into a single checklist to remove restated points.

Inline one or two concrete examples (e.g. an accessible timeout-warning snippet or an autosave trigger) so the body is actionable without forcing a jump to rule.md.

DimensionReasoningScore

Conciseness

Mostly efficient, but the Quick Reference bullets and the Check/Fix/Explain/Code Review sections restate the same checks multiple times (e.g. 'Review authenticated flows...' vs 'Review authenticated forms, checkout flows, editors...'), so it could be tightened.

2 / 3

Actionability

Names specific things to check and fix ('offer turn off, adjust, or extend behavior', 'restore the user to the same step'), but concrete implementation is deferred to references/rule.md rather than given inline.

2 / 3

Workflow Clarity

A simple single-purpose review skill with an unambiguous action, organized into clear Check/Fix/Explain phases that sequence the work.

3 / 3

Progressive Disclosure

Body is a concise overview that clearly signals one-level-deep detail ('see references/rule.md' for implementation details and examples), and the referenced file exists.

3 / 3

Total

10

/

12

Passed

Description

85%

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 well-structured description with an explicit 'Use when' trigger and several concrete capabilities. Its main weakness is trigger-term coverage, which misses the most natural user phrasings around session expiry.

Suggestions

Add natural trigger terms users would actually say, e.g. 'session timeout', 'session expired', or 'form data lost on logout'.

Consider leading with the skill's core purpose (preventing data loss from session timeouts) before listing the checks, to make the what even sharper.

DimensionReasoningScore

Specificity

Lists multiple concrete checks — 'warning timing, dialog accessibility, autosave frequency, timeout extension, and post-login state restoration' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Check both client and server behavior: ...') and when ('Use when reviewing authenticated user flows or long forms') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Has some natural terms ('authenticated user flows', 'long forms', 'timeout') but omits common variations a user would actually say like 'session timeout', 'session expired', or 'lost my work'.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche — session-timeout recovery in authenticated flows — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.