CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

right-to-erasure

Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.

Quality

70%

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/right-to-erasure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 overview skill with excellent progressive disclosure — a lean SKILL.md body deferring implementation detail to a real, well-matched reference file. Its weaknesses are internal duplication and a GDPR explainer Claude does not need, plus the absence of any verification step in the body for what is a destructive data-deletion workflow.

Suggestions

Replace the GDPR Article 17 explainer paragraph with a one-line rationale ('GDPR Art. 17 requires complete erasure within 30 days; fines up to 4% of turnover') — Claude already knows the regulation.

Merge the Quick Reference bullets into the Check section to eliminate the triple repetition of the storage-clearance list.

Add an explicit verify step to the workflow (e.g. a 'Verify' section pointing to the Verification checks in references/rule.md) so the destructive deletion flow includes a validation checkpoint.

DimensionReasoningScore

Conciseness

Mostly tight, but the opening paragraph explains GDPR Article 17 and its fine thresholds ('up to €20 million or 4% of global annual turnover') — background Claude already knows — and the Quick Reference bullets substantially duplicate the Check and Fix sections ('Clear all client-side storage: localStorage, sessionStorage, IndexedDB, and cookies' appears three times in different wording). Not 4 because these trims are readily identifiable; not 2 because the body is short and the padding is limited to one paragraph plus repetition.

3 / 5

Actionability

Concrete requirements are named (localStorage, sessionStorage, IndexedDB, cookies, server deletion request, user confirmation, 30-day timeline) and the Code Review section gives specific flag conditions ('missing client-side storage clearance, absent confirmation UI, or missing server-side deletion calls'). Not 4 because there are no executable detection steps or code in the body — no how to find the endpoint, check storage, or verify the request — the details are entirely deferred to the reference; not 2 because the guidance is specific about what must exist and what to flag.

3 / 5

Workflow Clarity

The Check / Fix / Explain / Code Review sections imply a coherent audit-then-remediate sequence, but there are no explicit checkpoints or ordering. Data deletion is a destructive operation, and the body contains no validation/verification step (the reference's Verification section is never surfaced), so per the destructive-operation cap workflow clarity cannot exceed 3. Not 2 because the task sections do list distinct, recognizable steps rather than being poorly defined.

3 / 5

Progressive Disclosure

The body is a short, well-sectioned overview and the single reference is clearly signaled and one level deep: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and references/rule.md exists (193 lines) holding exactly that: code examples, per-storage API guidance, server-side API details, and verification checks. Not 4 because the split is clean with no content that belongs in the reference inlined in SKILL.md.

5 / 5

Total

14

/

20

Passed

Description

70%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 focused, correctly structured trigger description with explicit 'Use when' guidance and a clear verification goal. Its main weaknesses are a fused what/when structure with a single action verb, and missing the most natural synonyms (GDPR, right to erasure, delete account) users would actually say.

Suggestions

Lead with a standalone capability statement before the trigger clause, e.g. 'Verifies that a user-facing data deletion flow exists — clearing client-side storage and triggering a server-side deletion request — during audits.'

Add high-probability trigger synonyms to the 'when' clause: GDPR, right to erasure, right to be forgotten, 'delete my account', data removal request.

Name the concrete checks performed (client-side storage clearance, deletion endpoint, confirmation UI) to lift the action coverage from one verb to several specific capabilities.

DimensionReasoningScore

Specificity

Names the domain (user data deletion compliance) with one concrete action — 'verify that a complete data deletion path exists' — aimed at specific audit targets ('account settings pages, privacy dashboards, or API routes'). Not 4 because it lists objects to inspect rather than several distinct capabilities or actions; not 2 because the action and domain are concrete, not generic.

3 / 5

Completeness

Explicitly answers both parts: 'Use when auditing account settings pages, privacy dashboards, or API routes' (when) and 'to verify that a complete data deletion path exists for users' (what). Not 5 because the 'what' is fused into the trigger clause rather than stated as standalone capabilities with concrete trigger variations; not 3 because both what and when are explicit, and the 'Use when' clause is present.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say during an audit ('account settings pages', 'privacy dashboards', 'API routes', 'data deletion'). Not 5 because common trigger synonyms are missing — 'GDPR', 'right to erasure', 'delete account', 'right to be forgotten' — which are the most likely user phrasings for this need.

4 / 5

Distinctiveness Conflict Risk

The deletion-path verification goal is a clear niche, and the target surfaces are specific. Not 5 because 'privacy dashboards' and 'account settings pages' overlap with other privacy-audit skills (cookie consent, privacy policy checks) in the same rule family; not 3 because the specific intent (complete data deletion path) keeps it mostly distinct.

4 / 5

Total

15

/

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/right-to-erasure/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.