C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and…
Install Right To Erasure
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills 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/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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 mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-erasure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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 mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-erasure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/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 mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills 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/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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 mukul975/Privacy-Data-Protection-Skills 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 mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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 mukul975/Privacy-Data-Protection-Skills --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 mukul975/Privacy-Data-Protection-Skills right-to-erasure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/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
- 301
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,081 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and…
- Works in 8 steps: Receive and Log the Erasure Request → Identify the Ground for Erasure → Check for Applicable Exceptions → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Erasure Processing Workflow and Response Timeline
- Runs Python scripts from its folder
What it does
Right To Erasure is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and third-party notification under Article 19. Activate for erasure request, deletion request, right to be forgotten, Art. 17 queries.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the right-to-erasure skill to implement the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for…”
- “/right-to-erasure”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. 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
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 2.4k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 1,081 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); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,081 words, ~2,410 tokens.
Download SKILL.mdSave it as
.claude/skills/right-to-erasure/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- right-to-erasure
- description
- Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and third-party notification under Article 19. Activate for erasure request, deletion request, right to be forgotten, Art. 17 queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- right-to-erasure, right-to-be-forgotten, gdpr-article-17, data-deletion, anonymization
Implementing Right to Erasure Workflow
Overview
The right to erasure under GDPR Article 17 allows data subjects to request the deletion of their personal data. This right is not absolute — it is subject to specific grounds for erasure and a set of exceptions. This skill provides the complete operational procedure for receiving, assessing, executing, and confirming erasure requests.
Legal Foundation
GDPR Article 17 — Right to Erasure ('Right to be Forgotten')
Six Grounds for Erasure Under Art. 17(1)
The data subject has the right to obtain erasure where one of the following grounds applies:
- Art. 17(1)(a) — Purpose fulfilment: The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.
- Art. 17(1)(b) — Consent withdrawal: The data subject withdraws consent on which the processing is based under Art. 6(1)(a) or Art. 9(2)(a), and there is no other legal ground for the processing.
- Art. 17(1)(c) — Successful objection: The data subject objects pursuant to Art. 21(1) and there are no overriding legitimate grounds for the processing, or the data subject objects to processing for direct marketing under Art. 21(2).
- Art. 17(1)(d) — Unlawful processing: The personal data have been unlawfully processed.
- Art. 17(1)(e) — Legal obligation: The personal data have to be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.
- Art. 17(1)(f) — Child's data (information society services): The personal data have been collected in relation to the offer of information society services referred to in Art. 8(1).
Five Exceptions Under Art. 17(3)
Erasure does NOT apply to the extent that processing is necessary for:
- Art. 17(3)(a) — Freedom of expression and information: Exercising the right of freedom of expression and information.
- Art. 17(3)(b) — Legal obligation: Compliance with a legal obligation which requires processing by Union or Member State law to which the controller is subject, or for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.
- Art. 17(3)(c) — Public health: Reasons of public interest in the area of public health in accordance with Art. 9(2)(h) and (i), and Art. 9(3).
- Art. 17(3)(d) — Archiving/research: Archiving purposes in the public interest, scientific or historical research purposes, or statistical purposes in accordance with Art. 89(1), in so far as the right to erasure is likely to render impossible or seriously impair the achievement of the objectives of that processing.
- Art. 17(3)(e) — Legal claims: The establishment, exercise, or defence of legal claims.
GDPR Article 19 — Notification Obligation
The controller shall communicate any erasure of personal data to each recipient to whom the personal data have been disclosed, unless this proves impossible or involves disproportionate effort. The controller shall inform the data subject about those recipients if the data subject requests it.
Erasure Processing Workflow
Step 1: Receive and Log the Erasure Request
- Log the request with a unique reference (format: ERA-YYYY-NNNN).
- Record the channel, timestamp (UTC), and identity of the requester.
- Send acknowledgement within 3 business days.
- Verify identity using the same tiered approach as DSAR processing (low/medium/high risk).
Step 2: Identify the Ground for Erasure
- Review the request to determine which of the six grounds under Art. 17(1)(a)-(f) the data subject is invoking.
- If the data subject has not specified a ground, assess which ground(s) are applicable based on the facts.
- Document the identified ground(s) in the processing record.
Step 3: Check for Applicable Exceptions
For each ground identified, evaluate whether any of the five exceptions under Art. 17(3)(a)-(e) apply:
| Exception | Assessment Question | Common Scenarios at Meridian Analytics Ltd |
|---|---|---|
| Freedom of expression (a) | Is this data published as part of journalism or public discourse? | Published research reports, public-facing analytics |
| Legal obligation (b) | Is there a statutory retention requirement? | Financial records under Companies Act 2006 (6 years), tax records under HMRC requirements (6 years), anti-money laundering records under MLR 2017 (5 years) |
| Public health (c) | Is this data necessary for public health purposes? | Rare — applies to health data processors |
| Archiving/research (d) | Would erasure render research impossible or seriously impaired? | Anonymised datasets used in published research |
| Legal claims (e) | Are there pending or anticipated legal proceedings involving this data? | Active disputes, regulatory investigations, litigation hold data |
Show full SKILL.md (367 more words)Show less
Step 4: Deletion vs Anonymization Decision Tree
[Erasure Ground Established & No Exception Applies]
│
▼
[Can data be permanently deleted from all systems?]
│
├── Yes ──► [PERMANENT DELETION]
│ - Remove from primary databases
│ - Remove from backup systems within next backup cycle
│ - Remove from third-party processors (Art. 19)
│ - Purge from caches, logs, and temporary storage
│ - Verify deletion across all systems
│
└── No ──► [Assess why deletion is not possible]
│
├── Technical constraint (embedded in backup tapes)
│ └── [ANONYMIZE + schedule deletion at next backup rotation]
│ [Maximum retention of backup: 90 days at Meridian Analytics Ltd]
│
├── Partial exception applies (some data needed for legal obligation)
│ └── [PARTIAL DELETION + ANONYMIZATION]
│ [Delete data not subject to exception]
│ [Retain excepted data with restricted access]
│ [Anonymize where possible]
│
└── Data is intermingled with other subjects' data
└── [TARGETED ANONYMIZATION]
[Replace identifiers with irreversible pseudonyms]
[Remove all direct identifiers]
[Verify re-identification risk < 0.05%]Step 5: Execute the Erasure
- Primary systems: Execute deletion queries/commands across all identified data stores.
- Backup systems: Flag data for deletion at next backup rotation cycle (document the expected completion date, maximum 90 days).
- Third-party processors: Issue erasure instructions to all processors under Art. 28 agreements. Record the instruction date and request confirmation of completion.
- Caches and temporary storage: Purge application caches, CDN caches, and temporary files.
- Search engine de-indexing: Where personal data was made public (Art. 17(2)), submit de-indexing requests to search engines.
Step 6: Notify Third-Party Recipients (Art. 19)
- Identify all recipients to whom the personal data was disclosed (reference the Art. 30 records of processing).
- Send erasure notification to each recipient with:
- The data subject reference (anonymised)
- The specific data to be erased
- The legal basis for the erasure request
- A deadline for confirmation of erasure (14 calendar days)
- Record each notification and the recipient's confirmation.
- If the data subject requests it, provide the list of recipients notified.
Step 7: Verify and Confirm
- Run verification checks across all systems to confirm data has been erased or anonymised.
- Obtain confirmation from all third-party processors.
- Compile the erasure completion record.
- Send confirmation to the data subject within the 30-day response deadline, including:
- Confirmation that erasure has been completed
- Any partial exceptions applied (with legal basis)
- Expected completion date for backup system erasure (if applicable)
- List of third parties notified (if requested)
Step 8: Record Retention
- Retain the erasure processing record (request details, assessment, execution log, confirmations) for 3 years.
- The record must NOT contain the erased personal data itself — only metadata about the erasure process.
- Store a suppression record (minimum identifiers needed to recognise future requests from the same individual and prevent re-collection) where appropriate.
Response Timeline
- Standard deadline: 30 calendar days from receipt (or from identity verification).
- Extension: Up to 60 additional days for complex requests (Art. 12(3)), with notification to the data subject within the initial 30-day period.
- Backup erasure: Must be completed within the next full backup rotation cycle (maximum 90 days at Meridian Analytics Ltd), documented in the response.
© mukul975, Apache-2.0. 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 4 other files (scripts, references, assets) in skills/privacy/right-to-erasure of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
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 skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about Right To Erasure
What does Right To Erasure do?
Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and…. Right To Erasure is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and third-party notification under Article 19.
When should I use Right To Erasure?
Right To Erasure fits situations like: tasks that involve Privacy and GDPR.
How do I install Right To Erasure in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a claude-code`. Or copy the skill folder (skills/privacy/right-to-erasure in mukul975/Privacy-Data-Protection-Skills) 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 mukul975/Privacy-Data-Protection-Skills --skill right-to-erasure -a codex`. Or copy the skill folder (skills/privacy/right-to-erasure in mukul975/Privacy-Data-Protection-Skills) 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 mukul975/Privacy-Data-Protection-Skills --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?
Going by SKILL.md and its folder, Right To Erasure needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Right To Erasure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Right To Erasure use?
Right To Erasure is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Right To Erasure use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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.7k 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: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 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?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.