CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The SKILL.md body is a well-organized, lean overview that delegates detailed code to a single clearly-signaled reference, with an unambiguous review workflow. Its only weakness is that the most executable, copy-paste-ready guidance lives in the reference rather than the body itself.

Suggestions

Consider including one small inline try/catch wrapper snippet in the body so the core defensive pattern is immediately actionable without opening the reference.

The Check section could name a quick concrete way to locate storage accesses (e.g., grep for localStorage/sessionStorage) to make the first step more executable.

DimensionReasoningScore

Conciseness

The body is lean — a brief intro, a tight Quick Reference list, and short Check/Fix/Explain/Code Review sections — with no lecturing on concepts Claude already knows; every token earns its place.

3 / 3

Actionability

The guidance is concrete and specific ('Always wrap localStorage access in try/catch', 'Never store sensitive data… use httpOnly cookies') but the actual executable code lives in the reference, leaving the body with directives rather than copy-paste-ready examples.

2 / 3

Workflow Clarity

As a simple single-purpose review skill the Check/Fix/Explain/Code Review sections give an unambiguous sequence, and the Code Review section explicitly calls for stating how the change should be verified in the browser.

3 / 3

Progressive Disclosure

The body is a clear overview that points to one well-signaled, one-level-deep reference ('see references/rule.md'), and that reference file exists and holds the detailed code, matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

11

/

12

Passed

Description

77%

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' trigger and concrete actions, but its trigger terms omit the natural Web Storage keywords (localStorage/sessionStorage/quota) that users would actually say, and the broad review framing risks overlapping with other frontend skills.

Suggestions

Add natural Web Storage keywords to the trigger clause (e.g., localStorage, sessionStorage, storage quota, Web Storage API) so users can say the terms they'd naturally use.

Rephrase 'related to Use Web Storage API safely' into a smoother, third-person description of the skill's purpose rather than restating the rule title.

DimensionReasoningScore

Specificity

Concrete actions are named ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path') with multiple specific targets, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It answers both 'what' (review and inspect source and browser execution paths) and 'when' with an explicit 'Use when...' trigger clause, matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Relevant review-oriented terms are present but the actual natural Web Storage keywords a user would say (localStorage, sessionStorage, quota, Web Storage) are missing, and 'related to Use Web Storage API safely' reads awkwardly — partial coverage.

2 / 3

Distinctiveness Conflict Risk

The 'scripts, client components, bundles, or runtime behavior' framing is broad across many frontend review skills; only the Web Storage tie-in narrows it, so overlap with similar skills remains possible.

2 / 3

Total

10

/

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.