Agent skill
Automated enforcement of GDPR Article 5(1)(e) storage limitation principle.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill automating-storage-limitation-controls -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills automating-storage-limitation-controls --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/automating-storage-limitation-controls .claude/skills/automating-storage-limitation-controls && 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 "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .claude/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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/automating-storage-limitation-controlsType 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 automating-storage-limitation-controls -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills automating-storage-limitation-controls --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/automating-storage-limitation-controls .agents/skills/automating-storage-limitation-controls && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .agents/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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 automating-storage-limitation-controls -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills automating-storage-limitation-controls --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/automating-storage-limitation-controls .cursor/skills/automating-storage-limitation-controls && 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 "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .cursor/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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/automating-storage-limitation-controls--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 automating-storage-limitation-controls -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills automating-storage-limitation-controls --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/automating-storage-limitation-controls .gemini/skills/automating-storage-limitation-controls && 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 "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .gemini/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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 automating-storage-limitation-controlsInstalls 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 automating-storage-limitation-controls -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/automating-storage-limitation-controls .github/skills/automating-storage-limitation-controls && 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 "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .github/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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 automating-storage-limitation-controls -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 automating-storage-limitation-controls --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/automating-storage-limitation-controls .opencode/skills/automating-storage-limitation-controls && 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 "automating-storage-limitation-controls" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/automating-storage-limitation-controls into .opencode/skills/automating-storage-limitation-controls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automating-storage-limitation-controls", 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.
automating-storage-limitation-controlsAutomated enforcement of GDPR Article 5(1)(e) storage limitation principle.
Automating Storage Limitation Controls is an agent skill from mukul975/Privacy-Data-Protection-Skills. Automated enforcement of GDPR Article 5(1)(e) storage limitation principle. Covers TTL-based deletion, retention policy engines, archival workflows, legal hold exemptions, and lifecycle automation. Includes technical implementation patterns for automated data expiry and defensible deletion across distributed systems.
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 and Authorization and RBAC. 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Automating Storage Limitation Controls loads about 2.4k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 923 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.
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.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 923 words, ~2,446 tokens.
.claude/skills/automating-storage-limitation-controls/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Article 5(1)(e) of the GDPR requires that personal data be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed." This is the storage limitation principle. Controllers must define retention periods for each category of personal data based on the purpose of processing (Article 13(2)(a) requires disclosure of retention periods or criteria).
Automation is critical because manual retention management at scale inevitably leads to compliance gaps. The EDPB Guidelines 4/2019 on Article 25 specifically identify automated deletion mechanisms as an example of data protection by design.
Each retention period must be justified by reference to the processing purpose, legal requirements, or legitimate business need:
| Data Category | Purpose | Lawful Basis | Retention Period | Retention Trigger | Legal Reference |
|---|---|---|---|---|---|
| Customer account data | Service delivery | Art. 6(1)(b) | Duration of contract + 90 days | Account closure | Art. 5(1)(e), Art. 17(1)(a) |
| Transaction records | Tax compliance | Art. 6(1)(c) | 10 years | Transaction date | Swiss CO Art. 958f, EU VAT Directive 2006/112/EC Art. 242 |
| Support tickets | Customer service | Art. 6(1)(b) | 3 years | Ticket closure | Art. 5(1)(e), limitation period |
| Server access logs | Security monitoring | Art. 6(1)(f) | 12 months | Log creation date | Art. 5(1)(e), ENISA recommendation |
| Marketing consent records | Accountability | Art. 6(1)(c) | Duration of consent + 5 years | Consent withdrawal | Art. 7(1), Art. 5(2) |
| Employment records | Legal obligation | Art. 6(1)(c) | Duration of employment + 10 years | Employment end | Swiss OR Art. 127-128 |
| Cookie analytics | Product improvement | Art. 6(1)(a) | 13 months | Data collection | ePrivacy Directive Art. 5(3), CNIL guidance |
| DPIA records | Accountability | Art. 6(1)(c) | Duration of processing + 3 years | Processing cessation | Art. 35, Art. 5(2) |
┌─────────────────────────────────────────────────────────────┐
│ Retention Policy Engine │
│ ┌───────────────┐ ┌────────────────┐ ┌───────────────┐ │
│ │ Policy Store │ │ TTL Calculator │ │ Legal Hold │ │
│ │ (per category)│ │ (trigger+period)│ │ Registry │ │
│ └───────┬───────┘ └───────┬────────┘ └──────┬────────┘ │
│ └──────────────────┼───────────────────┘ │
└─────────────────────────────┼───────────────────────────────┘
│
┌─────────────────────────────▼───────────────────────────────┐
│ Lifecycle Scheduler │
│ ┌──────────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Expiry Scanner │ │ Archive Mover│ │ Deletion │ │
│ │ (daily cron) │ │ (pre-delete) │ │ Executor │ │
│ └──────────────────┘ └──────────────┘ └──────────────┘ │
└─────────────────────────────┬───────────────────────────────┘
│
┌─────────────────────────────▼───────────────────────────────┐
│ Audit and Verification │
│ ┌──────────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Deletion Log │ │ Verification │ │ Exception │ │
│ │ (immutable) │ │ Scanner │ │ Reporter │ │
│ └──────────────────┘ └──────────────┘ └──────────────┘ │
└─────────────────────────────────────────────────────────────┘| Pattern | Description | Use Case | Complexity |
|---|---|---|---|
| TTL columns | Database column storing expiry timestamp; background job deletes expired rows | Single-database systems, Redis, DynamoDB | Low |
| Event-driven deletion | Lifecycle event (account closure) publishes deletion command to message queue | Microservice architectures | Medium |
| Tombstone + compaction | Mark records as deleted; background compaction physically removes data | Append-only stores, event sourcing | Medium |
| Cascade deletion | Delete propagates across foreign key relationships | Relational databases with referential integrity | Medium |
| Distributed saga | Coordinated deletion across multiple services with rollback on failure | Polyglot persistence, cross-service data | High |
| Crypto-shredding | Destroy the encryption key rendering the data unreadable without physical deletion | Systems where physical deletion is impractical (backups, immutable logs) | Medium |
Legal holds suspend automated deletion when data is subject to litigation, regulatory investigation, or audit proceedings.
Legal Hold Lifecycle:
Prism Data Systems AG Implementation:
| Hold Parameter | Value |
|---|---|
| Hold scope format | JSON document specifying data_categories, date_range_start, date_range_end, subject_identifiers, matter_reference |
| Hold registry | PostgreSQL table with immutable audit trail |
| Review cadence | Monthly by legal counsel, quarterly by DPO |
| Maximum hold duration without renewal | 12 months |
| Hold release approval | Dual approval: legal counsel + DPO |
| Tier | Storage Type | Access Pattern | Encryption | Retention Phase |
|---|---|---|---|---|
| Hot | Primary database (PostgreSQL) | Real-time read/write | AES-256-GCM field-level | Active processing |
| Warm | Object storage (S3-compatible, Glacier Instant Retrieval class) | Occasional read, no write | AES-256-GCM object-level | Post-purpose, pre-deletion (legal/audit) |
| Cold | Offline archive (tape/vault) | Restore on request (24-48h) | AES-256-GCM + envelope encryption | Statutory retention only |
Transition Rules for Prism Data Systems AG:
| Transition | Trigger | Automation |
|---|---|---|
| Hot → Warm | Purpose fulfilled (e.g., account closed) + 90 days | Daily lifecycle job |
| Warm → Cold | Warm retention period expires, statutory retention still applies | Monthly lifecycle job |
| Cold → Deletion | Statutory retention period expires, no legal hold active | Quarterly lifecycle job with DPO approval gate |
| Any → Legal Hold | Legal hold registered for matching scope | Immediate suspension |
Inventory data stores — Catalog every system that stores personal data, including primary databases, caches, message queues, logs, backups, and third-party integrations.
Map retention requirements — For each data category and processing purpose, determine the retention period based on purpose necessity, legal obligations, and limitation periods.
Implement TTL metadata — Add retention-related columns or metadata to each data store: created_at, retention_trigger_event, retention_trigger_date, ttl_expiry_date, legal_hold_id.
Deploy lifecycle scheduler — Implement a background service that scans for expired records daily, checks for active legal holds, and executes deletion or archival transitions.
Implement deletion verification — After each deletion cycle, run a verification scan to confirm that all targeted records have been removed from primary stores, replicas, and caches.
Configure backup rotation — Ensure that backup retention aligns with the longest applicable retention period. Implement crypto-shredding for backup media where granular deletion is impractical.
Deploy monitoring and alerting — Monitor deletion job success rates, flag records that exceed their TTL by more than 7 days, and alert on legal hold expirations.
© 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
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/automating-storage-limitation-controls of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Automating Storage Limitation Controls 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 |
|---|---|---|---|---|---|---|
| Automating Storage Limitation Controls this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Cis ControlsSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Tos Clause Scannerzebbern/claude-code-guide | 4.7k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Healthcare Phi Complianceaffaan-m/ECC | 277k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Policy OpaAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Fondo Security Basicsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT |
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection…
zebbern/claude-code-guide
Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues.
affaan-m/ECC
Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…
AgentSecOps/SecOpsAgentKit
Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).
jeremylongshore/tons-of-skills-marketplace
Apply security best practices for Fondo including OAuth token management, financial data protection, SOC 2 compliance, and access control.
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
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.
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.
Categories
Automated enforcement of GDPR Article 5(1)(e) storage limitation principle. Automating Storage Limitation Controls is an agent skill from mukul975/Privacy-Data-Protection-Skills. Automated enforcement of GDPR Article 5(1)(e) storage limitation principle.
Automating Storage Limitation Controls fits situations like: tasks that involve Privacy and GDPR; tasks that involve Authorization and RBAC.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill automating-storage-limitation-controls -a claude-code`. Or copy the skill folder (skills/privacy/automating-storage-limitation-controls in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/automating-storage-limitation-controls in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill automating-storage-limitation-controls -a codex`. Or copy the skill folder (skills/privacy/automating-storage-limitation-controls in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/automating-storage-limitation-controls in your project. Codex loads it when a task matches its description.
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 automating-storage-limitation-controls -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automating-storage-limitation-controls, .gemini/skills/automating-storage-limitation-controls, .github/skills/automating-storage-limitation-controls and .opencode/skills/automating-storage-limitation-controls in your project.
Going by SKILL.md and its folder, Automating Storage Limitation Controls needs Python for the scripts in its folder. Our summary lists: Python 3.
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.
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.
Automating Storage Limitation Controls 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.
About 2.4k tokens (SKILL.md is roughly 9.8k 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 2.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Automating Storage Limitation Controls: Cis Controls (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Tos Clause Scanner (zebbern/claude-code-guide, 4.7k stars), Healthcare Phi Compliance (affaan-m/ECC, 277k stars) and Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
