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

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

Quality

Content

72%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 compact, well-structured review skill that delegates code to a single real reference file and gives concrete checklists. The main gap is workflow clarity: the sections read as parallel review tasks rather than a sequenced, validated workflow.

Suggestions

Turn Check/Fix/Code Review into an explicit sequenced workflow with a verification checkpoint (e.g. 'After applying fixes, verify in the browser: re-run the failing flow and confirm QuotaExceededError is handled') to add a validate→fix→retry loop.

Trim the opening rationale paragraph to one line, or fold it into the reference, since the quota/private-browsing facts are largely known to Claude.

Inline one minimal try/catch storage wrapper snippet in the Quick Reference so the core pattern is visible without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive — four tight Quick Reference bullets and one-line Check/Fix/Explain/Code Review sections — but the opening rationale paragraph re-explains quota limits and private-browsing behavior that Claude already knows.	4 / 5
Actionability	Concrete checklists name exactly what to look for (missing try/catch, unhandled JSON.parse, storage of sensitive data) and what to fix; no inline executable code, but the scoring notes allow that for an instruction/review skill, and the code lives in references/rule.md.	4 / 5
Workflow Clarity	The Quick Reference/Check/Fix/Explain/Code Review sections form a menu of review tasks rather than a strict sequence, and verification ('state how the change should be verified in the browser') is only implicitly a checkpoint with no validate→fix→verify feedback loop.	3 / 5
Progressive Disclosure	A clear, well-organized overview with a single, well-signaled one-level-deep reference ('see references/rule.md' for implementation details, code examples, and framework-specific guidance), and the referenced file exists.	5 / 5
	Total	16 / 20 Passed

Description

80%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 well-formed description that explicitly pairs a 'what' with a 'Use when' trigger and names several concrete review actions. Its main weaknesses are the missing natural localStorage/sessionStorage synonyms and a trigger template that overlaps with sibling frontend rules.

Suggestions

Add the natural synonyms users say ('localStorage', 'sessionStorage') to the trigger clause, e.g. 'Use when reviewing localStorage/sessionStorage usage, scripts, client components, bundles, or runtime behavior'.

Tighten the 'what' to describe the skill's actual web-storage actions (try/catch wrapping, serialization, avoiding sensitive-data storage) rather than only the generic review methodology.

Differentiate the trigger from sibling frontendchecklist rules by leading with the web-storage-specific signals instead of the shared 'scripts, client components, bundles' template.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions ('reviewing scripts, client components, bundles, or runtime behavior' and 'Inspect both source code and the browser execution path'), though they are generic review-process actions rather than web-storage-specific operations.	4 / 5
Completeness	Explicitly answers both 'what' (review/inspect source and browser execution path so fixes target the real bottleneck) and 'when' ('Use when reviewing scripts, client components, bundles, or runtime behavior related to Use Web Storage API safely') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage across review triggers ('scripts, client components, bundles, runtime behavior, Web Storage API, browser execution path'), but it omits the natural synonyms users actually say — localStorage and sessionStorage.	4 / 5
Distinctiveness Conflict Risk	The 'Web Storage API' anchor gives it a niche, but the 'reviewing scripts, client components, bundles, or runtime behavior' trigger phrasing is a shared template across sibling frontendchecklist rules, creating real overlap risk with closely related skills.	3 / 5
	Total	16 / 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/web-storage/SKILL.md
Commit: 30756a7

Reviewed: 4 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.