Implements NIST SP 800-88 Rev. An agent skill from mukul975/Privacy-Data-Protection-Skills.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill secure-data-destruction -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills secure-data-destruction --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/secure-data-destruction .claude/skills/secure-data-destruction && 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 "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .claude/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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/secure-data-destructionType 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 secure-data-destruction -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills secure-data-destruction --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/secure-data-destruction .agents/skills/secure-data-destruction && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .agents/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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 secure-data-destruction -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills secure-data-destruction --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/secure-data-destruction .cursor/skills/secure-data-destruction && 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 "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .cursor/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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/secure-data-destruction--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 secure-data-destruction -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills secure-data-destruction --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/secure-data-destruction .gemini/skills/secure-data-destruction && 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 "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .gemini/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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 secure-data-destructionInstalls 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 secure-data-destruction -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/secure-data-destruction .github/skills/secure-data-destruction && 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 "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .github/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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 secure-data-destruction -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 secure-data-destruction --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/secure-data-destruction .opencode/skills/secure-data-destruction && 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 "secure-data-destruction" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/secure-data-destruction into .opencode/skills/secure-data-destruction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "secure-data-destruction", 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.
secure-data-destructionImplements NIST SP 800-88 Rev. An agent skill from mukul975/Privacy-Data-Protection-Skills.
Secure Data Destruction is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements NIST SP 800-88 Rev. 1 media sanitization procedures including Clear, Purge, and Destroy methods for all media types. Covers certificate of destruction generation, verification procedures, vendor management for third-party destruction, and chain of custody documentation. Activate for data destruction, media sanitization, secure erasure, certificate of destruction queries.
Its SKILL.md is about 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 Vendor and procurement management and 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.
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.
Secure Data Destruction loads about 4k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 846 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). 846 words, ~3,967 tokens.
.claude/skills/secure-data-destruction/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Secure data destruction ensures that personal data is rendered permanently irrecoverable when retention periods expire, assets are decommissioned, or erasure is required. NIST Special Publication 800-88 Revision 1 (Guidelines for Media Sanitization) provides the authoritative framework for sanitization methods. This skill covers the three sanitization levels (Clear, Purge, Destroy), media-specific procedures, certificate of destruction generation, verification requirements, and vendor management for outsourced destruction services.
Defines three levels of media sanitization:
Personal data shall be processed in a manner that ensures appropriate security, including protection against unauthorised or unlawful processing and against accidental loss, destruction, or damage. Secure destruction is the final step in the data lifecycle security chain.
Equipment containing storage media shall be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use.
The ICO recommends that organisations ensure personal data is disposed of securely, whether in electronic or paper form, and that appropriate verification is conducted to confirm destruction.
European standard for organizations providing secure destruction services, including requirements for personnel, premises, equipment, and processes.
The appropriate sanitization method depends on the confidentiality level of the data and the future disposition of the media:
[Media Contains Personal Data?]
│
├── No ──► Standard disposal (no sanitization required)
│
└── Yes ──► [Confidentiality Classification?]
│
├── Standard Personal Data
│ └── [Media Disposition?]
│ ├── Reuse within org ──► CLEAR
│ ├── Reuse external ──► PURGE
│ └── Disposal ──► DESTROY
│
├── Special Category Data (Art. 9)
│ └── [Media Disposition?]
│ ├── Reuse within org ──► PURGE
│ ├── Reuse external ──► DESTROY
│ └── Disposal ──► DESTROY
│
└── Highly Sensitive (financial, security, legal)
└── DESTROY (regardless of disposition)| Media Type | CLEAR | PURGE | DESTROY |
|---|---|---|---|
| HDD (magnetic) | ATA Secure Erase (single pass overwrite with fixed pattern) | ATA Secure Erase Enhanced (multiple pass with verification); Degaussing with NSA/CESG-approved degausser | Physical destruction: shredding (particle size ≤ 2mm), disintegration, incineration, or smelting |
| SSD / Flash | ATA Secure Erase (vendor implementation) | ATA Sanitize Block Erase or Crypto Erase (if SED); NVMe Format with Crypto Erase | Physical destruction: shredding (particle size ≤ 2mm), disintegration, incineration |
| Magnetic tape | Overwrite entire tape with fixed pattern (single pass) | Degaussing with NSA/CESG-approved degausser rated for tape coercivity | Physical destruction: shredding, incineration |
| Optical media (CD/DVD/Blu-ray) | Not applicable (WORM media) | Not applicable (WORM media) | Physical destruction: shredding (particle size ≤ 0.5mm), incineration |
| USB flash drives | ATA Secure Erase (if supported) | Crypto Erase (if SED); vendor-specific sanitize command | Physical destruction: shredding, disintegration |
| Mobile devices | Factory reset + encryption verification | Crypto Erase (full-device encryption key destruction) | Physical destruction: shredding |
| Paper documents | Not applicable | Not applicable | Cross-cut shredding (DIN 66399 P-4 minimum; P-5 for special category data); incineration |
| Virtual machines / cloud instances | Delete VM and associated disks; verify deallocation | Crypto Erase (destroy encryption keys); vendor-certified sanitization | Request destruction certificate from cloud provider (limited availability) |
| Level | Particle Size | Use Case |
|---|---|---|
| P-1 | ≤ 12mm strips | General, non-personal documents |
| P-2 | ≤ 6mm strips | Internal documents, low sensitivity |
| P-3 | ≤ 2mm strips or 320mm² particles | Personal data (standard) |
| P-4 | ≤ 160mm² particles (max 6mm width) | Minimum for GDPR personal data |
| P-5 | ≤ 30mm² particles (max 2mm width) | Special category data, financial data |
| P-6 | ≤ 10mm² particles (max 1mm width) | Classified, intelligence-grade |
| P-7 | ≤ 5mm² particles (max 1mm width) | Top secret, maximum security |
PROCEDURE: IN-HOUSE ELECTRONIC MEDIA SANITIZATION
Organization: Orion Data Vault Corp
Procedure ID: SEC-DEST-001
1. ASSET IDENTIFICATION
- Record asset tag, serial number, media type, capacity
- Record data classification level
- Record owning department and data categories stored
- Verify no active litigation hold applies (check litigation hold register)
2. CHAIN OF CUSTODY
- Collect media from originating department with signed handover form
- Transport in sealed, tamper-evident container
- Log receipt in destruction register with timestamp and receiving officer
3. SANITIZATION EXECUTION
a. Select sanitization method per decision framework above
b. For CLEAR:
- Execute ATA Secure Erase / vendor secure erase command
- Log start time, end time, tool used, firmware version
c. For PURGE:
- Execute degaussing (record degausser model, field strength, pass count)
- OR execute Crypto Erase (record key destruction confirmation)
- OR execute ATA Sanitize command (record command type and completion)
d. For DESTROY:
- Transfer to destruction equipment (shredder, disintegrator)
- Execute destruction (record equipment model, particle size achieved)
- Collect destroyed material in secure waste container
4. VERIFICATION
- For CLEAR/PURGE: Attempt to read data from sanitized media using forensic tools
- Verification must be performed by a different individual than the one who executed sanitization
- For DESTROY: Visual inspection to confirm media is physically irrecoverable
- Record verification result (PASS/FAIL)
- If FAIL: Escalate to next sanitization level
5. DOCUMENTATION
- Generate Certificate of Destruction (see template below)
- Update asset register to mark asset as destroyed/sanitized
- File certificate in destruction records (retain for 7 years)PROCEDURE: THIRD-PARTY DESTRUCTION SERVICE MANAGEMENT
Organization: Orion Data Vault Corp
Procedure ID: SEC-DEST-002
1. VENDOR QUALIFICATION (pre-engagement)
- Verify EN 15713:2009 certification (or equivalent)
- Verify ISO 27001:2022 certification
- Verify ADISA (Asset Disposal & Information Security Alliance) certification
- Review vendor's data processing agreement (Art. 28 GDPR)
- Conduct on-site audit of destruction facility
- Verify insurance coverage (minimum £5M professional indemnity)
- Verify DBS checks on all personnel handling media
2. PRE-COLLECTION PREPARATION
- Complete asset inventory of items for destruction
- Seal items in tamper-evident containers
- Affix unique tracking barcode to each container
- Generate collection manifest listing all assets by serial number
3. COLLECTION AND TRANSPORT
- Vendor arrives with GPS-tracked, locked vehicle
- Verify driver identity against pre-approved personnel list
- Hand over sealed containers with signed collection manifest
- Retain copy of collection manifest
4. DESTRUCTION EXECUTION (at vendor facility)
- Option A: On-site destruction (vendor brings mobile shredder)
- Orion Data Vault Corp representative witnesses destruction
- Video recording of destruction process
- Option B: Off-site destruction (at vendor facility)
- GPS tracking of vehicle to vendor facility
- Video evidence of destruction provided within 24 hours
5. CERTIFICATE OF DESTRUCTION
- Vendor provides Certificate of Destruction within 5 business days
- Certificate must include: asset serial numbers, destruction method, particle size,
date/time, location, personnel involved, verification method
- Cross-reference certificate against collection manifest (100% match required)
6. ANNUAL VENDOR AUDIT
- Annual on-site audit of vendor facility and processes
- Review vendor's incident register
- Verify continued certification compliance
- Review subcontractor arrangements (if any)═══════════════════════════════════════════════════════════════
CERTIFICATE OF DESTRUCTION
Orion Data Vault Corp
═══════════════════════════════════════════════════════════════
Certificate Number: COD-2026-0087
Date of Destruction: 2026-03-14
Location: Orion Data Vault Corp — Secure Destruction Room B2
REQUESTING DEPARTMENT: IT Operations
AUTHORISED BY: [Information Security Manager Name]
DATA PROTECTION OFFICER APPROVAL: [DPO Name] — Approved 2026-03-12
ASSETS DESTROYED:
┌────────────┬──────────────┬──────────┬──────────┬───────────────┬──────────────┐
│ Asset Tag │ Serial No. │ Type │ Capacity │ Data Class. │ Method │
├────────────┼──────────────┼──────────┼──────────┼───────────────┼──────────────┤
│ OD-SRV-441 │ WD-2TB-A8F21 │ HDD 3.5" │ 2 TB │ Special Cat. │ DESTROY │
│ OD-SRV-442 │ WD-2TB-A8F22 │ HDD 3.5" │ 2 TB │ Special Cat. │ DESTROY │
│ OD-LAP-219 │ SM-512-C3E01 │ SSD M.2 │ 512 GB │ Standard PD │ PURGE+DESTROY│
│ OD-USB-088 │ KN-64G-D1F03 │ USB Flash│ 64 GB │ Standard PD │ DESTROY │
│ OD-TAP-017 │ LT-8TB-E2G04 │ LTO-8 │ 12 TB │ Financial │ DESTROY │
└────────────┴──────────────┴──────────┴──────────┴───────────────┴──────────────┘
SANITIZATION DETAILS:
- Method: Physical destruction via industrial shredder (model: HSM Powerline FA 500.3)
- Particle size achieved: 2mm (compliant with DIN 66399 E-4 / H-5)
- Pre-destruction purge: Degaussing performed on HDDs and tape (Verity Systems V94 DG,
field strength: 1.2 Tesla, 2 passes)
VERIFICATION:
- Post-shredding inspection: PASS — no intact media fragments exceeding particle size spec
- Verified by: [Security Officer Name] — independent of destruction operator
- Photographic evidence: Retained in destruction records (file: COD-2026-0087-photos.zip)
WASTE DISPOSAL:
- Destroyed material transferred to licensed WEEE recycler
- Recycler: [Licensed Recycler Name], License No: [WEEE License]
- Transfer note reference: WTN-2026-0087
CHAIN OF CUSTODY:
- Collected from: Server Room A (Rack 14) by [IT Technician Name]
- Collection date: 2026-03-13
- Stored in: Secure Destruction Staging Area (locked, access-controlled)
- Destruction witnessed by: [Security Officer Name]
CERTIFICATION:
I certify that the assets listed above have been destroyed in accordance
with NIST SP 800-88 Rev. 1 guidelines and Orion Data Vault Corp
Secure Destruction Procedure SEC-DEST-001.
Destruction Operator: _________________________ Date: 2026-03-14
Verification Officer: _________________________ Date: 2026-03-14
DPO Acknowledgement: _________________________ Date: __________
═══════════════════════════════════════════════════════════════
RETAIN THIS CERTIFICATE FOR 7 YEARS
Next review: 2033-03-14
═══════════════════════════════════════════════════════════════| Requirement | Standard | Evidence Required |
|---|---|---|
| Information security management | ISO/IEC 27001:2022 | Current certificate from accredited body |
| Secure destruction services | EN 15713:2009 | Current certificate |
| Asset disposal security | ADISA certification | Current ADISA certificate with relevant claim level |
| Data processing agreement | GDPR Art. 28 | Signed DPA covering destruction as processing activity |
| Personnel security | DBS/vetting checks | Confirmation that all personnel with access to media are vetted |
| Insurance | Professional indemnity | Certificate of insurance (minimum £5M) |
| Environmental compliance | WEEE Regulations 2013 | Waste carrier license; evidence of WEEE-compliant recycling |
| Business continuity | Operational resilience | BCP documentation; alternative facility available |
| Incident management | Breach notification capability | Documented incident response procedure; 24-hour notification commitment |
| Transport security | Secure logistics | GPS-tracked vehicles; locked and alarmed compartments |
| Metric | Target | Measurement |
|---|---|---|
| Certificate of destruction delivery time | Within 5 business days of destruction | Per engagement |
| Collection scheduling reliability | Within agreed collection window (±2 hours) | Per collection |
| Asset inventory accuracy | 100% match between manifest and certificate | Per engagement |
| Incident count | Zero security incidents | Annual |
| Certification maintenance | All certifications current | Annual check |
| Audit findings | Zero critical or major findings | Annual audit |
| Record | Retention Period | Storage |
|---|---|---|
| Certificate of Destruction | 7 years from destruction date | Secure document management system (encrypted) |
| Collection manifests | 7 years from collection date | Filed with associated certificate |
| Chain of custody logs | 7 years from destruction date | Filed with associated certificate |
| Photographic/video evidence | 3 years from destruction date | Secure encrypted storage |
| Vendor audit reports | 7 years from audit date | Vendor management file |
| Vendor DPA | Duration of relationship + 6 years | Legal records |
© 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/secure-data-destruction of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Secure Data Destruction 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 |
|---|---|---|---|---|---|---|
| Secure Data Destruction this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Regulatory Deal Card Generator Patrick Munrolawve-ai/awesome-legal-skills | 836 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Tech Contract Negotiation Patrick Munrolawve-ai/awesome-legal-skills | 836 | — | ~4.9k | Automated safety check: Pass | AGPL-3.0 | |
| AI Governance Reviewer Carl Ditzlerlawve-ai/awesome-legal-skills | 836 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Operational Designmagnus919/hermes-profiles | 281 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Operational Designmagnus919/agent-skills | 113 | — | ~1.4k | Automated safety check: Pass | MIT |
lawve-ai/awesome-legal-skills
Generates standalone interactive HTML "deal cards" that translate complex regulations into negotiation-ready reference tools, systematically distinguishing mandatory obligations from negotiable…
lawve-ai/awesome-legal-skills
Systematic contract negotiation strategies for technology services agreements with German/EU law specificity.
lawve-ai/awesome-legal-skills
A skill your agent uses when the user wants an AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk review of an internal AI use case, an AI product feature, an LLM workflow…
magnus919/hermes-profiles
COO methodology for process design, organizational scaling, operational metrics, compliance and audit, vendor management, and team topology.
magnus919/agent-skills
Design and improve operational processes, controls, metrics, vendors, and scaling models through bounded pilots and evidence.
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
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.
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Categories
Implements NIST SP 800-88 Rev. An agent skill from mukul975/Privacy-Data-Protection-Skills. Secure Data Destruction is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements NIST SP 800-88 Rev.
Secure Data Destruction fits situations like: tasks that involve Vendor and procurement management; tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill secure-data-destruction -a claude-code`. Or copy the skill folder (skills/privacy/secure-data-destruction in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/secure-data-destruction in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill secure-data-destruction -a codex`. Or copy the skill folder (skills/privacy/secure-data-destruction in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/secure-data-destruction 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 secure-data-destruction -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/secure-data-destruction, .gemini/skills/secure-data-destruction, .github/skills/secure-data-destruction and .opencode/skills/secure-data-destruction in your project.
Going by SKILL.md and its folder, Secure Data Destruction 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.
Secure Data Destruction 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 4k tokens (SKILL.md is roughly 16k 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.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Secure Data Destruction: Regulatory Deal Card Generator Patrick Munro (lawve-ai/awesome-legal-skills, 836 stars), Tech Contract Negotiation Patrick Munro (lawve-ai/awesome-legal-skills, 836 stars), AI Governance Reviewer Carl Ditzler (lawve-ai/awesome-legal-skills, 836 stars) and Operational Design (magnus919/hermes-profiles, 281 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 295 GitHub stars. The repository holds 278 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.
