C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance.
Install Retention Exception Mgmt
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill retention-exception-mgmt -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills retention-exception-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/retention-exception-mgmt .claude/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .claude/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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/retention-exception-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 retention-exception-mgmt -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills retention-exception-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/retention-exception-mgmt .agents/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .agents/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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 retention-exception-mgmt -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills retention-exception-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/retention-exception-mgmt .cursor/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .cursor/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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/retention-exception-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 retention-exception-mgmt -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills retention-exception-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/retention-exception-mgmt .gemini/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .gemini/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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 retention-exception-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 retention-exception-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/retention-exception-mgmt .github/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .github/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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 retention-exception-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 retention-exception-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/retention-exception-mgmt .opencode/skills/retention-exception-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 "retention-exception-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/retention-exception-mgmt into .opencode/skills/retention-exception-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retention-exception-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.
Facts
- Skill name
retention-exception-mgmt- GitHub stars
- 301
- Token cost
- ~3.3k tokens
- SKILL.md length
- 873 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance.
- Works in 4 steps: Request Submission → DPO Assessment → Approval Authority → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Context, Exception Categories and Exception Request Workflow, plus 2 more sections
- Runs Python scripts from its folder
What it does
Retention Exception Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance. Covers legitimate grounds for extending retention beyond scheduled periods and governance controls to prevent indefinite data hoarding. Activate for retention exception, retention extension, data hoarding prevention, retention override queries.
Its SKILL.md is about 3.3k 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 retention-exception-mgmt skill to manage retention exception workflows including request-approval processes, duration limits, periodic…”
- “/retention-exception-mgmt”
Requirements
- Python 3
Workflow steps
4 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
Retention Exception Mgmt loads about 3.3k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 873 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). 873 words, ~3,294 tokens.
Download SKILL.mdSave it as
.claude/skills/retention-exception-mgmt/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- retention-exception-mgmt
- description
- Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance. Covers legitimate grounds for extending retention beyond scheduled periods and governance controls to prevent indefinite data hoarding. Activate for retention exception, retention extension, data hoarding prevention, retention override queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-retention-deletion
- metadata.tags
- retention-exception, retention-extension, data-governance, retention-override, exception-management
Retention Exception Management
Overview
Retention exceptions are formal, time-limited deviations from the approved data retention schedule. While the retention schedule defines default retention periods based on legal basis and processing purpose, legitimate business or legal circumstances may require retaining specific data beyond the scheduled period. Without a rigorous exception management process, exceptions become a mechanism for indefinite data hoarding that undermines the storage limitation principle under GDPR Article 5(1)(e). This skill defines the governance framework for requesting, approving, monitoring, and expiring retention exceptions.
Legal Context
GDPR Article 5(1)(e) — Storage Limitation
The storage limitation principle requires that personal data not be kept longer than necessary. Any extension beyond the retention schedule must be justified and documented. Exceptions must be genuinely necessary, proportionate, and time-limited.
GDPR Article 5(2) — Accountability
The controller shall be responsible for, and be able to demonstrate compliance with, the data protection principles. Retention exceptions must be documented with sufficient detail to demonstrate that each exception is justified and proportionate.
GDPR Recital 39 — Time Limits
Time limits should be established by the controller for erasure or for periodic review. Exceptions to these time limits must themselves be subject to periodic review.
Exception Categories
Legitimate Grounds for Retention Exceptions
| Category | Description | Maximum Duration | Approval Level |
|---|---|---|---|
| Legal hold | Litigation, regulatory investigation, or audit requiring data preservation | Duration of legal proceedings + 6 months | Legal Counsel (mandatory) |
| Regulatory requirement | New or updated regulatory requirement mandating extended retention not yet reflected in the schedule | Until schedule is updated (max 6 months) | DPO + Legal |
| Contractual obligation | Contract requires retention beyond default period | Duration of contractual obligation + limitation period | Business Owner + DPO |
| Ongoing dispute | Unresolved customer complaint or dispute not yet escalated to formal proceedings | 12 months (renewable) | DPO |
| Business continuity | Data needed for system migration, audit, or disaster recovery beyond normal period | 6 months (non-renewable without re-application) | IT Director + DPO |
| Research/statistical | Data needed for research or statistical purposes under Art. 89(1) | Duration of research project + 6 months | DPO + Research Lead |
| Public interest archiving | Data has archiving value in the public interest | Indefinite (with annual review) | DPO + Board approval |
Prohibited Exception Grounds
The following are NOT legitimate grounds for retention exceptions:
- "We might need it someday" — Speculative future use is not a valid basis under GDPR.
- "It's easier to keep it" — Administrative convenience does not override storage limitation.
- "We haven't finished the data migration" — Technical migration should be prioritized; a maximum 6-month exception applies.
- "The data owner hasn't responded" — Non-response is not approval; escalate and proceed with scheduled deletion.
- "We want to train ML models" — This constitutes a new processing purpose requiring its own legal basis assessment, not a retention exception.
Exception Request Workflow
Step 1: Request Submission
RETENTION EXCEPTION REQUEST — Orion Data Vault Corp
-----------------------------------------------------
Request Reference: RET-EXC-2026-0014
Date Submitted: 2026-03-14
Requestor: [Name, Title, Department]
SECTION 1: DATA IDENTIFICATION
- Data Category (from retention schedule): [CAT-XXX]
- Specific data set / records: [Description]
- Number of data subjects affected: [Count or estimate]
- Current retention period: [Per schedule]
- Scheduled deletion date: [YYYY-MM-DD]
SECTION 2: EXCEPTION REQUEST
- Requested extension period: [Specific duration — NOT "indefinite"]
- Proposed new deletion date: [YYYY-MM-DD]
- Exception category (from table above): [Select one]
SECTION 3: JUSTIFICATION
- Detailed explanation of why the extension is necessary:
[Minimum 200 words — must address specific legal, regulatory,
contractual, or operational necessity]
- What would the consequence be if the data were deleted on schedule?
[Specific, concrete consequences — not speculative]
- What alternatives to retention were considered?
[e.g., anonymization, aggregation, partial deletion]
- Why were alternatives rejected?
[Specific reasons]
SECTION 4: PROPORTIONALITY ASSESSMENT
- Is the full data set needed, or can it be minimized?
[Detail which fields/records are genuinely needed]
- Can the data be pseudonymized during the exception period?
[Yes/No — if No, explain why]
- What access restrictions will be applied during the exception?
[Detail access controls]
- What is the sensitivity level of the data?
[Standard personal data / Special category / Financial / etc.]
SECTION 5: SUPPORTING DOCUMENTATION
- [Attach legal opinion, regulatory notice, contract clause, etc.]
Requestor Signature: _________________________
Date: _________________________Step 2: DPO Assessment
The DPO conducts an independent assessment of the exception request:
DPO ASSESSMENT — RETENTION EXCEPTION
-------------------------------------
Request Reference: RET-EXC-2026-0014
DPO: [Name]
Assessment Date: [YYYY-MM-DD]
NECESSITY TEST:
□ Is the exception genuinely necessary for the stated purpose?
□ Has the requestor demonstrated specific (not speculative) consequences of deletion?
□ Is the exception category legitimate per the approved framework?
PROPORTIONALITY TEST:
□ Is the requested duration proportionate to the stated need?
□ Has data minimization been applied (only necessary data retained)?
□ Are adequate access restrictions in place during the exception?
□ Has pseudonymization been applied where feasible?
LEGAL BASIS CHECK:
□ Does a valid legal basis exist for continued processing during the exception?
□ If the original legal basis was consent, has the data subject been informed?
□ Are any data subject rights affected (pending Art. 17 requests)?
RISK ASSESSMENT:
- Risk to data subjects from extended retention: [Low/Medium/High]
- Risk to organization from not retaining: [Low/Medium/High]
- Balance: [Retain / Delete / Partial retention]
RECOMMENDATION:
□ APPROVE — as requested
□ APPROVE WITH CONDITIONS — [specify conditions]
□ APPROVE REDUCED DURATION — [specify reduced period]
□ REJECT — [specify reasons]
DPO Signature: _________________________
Date: _________________________Step 3: Approval Authority
| Exception Category | Required Approvals | Escalation |
|---|---|---|
| Legal hold | Legal Counsel (mandatory) | N/A — legal holds are mandatory |
| Regulatory requirement | DPO + Legal Counsel | Board if regulation impacts >10,000 data subjects |
| Contractual obligation | Business Owner + DPO | Legal Counsel if contract value >£500K |
| Ongoing dispute | DPO | Legal Counsel if dispute may escalate to litigation |
| Business continuity | IT Director + DPO | CTO if >6 months or >50,000 records |
| Research/statistical | DPO + Research Lead | Ethics Committee if special category data |
| Public interest archiving | DPO + Board approval | External legal opinion required |
Show full SKILL.md (327 more words)Show less
Step 4: Exception Registration
Approved exceptions are recorded in the Retention Exception Register:
RETENTION EXCEPTION REGISTER — Orion Data Vault Corp
(Extract — Active Exceptions as of 2026-03-14)
┌──────────────────┬────────────────┬──────────┬──────────────┬──────────────┬────────────┬─────────────┐
│ Exception Ref │ Data Category │ Records │ Original │ Extended │ Category │ Next Review │
│ │ │ Affected │ Deletion │ Deletion │ │ │
├──────────────────┼────────────────┼──────────┼──────────────┼──────────────┼────────────┼─────────────┤
│ RET-EXC-2025-008│ CAT-003 Trans. │ 12,400 │ 2025-12-31 │ 2026-06-30 │ Regulatory │ 2026-03-31 │
│ │ Records │ │ │ │ (FCA audit)│ │
├──────────────────┼────────────────┼──────────┼──────────────┼──────────────┼────────────┼─────────────┤
│ RET-EXC-2026-003│ CAT-006 Appli- │ 340 │ 2026-01-15 │ 2026-07-15 │ Ongoing │ 2026-04-15 │
│ │ cant Data │ │ │ │ dispute │ │
├──────────────────┼────────────────┼──────────┼──────────────┼──────────────┼────────────┼─────────────┤
│ RET-EXC-2026-011│ CAT-002 Cust. │ 85,200 │ 2026-03-01 │ 2026-09-01 │ Business │ 2026-06-01 │
│ │ Account Data │ │ │ │ continuity │ │
│ │ │ │ │ │ (migration)│ │
└──────────────────┴────────────────┴──────────┴──────────────┴──────────────┴────────────┴─────────────┘Periodic Review Process
Review Triggers
| Trigger | Action |
|---|---|
| Scheduled review date reached | Reassess necessity and proportionality; renew, reduce, or expire |
| Exception duration 75% elapsed | Alert to requestor and DPO — prepare renewal or deletion |
| Exception duration 100% elapsed | Automatic deletion unless renewal approved before expiry |
| Underlying circumstance resolved | Immediate reassessment — e.g., litigation concluded, migration completed |
| Data subject complaint | DPO review of specific exception affecting complainant |
| Annual retention schedule review | All active exceptions reviewed as part of annual schedule review |
Review Procedure
[Exception Review Date Reached]
│
▼
[DPO Retrieves Exception Record]
│
▼
[Reassess Necessity]
│
├── Underlying circumstance still active?
│ ├── Yes ──► [Reassess proportionality and duration]
│ └── No ──► [Expire exception — schedule deletion within 30 days]
│
├── Can scope be reduced?
│ ├── Yes ──► [Minimize — delete non-essential records, pseudonymize remainder]
│ └── No ──► [Document why full scope still needed]
│
└── Has maximum allowable duration been reached?
├── Yes ──► [Expire exception — escalate if requestor objects]
└── No ──► [Renew with updated justification]
│
▼
[Update Exception Register]
[Notify requestor of outcome]
[Schedule next review date]Governance Controls
Anti-Hoarding Safeguards
- Maximum duration limits: Each exception category has a defined maximum duration (see table above). No exception may exceed its category maximum without Board approval.
- Mandatory review cycle: All exceptions are reviewed at minimum every 6 months, regardless of stated duration.
- Auto-expiry: Exceptions that are not renewed by their review date automatically trigger deletion of the associated data within 30 days.
- Exception volume monitoring: The DPO reports quarterly on the total number and volume of active exceptions. An upward trend triggers a governance review.
- Exception-to-schedule ratio: If more than 15% of data by volume is held under exceptions, a full retention schedule review is triggered (the schedule may need updating rather than operating through exceptions).
- No retrospective exceptions: Exceptions cannot be applied retrospectively to data that has already been deleted. Exceptions must be approved before the scheduled deletion date.
- Audit trail: All exception requests, assessments, approvals, reviews, and expirations are logged in an immutable audit trail.
Quarterly Exception Report
The DPO prepares a quarterly report for the Board containing:
- Total active exceptions (count and data volume)
- New exceptions approved in the quarter
- Exceptions expired or cancelled in the quarter
- Exceptions approaching maximum duration
- Exception category breakdown
- Data subject impact (number of data subjects affected by active exceptions)
- Trend analysis (quarter-over-quarter comparison)
- Recommendations (schedule updates needed, governance improvements)
© 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/retention-exception-mgmt 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
Retention Exception 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 |
|---|---|---|---|---|---|---|
| Retention Exception Mgmt this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~3.3k | 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 Retention Exception Mgmt
What does Retention Exception Mgmt do?
Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance. Retention Exception Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages retention exception workflows including request-approval processes, duration limits, periodic review cycles, documentation requirements, and audit trail maintenance.
When should I use Retention Exception Mgmt?
Retention Exception Mgmt fits situations like: tasks that involve Privacy and GDPR.
How do I install Retention Exception Mgmt in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill retention-exception-mgmt -a claude-code`. Or copy the skill folder (skills/privacy/retention-exception-mgmt in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/retention-exception-mgmt in your project. Claude Code loads it when a task matches its description.
How do I install Retention Exception Mgmt in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill retention-exception-mgmt -a codex`. Or copy the skill folder (skills/privacy/retention-exception-mgmt in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/retention-exception-mgmt in your project. Codex loads it when a task matches its description.
Can I use Retention Exception Mgmt 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 retention-exception-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/retention-exception-mgmt, .gemini/skills/retention-exception-mgmt, .github/skills/retention-exception-mgmt and .opencode/skills/retention-exception-mgmt in your project.
What does Retention Exception Mgmt need to run?
Going by SKILL.md and its folder, Retention Exception Mgmt needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Retention Exception Mgmt 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 Retention Exception Mgmt 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 Retention Exception Mgmt use?
Retention Exception 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.
How many tokens does Retention Exception Mgmt use?
About 3.3k tokens (SKILL.md is roughly 13k 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.2k tokens, read only when the agent opens those files.
What are the alternatives to Retention Exception Mgmt?
Skills that share tags, products or a category with Retention Exception Mgmt: 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 Retention Exception Mgmt?
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.