CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-storage

Use when reviewing scripts, client components, bundles, or runtime behavior related to Use Web Storage API safely. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

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/web-storage/SKILL.md
SKILL.md
Quality
Evals
Security

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 clean, tight single-purpose skill: concise overview with a sharp Quick Reference, concrete storage-specific checks, and exemplary progressive disclosure that delegates implementation depth to a real one-level-deep reference file. The main gaps are unstated relationships between the Check/Fix/Explain/Code Review modes and a slightly padded motivational intro.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with a tight Quick Reference of four one-line rules and terse Check/Fix/Explain/Code Review sections; the only trimmable material is the motivational close of the intro ('Applications that don't handle these errors crash silently, leaving users unable to use the app') and quota facts Claude largely already knows. This matches anchor 4 ('efficient; minor instances of over-explanation') rather than 5, which would drop the motivational padding entirely.

4 / 5

Actionability

The guidance names specific APIs and concrete checks — 'wrap localStorage access in try/catch', 'Serialize objects with JSON.stringify and validate on read with JSON.parse', 'use httpOnly cookies', 'Find all localStorage and sessionStorage accesses in this file' — which is actionable without inline code (per the instruction-only scoring note). Not anchor 5 because the Fix section stays high-level ('Add try/catch error handling to all Web Storage operations') with executable examples delegated entirely to the reference file.

4 / 5

Workflow Clarity

The Check → Fix flow is clearly sequenced and unambiguous, and the Code Review section does instruct to 'state how the change should be verified in the browser', giving a verification checkpoint. Not anchor 5 because the relationship between the four modes (Check, Fix, Explain, Code Review) is never stated — a reader must infer when to use which — and Check and Code Review partially overlap.

4 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that pushes all implementation detail, code examples, and framework guidance to `references/rule.md`, which exists, is one level deep (no nested references inside it), and is clearly signaled at the bottom ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'). This matches anchor 5: clear overview, appropriately split content, well-signaled one-level-deep reference.

5 / 5

Total

17

/

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 'Use when...' clause and names both what the skill does and its domain, but it leans on the technical umbrella term 'Web Storage API' and generic review framing instead of the natural vocabulary (localStorage, sessionStorage, quota, try/catch) users would actually say. Trigger and specificity are the weak points. It uses appropriate third-person/impersonal voice and is concise.

Suggestions

Include the natural terms users say — 'localStorage', 'sessionStorage', 'storage quota', 'QuotaExceededError' — alongside or instead of the umbrella term 'Web Storage API', which most users won't say verbatim.

Replace the generic action framing ('reviewing scripts, client components, bundles, or runtime behavior') with storage-specific concrete actions, e.g. 'audit localStorage/sessionStorage usage for missing try/catch, unvalidated JSON.parse, and sensitive-data leaks'.

Smooth the awkward embedded rule title ('related to Use Web Storage API safely') into a natural clause so the sentence reads as description prose, not a pasted rule name.

DimensionReasoningScore

Specificity

The description names the domain ("Use Web Storage API safely") and two concrete actions — "reviewing scripts, client components, bundles, or runtime behavior" and "Inspect both source code and the browser execution path" — but stops at 2 actions rather than the 'several specific actions' of anchor 4, and the actions are generic to any frontend review rather than storage-specific.

3 / 5

Completeness

Both 'what' ("reviewing scripts, client components, bundles, or runtime behavior related to Use Web Storage API safely" + "Inspect both source code and the browser execution path") and 'when' (explicit "Use when reviewing..." clause) are present, satisfying anchor 4. Not anchor 5 because the trigger objects ('scripts, client components, bundles') are generic rather than concrete storage-related trigger phrases, and the embedded rule title 'Use Web Storage API safely' reads awkwardly inside the sentence.

4 / 5

Trigger Term Quality

Relevant keywords like "scripts", "client components", "bundles", "runtime behavior", and "browser" are present, but the most natural user terms — "localStorage" and "sessionStorage" — are absent, leaving only the technical umbrella term "Web Storage API". This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'), not 4, because the everyday synonyms users actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The Web Storage niche is fairly distinct with clear browser-storage triggers, but the description's emphasis on broadly-scoped review targets ('scripts, client components, bundles, or runtime behavior') creates minor overlap risk with general JavaScript/browser code-review skills — matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's minimal-conflict clear niche.

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/web-storage/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.