Legal Compliance
travisjneuman/.claude
Legal and compliance expertise for corporate governance, contract analysis, regulatory compliance (SOX, GDPR, HIPAA), risk assessment, intellectual property, and litigation management.
Manages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention…
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill litigation-hold-mgmt -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills litigation-hold-mgmt --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/litigation-hold-mgmt .claude/skills/litigation-hold-mgmt && 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 "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .claude/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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/litigation-hold-mgmtType 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 litigation-hold-mgmt -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills litigation-hold-mgmt --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/litigation-hold-mgmt .agents/skills/litigation-hold-mgmt && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .agents/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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 litigation-hold-mgmt -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills litigation-hold-mgmt --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/litigation-hold-mgmt .cursor/skills/litigation-hold-mgmt && 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 "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .cursor/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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/litigation-hold-mgmt--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 litigation-hold-mgmt -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills litigation-hold-mgmt --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/litigation-hold-mgmt .gemini/skills/litigation-hold-mgmt && 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 "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .gemini/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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 litigation-hold-mgmtInstalls 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 litigation-hold-mgmt -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/litigation-hold-mgmt .github/skills/litigation-hold-mgmt && 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 "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .github/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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 litigation-hold-mgmt -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 litigation-hold-mgmt --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/litigation-hold-mgmt .opencode/skills/litigation-hold-mgmt && 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 "litigation-hold-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/litigation-hold-mgmt into .opencode/skills/litigation-hold-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "litigation-hold-mgmt", 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.
litigation-hold-mgmtManages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention…
Litigation Hold Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention schedules. Covers litigation hold registers, compliance monitoring, and Art. 17(3)(e) exception documentation. Activate for legal hold, litigation preservation, data freeze, e-discovery hold queries.
Its SKILL.md is about 3.6k 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 Legal research 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.
6 steps, taken from the step headings 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.
Shell commands in SKILL.md call:
gcloudFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gcloud, which can reach the network depending on how they are called.
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.
Litigation Hold Mgmt loads about 3.6k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 935 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). 935 words, ~3,612 tokens.
.claude/skills/litigation-hold-mgmt/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.A litigation hold (also called legal hold or preservation order) is a directive to preserve all data and documents relevant to pending or reasonably anticipated litigation, regulatory investigation, or audit. Litigation holds override normal retention schedules and automated deletion processes — data subject to a hold must NOT be deleted, modified, or destroyed until the hold is formally released. This skill provides the complete operational framework for issuing, tracking, implementing, and releasing litigation holds, including the critical interaction between holds and GDPR data retention and erasure obligations.
The right to erasure does not apply where processing is necessary for the establishment, exercise, or defence of legal claims. This is the primary GDPR basis for retaining personal data under a litigation hold beyond its normal retention period.
In England and Wales, the duty to preserve documents arises when litigation is reasonably contemplated or has commenced:
Regulatory bodies (European Commission, national competition authorities, financial regulators) may require preservation of documents relevant to an investigation. Failure to preserve can constitute obstruction.
A litigation hold must be issued when any of the following events occur:
| Trigger Category | Specific Events | Response Time |
|---|---|---|
| Litigation filed | Claim form received; writ served; arbitration notice received | Immediate (within 24 hours) |
| Litigation anticipated | Pre-action protocol letter received; demand letter received; formal complaint indicating likely litigation | Within 48 hours |
| Regulatory investigation | Notice of investigation; dawn raid; regulatory inquiry letter; request for information from supervisory authority | Immediate (within 24 hours) |
| Internal investigation | Whistleblower report triggering formal investigation; fraud suspicion; compliance breach identified | Within 48 hours |
| DPA inquiry | Data protection authority opens formal investigation or requests information under GDPR Art. 58 | Within 48 hours |
| Tax audit | HMRC opens formal enquiry; VAT inspection notice | Within 48 hours |
| Employment dispute | Tribunal claim filed; formal grievance raising likelihood of tribunal proceedings | Within 48 hours |
LITIGATION HOLD SCOPE DEFINITION — Orion Data Vault Corp
---------------------------------------------------------
Hold Reference: LH-2026-0023
Matter: [Description of litigation/investigation]
Legal Counsel: [Internal/External counsel name]
Date Issued: 2026-03-14
Anticipated Duration: [Estimate — reassess quarterly]
SCOPE — DATA TO PRESERVE:
1. Date Range: [Start date] to [End date / ongoing]
2. Data Subjects: [Named individuals, departments, or "all"]
3. Data Categories:
□ Email and electronic communications
□ Documents (Word, Excel, PowerPoint, PDF)
□ Financial records and transactions
□ Customer/client records
□ Employee records
□ CCTV/surveillance footage
□ Access logs and audit trails
□ Database records (specify: _____________)
□ Backup tapes/archives
□ Mobile device data (text messages, call logs)
□ Collaboration platforms (Teams, Slack, SharePoint)
□ Other: _____________
4. Systems in Scope:
□ Email system (Exchange/Gmail)
□ File servers / network drives
□ SharePoint / OneDrive / Google Drive
□ CRM (Salesforce)
□ ERP (SAP)
□ HR system
□ Financial system
□ Cloud storage (AWS S3 / Azure / GCP)
□ Backup systems
□ Messaging platforms
□ Other: _____________
5. Custodians (individuals who may hold relevant data):
- [Name, Title, Department]
- [Name, Title, Department]
- [Name, Title, Department]
EXCLUSIONS:
- [Specify any data explicitly outside scope]
INTERACTION WITH RETENTION SCHEDULE:
- Normal retention schedule: SUSPENDED for all in-scope data
- Automated deletion: PAUSED for in-scope data categories
- Art. 17 erasure requests: EXCEPTION applies under Art. 17(3)(e)Every individual identified as a custodian must receive a formal hold notice:
LITIGATION HOLD NOTICE — CONFIDENTIAL
Orion Data Vault Corp
To: [Custodian Name, Title]
From: [General Counsel / Legal Department]
Date: [YYYY-MM-DD]
Re: Litigation Hold — Reference LH-2026-0023
DIRECTIVE: PRESERVE ALL POTENTIALLY RELEVANT DATA
You are hereby directed to preserve all documents and electronically
stored information (ESI) that may be relevant to the above-referenced
matter. This obligation is effective IMMEDIATELY and supersedes all
existing retention schedules and deletion policies.
WHAT YOU MUST DO:
1. STOP all deletion, destruction, or modification of potentially
relevant documents and data.
2. PRESERVE all emails, documents, files, messages, voicemails,
text messages, and other records related to [description of
subject matter].
3. DISABLE any auto-delete functions on your email or messaging
accounts for the duration of this hold.
4. DO NOT move, rename, or reorganize files that may be relevant.
5. PRESERVE all physical documents (paper files, notebooks, etc.).
SCOPE:
- Time period: [Start date] to present
- Subject matter: [Description]
- Document types: All formats (electronic and physical)
THIS HOLD REMAINS IN EFFECT until you receive a formal written
release notice from the Legal Department. Do not assume the hold
has been lifted based on the passage of time or resolution of
the underlying matter.
QUESTIONS: Contact [Legal Department contact] immediately if you
have any questions about this notice or are unsure whether specific
documents fall within scope.
ACKNOWLEDGEMENT REQUIRED: Please confirm receipt and understanding
of this notice by signing below and returning to the Legal
Department within 48 hours.
I acknowledge receipt and understanding of this Litigation Hold Notice.
Name: ________________________
Signature: ____________________
Date: ________________________| System | Hold Implementation Method |
|---|---|
| Email (Exchange Online) | In-Place Hold or Litigation Hold via Exchange Admin Center / Compliance Center; applies to mailbox and archive |
| Email (Google Workspace) | Google Vault — create a Matter and apply Hold to specified users and date range |
| SharePoint / OneDrive | Preservation Hold via Microsoft Purview Compliance; applies at site, library, or folder level |
| Cloud Storage (AWS S3) | Apply S3 Object Lock Legal Hold (s3:PutObjectLegalHold) to relevant objects |
| Cloud Storage (Azure Blob) | Apply Legal Hold tags to containers via immutability policy |
| Cloud Storage (GCP) | Apply temporary hold to objects (gcloud storage objects update --temporary-hold) |
| Databases | Disable automated deletion jobs for in-scope records; flag records with hold reference |
| Backup systems | Tag relevant backup sets for indefinite retention; exclude from rotation/overwrite |
| Automated deletion system | Add hold reference to exclusion list in deletion orchestrator; all in-scope records bypass deletion queue |
| Collaboration (Teams/Slack) | Microsoft Purview retention policy; Slack Enterprise Grid Legal Hold (via Compliance API) |
| Activity | Frequency | Responsible |
|---|---|---|
| Custodian compliance reminder | Quarterly (or more frequently for active litigation) | Legal Department |
| New custodian identification | Ongoing — as new individuals are identified as relevant | Legal Counsel |
| System hold verification | Monthly — verify holds remain active on all in-scope systems | IT + Legal |
| New data source assessment | When new systems are deployed or data is migrated | IT + Legal |
| Hold scope review | Quarterly — assess whether scope should be expanded or narrowed | Legal Counsel |
| Interaction with Art. 17 requests | Per request — assess whether hold applies to data subject's data | DPO + Legal |
[Litigation/Investigation Concluded]
│
▼
[Legal Counsel Authorizes Release]
- Written authorization from lead counsel
- Confirmation that all proceedings (including appeals) are concluded
- Confirmation that no related proceedings are anticipated
│
▼
[Issue Hold Release Notice]
- Formal written notice to all custodians
- Notify IT to remove technical holds
- Notify DPO to resume normal retention schedule
│
▼
[Technical Hold Removal]
- Remove litigation hold from email systems
- Remove legal holds from cloud storage objects
- Re-enable automated deletion for affected data categories
- Remove hold exclusion from deletion orchestrator
- Unfreeze backup rotation for affected backup sets
│
▼
[Post-Release Retention Assessment]
- For each data category previously under hold:
├── Has normal retention period expired during hold? ──► Schedule immediate deletion
├── Is normal retention period still active? ──► Resume normal retention countdown
└── Were Art. 17 requests received during hold? ──► Process queued erasure requests
│
▼
[Update Litigation Hold Register]
- Record release date, authorizing counsel, matter outcome
- Archive hold documentation (retain for 6 years)Orion Data Vault Corp maintains a central register of all active and closed litigation holds:
LITIGATION HOLD REGISTER — Orion Data Vault Corp
(Extract — Active Holds as of 2026-03-14)
┌───────────────┬───────────────────────────┬────────────┬──────────────┬───────────┬──────────────────┐
│ Hold Ref │ Matter Description │ Date Issued│ Custodians │ Systems │ Next Review │
├───────────────┼───────────────────────────┼────────────┼──────────────┼───────────┼──────────────────┤
│ LH-2025-0018 │ Employment tribunal — │ 2025-06-15 │ 4 custodians │ Email, │ 2026-06-15 │
│ │ unfair dismissal claim │ │ │ HR system │ │
├───────────────┼───────────────────────────┼────────────┼──────────────┼───────────┼──────────────────┤
│ LH-2025-0021 │ ICO investigation — │ 2025-09-01 │ 7 custodians │ All │ 2026-03-01 │
│ │ data breach notification │ │ │ systems │ (overdue — │
│ │ │ │ │ │ under review) │
├───────────────┼───────────────────────────┼────────────┼──────────────┼───────────┼──────────────────┤
│ LH-2026-0023 │ Commercial dispute — │ 2026-03-14 │ 3 custodians │ Email, │ 2026-06-14 │
│ │ contract breach claim │ │ │ CRM, ERP, │ │
│ │ │ │ │ Finance │ │
└───────────────┴───────────────────────────┴────────────┴──────────────┴───────────┴──────────────────┘When an Art. 17 erasure request is received for data subject to a litigation hold:
Access requests are generally NOT affected by litigation holds. The data subject retains the right to access their data. However:
During an active hold:
© 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/litigation-hold-mgmt of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Litigation Hold Mgmt 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 |
|---|---|---|---|---|---|---|
| Litigation Hold Mgmt this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Legal Compliancetravisjneuman/.claude | 100 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Find Law Firmjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.6k | Automated safety check: Notes | MIT | |
| Legal CogaAAaqwq/AGI-Super-Team | 105 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| 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 |
travisjneuman/.claude
Legal and compliance expertise for corporate governance, contract analysis, regulatory compliance (SOX, GDPR, HIPAA), risk assessment, intellectual property, and litigation management.
jeremylongshore/tons-of-skills-marketplace
A skill your agent uses whenever the user wants to find, shortlist, vet, or enrich US B2B law firms — corporate, IP/patent, M&A and securities, employment, commercial litigation…
aAAaqwq/AGI-Super-Team
Legal demands two things: frontier-level reasoning and precision document generation.
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
aa0101181514/tw-legal-rag
Retrieve real Taiwan court judgments with verifiable citations before answering any question about Taiwan law or case law.
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
Manages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention…. Litigation Hold Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention schedules.
Litigation Hold Mgmt fits situations like: tasks that involve Legal research; tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill litigation-hold-mgmt -a claude-code`. Or copy the skill folder (skills/privacy/litigation-hold-mgmt in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/litigation-hold-mgmt in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill litigation-hold-mgmt -a codex`. Or copy the skill folder (skills/privacy/litigation-hold-mgmt in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/litigation-hold-mgmt 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 litigation-hold-mgmt -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/litigation-hold-mgmt, .gemini/skills/litigation-hold-mgmt, .github/skills/litigation-hold-mgmt and .opencode/skills/litigation-hold-mgmt in your project.
Going by SKILL.md and its folder, Litigation Hold Mgmt needs Python for the scripts in its folder and the command-line tools its instructions call (gcloud). 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.
Litigation Hold Mgmt 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 3.6k tokens (SKILL.md is roughly 14k 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 Litigation Hold Mgmt: Legal Compliance (travisjneuman/.claude, 100 stars), Find Law Firm (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Legal Cog (aAAaqwq/AGI-Super-Team, 105 stars) and C15t (c15t/c15t, 1.9k 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.