Paper to Chinese Patent Drafter
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
A skill your agent uses when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
Install Right To Erasure
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/right-to-erasure .claude/skills/right-to-erasure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .claude/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/right-to-erasure .agents/skills/right-to-erasure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .agents/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/right-to-erasure .cursor/skills/right-to-erasure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .cursor/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/right-to-erasure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/right-to-erasure .gemini/skills/right-to-erasure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .gemini/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/right-to-erasure .github/skills/right-to-erasure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .github/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist right-to-erasure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/right-to-erasure .opencode/skills/right-to-erasure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "right-to-erasure" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/right-to-erasure into .opencode/skills/right-to-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-erasure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
right-to-erasure- GitHub stars
- 74k
- Token cost
- ~512 tokens
- SKILL.md length
- 234 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
- Auditing account settings pages
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Privacy dashboards
What it does
Right To Erasure is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Legal & Compliance. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Auditing account settings pages
- Privacy dashboards
- API routes to verify that a complete data deletion path exists for users
Example prompts
- “/right-to-erasure”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Right To Erasure loads about 512 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 39 tokens; SKILL.md has 234 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 234 words, ~512 tokens.
Download SKILL.mdSave it as
.claude/skills/right-to-erasure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- right-to-erasure
- description
- Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
- metadata.category
- privacy
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 60
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/privacy/right-to-erasure
Implement a user-facing data deletion mechanism
GDPR Article 17 gives EU residents the right to have their personal data erased when it is no longer necessary for the purpose it was collected, or when they withdraw consent. Failing to honour this right can result in regulatory fines of up to €20 million or 4% of global annual turnover. Providing a clear deletion flow also builds trust with users who value control over their data.
Quick Reference
- Provide a visible "Delete my account / data" option in account settings
- Clear all client-side storage: localStorage, sessionStorage, IndexedDB, and cookies
- Send a deletion request to the server and confirm receipt to the user
- Complete deletion within 30 days as required by GDPR Article 17
Check
Check whether this application provides a user-facing data deletion mechanism that clears all client-side storage and triggers a server-side deletion request.
Fix
Implement a data deletion flow that clears localStorage, sessionStorage, IndexedDB, and cookies, then sends a deletion request to the server and shows confirmation to the user.
Explain
Explain GDPR Article 17 (right to erasure) and what a compliant data deletion flow must cover, including both client-side and server-side data.
Code Review
Review account settings, privacy pages, and API routes for a data deletion endpoint. Flag missing client-side storage clearance, absent confirmation UI, or missing server-side deletion calls.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/privacy/right-to-erasure
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/right-to-erasure of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Right To Erasure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Right To Erasure this skillthedaviddias/Front-End-Checklist | 74k | — | ~512 | Automated safety check: Pass | MIT | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 47k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Contract Reviewevolsb/claude-legal-skill | 464 | 1 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Legal Clinic Client Intakeanthropics/claude-for-legal | 9.6k | 3 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 107 | 1 repos | ~959 | Automated safety check: Pass | None |
Similar skills
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Contract Review
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
- Official
Legal Clinic Client Intake
anthropics/claude-for-legal
Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.
Paper To Cn Patent
snipp-zha/Paper-to-patent-Skill
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.
Employment Contract Templates
ynulihao/AgentSkillOS
Create employment contracts, offer letters, and HR policy documents following legal best practices.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Right To Erasure
What does Right To Erasure do?
A skill your agent uses when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users. Right To Erasure is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
When should I use Right To Erasure?
Right To Erasure fits situations like: auditing account settings pages; privacy dashboards; API routes to verify that a complete data deletion path exists for users.
How do I install Right To Erasure in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a claude-code`. Or copy the skill folder (skills/right-to-erasure in thedaviddias/Front-End-Checklist) into .claude/skills/right-to-erasure in your project. Claude Code loads it when a task matches its description.
How do I install Right To Erasure in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a codex`. Or copy the skill folder (skills/right-to-erasure in thedaviddias/Front-End-Checklist) into .agents/skills/right-to-erasure in your project. Codex loads it when a task matches its description.
Can I use Right To Erasure in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill right-to-erasure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/right-to-erasure, .gemini/skills/right-to-erasure, .github/skills/right-to-erasure and .opencode/skills/right-to-erasure in your project.
What does Right To Erasure need to run?
SKILL.md names no scripts, command-line tools or credentials: Right To Erasure is instructions for the agent only.
Does Right To Erasure access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Right To Erasure safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Right To Erasure use?
Right To Erasure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Right To Erasure use?
About 512 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Right To Erasure?
Skills that share tags, products or a category with Right To Erasure: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), C15t (c15t/c15t, 1.9k stars), Contract Review (evolsb/claude-legal-skill, 464 stars) and Legal Clinic Client Intake (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Right To Erasure?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.