C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations.
Install Privacy Law Monitoring
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-law-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-law-monitoring --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/privacy-law-monitoring .claude/skills/privacy-law-monitoring && 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 "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .claude/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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/privacy-law-monitoringType 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 privacy-law-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-law-monitoring --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/privacy-law-monitoring .agents/skills/privacy-law-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .agents/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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 privacy-law-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-law-monitoring --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/privacy-law-monitoring .cursor/skills/privacy-law-monitoring && 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 "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .cursor/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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/privacy-law-monitoring--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 privacy-law-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-law-monitoring --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/privacy-law-monitoring .gemini/skills/privacy-law-monitoring && 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 "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .gemini/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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 privacy-law-monitoringInstalls 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 privacy-law-monitoring -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/privacy-law-monitoring .github/skills/privacy-law-monitoring && 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 "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .github/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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 privacy-law-monitoring -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 privacy-law-monitoring --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/privacy-law-monitoring .opencode/skills/privacy-law-monitoring && 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 "privacy-law-monitoring" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-law-monitoring into .opencode/skills/privacy-law-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-law-monitoring", 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
privacy-law-monitoring- GitHub stars
- 301
- Token cost
- ~2.3k tokens
- SKILL.md length
- 960 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations.
- Works in 4 steps: Regulatory intelligence arrives through… → Privacy operations team conducts initial… → Classification assigned based on the… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Monitoring Framework, Change Classification Framework and Impact Scoring Methodology, plus 2 more sections
- Runs Python scripts from its folder
What it does
Privacy Law Monitoring is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Covers regulatory tracking sources, change classification, impact scoring methodology, and implementation prioritisation. Keywords: law monitoring, regulatory tracking, change management, impact assessment, implementation priority.
Its SKILL.md is about 2.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 and Prioritization frameworks. 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
- Tasks that involve Prioritization frameworks
Example prompts
- “Use the privacy-law-monitoring skill to guide privacy law change monitoring and impact assessment for multi-jurisdiction organisations”
- “/privacy-law-monitoring”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Regulatory intelligence arrives through monitoring channels.
- Privacy operations team conducts initial triage (within 24 hours of receipt).
- Classification assigned based on the framework above.
- Notification distributed to relevant stakeholders per the escalation matrix.
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
Privacy Law Monitoring loads about 2.3k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 960 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). 960 words, ~2,285 tokens.
Download SKILL.mdSave it as
.claude/skills/privacy-law-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- privacy-law-monitoring
- description
- Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Covers regulatory tracking sources, change classification, impact scoring methodology, and implementation prioritisation. Keywords: law monitoring, regulatory tracking, change management, impact assessment, implementation priority.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- global-privacy-regulations
- metadata.tags
- law-monitoring, regulatory-tracking, change-management, impact-assessment, implementation-priority
Privacy Law Change Monitoring and Impact Assessment
Overview
Privacy law is one of the fastest-evolving regulatory domains globally. Between 2018 and 2026, over 40 countries enacted or substantially amended comprehensive data protection legislation. Organisations operating across multiple jurisdictions must systematically monitor these changes, assess their impact on operations, and prioritise implementation to maintain continuous compliance.
Monitoring Framework
Tier 1 Sources: Official Regulatory Publications
| Source Type | Examples | Monitoring Frequency |
|---|---|---|
| Official gazettes | EU Official Journal, Brazil Diário Oficial da União, India Gazette, PRC State Council announcements | Daily automated monitoring |
| Regulator websites | EDPB, CNIL, ICO, ANPD, CAC, PIPC, PPC, OAIC, PDPC (Singapore), PDPC (Thailand) | Daily automated monitoring |
| Regulatory enforcement decisions | DPA decision databases, court rulings | Weekly review |
| Public consultations | Draft regulations, calls for comment | Weekly review |
Tier 2 Sources: Interpretive and Analytical
| Source Type | Examples | Monitoring Frequency |
|---|---|---|
| Law firm alerts and briefings | Baker McKenzie Global Privacy Radar, DLA Piper Data Protection Laws of the World, Hogan Lovells Chronicle of Data Protection | Weekly digest |
| Industry associations | IAPP (International Association of Privacy Professionals), GPA (Global Privacy Assembly) | Weekly review |
| Academic publications | Computer Law & Security Review, International Data Privacy Law (IDPL) | Monthly review |
| Regulatory guidance and FAQs | EDPB guidelines, CNIL guides, PPC guidelines, ANPD resolutions | As published |
Tier 3 Sources: Horizon Scanning
| Source Type | Examples | Monitoring Frequency |
|---|---|---|
| Legislative tracking | National parliament agendas, EU legislative observatory, US Congressional trackers | Monthly review |
| Political and policy signals | Government policy papers, party manifestos, ministerial speeches | Quarterly review |
| International developments | UN resolutions, trade agreements with data provisions, OECD reports | Quarterly review |
| Technology developments | AI regulation proposals, biometric regulation, blockchain privacy | Quarterly review |
Change Classification Framework
Classification Categories
| Category | Code | Definition | Response Timeline |
|---|---|---|---|
| New law enacted | LAW-NEW | A comprehensive data protection law enacted in a jurisdiction where the organisation operates or plans to operate | 90 days to full assessment; implementation per gap analysis |
| Major amendment | LAW-AMD | Significant amendment to an existing law (new rights, new obligations, new penalties) | 60 days to impact assessment; implementation per amendment effective date |
| Regulatory guidance | REG-GUID | New guidance, guidelines, or interpretive documents from a supervisory authority | 30 days to review; adapt practices within 90 days if material |
| Enforcement decision | ENF-DEC | Notable enforcement action establishing new precedent or interpretation | 14 days to relevance assessment; adapt practices within 60 days if applicable |
| Draft legislation | DRAFT-LEG | Published bill, draft regulation, or public consultation | Track; no immediate action; prepare impact assessment during consultation period |
| Adequacy decision | ADQ-DEC | New adequacy decision or adequacy revocation by a data protection authority | 30 days to assess impact on cross-border transfer mechanisms |
| International development | INT-DEV | Treaty, mutual recognition arrangement, or international framework change | 30 days to assess relevance |
Classification Process
- Regulatory intelligence arrives through monitoring channels.
- Privacy operations team conducts initial triage (within 24 hours of receipt).
- Classification assigned based on the framework above.
- Notification distributed to relevant stakeholders per the escalation matrix.
Impact Scoring Methodology
Impact Dimensions
| Dimension | Weight | Scoring (1-5) |
|---|---|---|
| Geographic scope | 25% | 1 = single jurisdiction; 3 = regional; 5 = global applicability |
| Operational change | 30% | 1 = policy update only; 3 = process change; 5 = system/infrastructure change |
| Data subject volume | 15% | 1 = <10K; 2 = 10K-100K; 3 = 100K-500K; 4 = 500K-1M; 5 = >1M |
| Enforcement risk | 20% | 1 = guidance only; 3 = active enforcement expected; 5 = enforcement actions in progress |
| Timeline pressure | 10% | 1 = >12 months; 2 = 6-12 months; 3 = 3-6 months; 4 = 1-3 months; 5 = <1 month |
Impact Score Calculation
Weighted impact score = (Geographic × 0.25) + (Operational × 0.30) + (Volume × 0.15) + (Enforcement × 0.20) + (Timeline × 0.10)
Show full SKILL.md (393 more words)Show less
Impact Categories
| Score Range | Category | Response |
|---|---|---|
| 4.0 - 5.0 | Critical | Immediate project initiation; executive sponsor; dedicated resources |
| 3.0 - 3.9 | High | Prioritised project within 30 days; CPO oversight |
| 2.0 - 2.9 | Medium | Planned implementation within 90 days; privacy team lead |
| 1.0 - 1.9 | Low | Incorporated into next review cycle; routine update |
Implementation Prioritisation
Prioritisation Matrix
| Factor | Weight | Assessment Criteria |
|---|---|---|
| Legal deadline | 30% | How much time until the change takes effect? |
| Penalty exposure | 25% | What is the maximum potential penalty for non-compliance? |
| Enforcement activity | 20% | Is the regulator actively enforcing this requirement? |
| Business impact | 15% | How significantly does the change affect current operations? |
| Reputational risk | 10% | Would non-compliance result in public attention or customer concern? |
Implementation Workflow
- Score: Apply the prioritisation matrix to each change requiring implementation.
- Sequence: Order implementation by composite priority score (highest first).
- Resource: Allocate resources based on operational change dimension (policy, process, or system).
- Execute: Implement per the standard change management process.
- Verify: Confirm implementation effectiveness through testing or audit.
- Close: Update the regulatory change register and compliance matrix.
Zenith Global Enterprises Monitoring Programme
Current Monitoring Scope
| Region | Jurisdictions Monitored | Primary Laws |
|---|---|---|
| Europe | EU 27 + UK + Switzerland + Norway | GDPR, UK GDPR, nDSG, Personvernloven |
| Americas | Brazil, USA (12 states), Canada | LGPD, State laws, PIPEDA |
| Asia-Pacific | China, Japan, Korea, India, Singapore, Thailand, Australia | PIPL, APPI, PIPA, DPDP, PDPA (SG), PDPA (TH), Privacy Act |
| Middle East | UAE, Saudi Arabia | PDPL (SA), DPL (UAE) |
Recent Change Log
| Date | Jurisdiction | Change | Classification | Impact Score | Status |
|---|---|---|---|---|---|
| Jan 2026 | India | DPDP Rules published for consultation | DRAFT-LEG | 3.8 (High) | Tracking; preparing response |
| Feb 2026 | Australia | Privacy Act reform amendments enacted | LAW-AMD | 4.2 (Critical) | Implementation project initiated |
| Feb 2026 | EU | EDPB guidelines on AI and GDPR | REG-GUID | 3.1 (High) | Under review by DPO team |
| Mar 2026 | China | CAC updated cross-border transfer guidance | REG-GUID | 3.5 (High) | Assessment in progress |
| Mar 2026 | Brazil | ANPD Resolution 20 on international transfers | REG-GUID | 3.0 (High) | Under review |
Escalation Matrix
| Impact Category | Notification Recipients | Response Time |
|---|---|---|
| Critical (4.0-5.0) | CPO, General Counsel, CEO, Board Privacy Committee | 24 hours |
| High (3.0-3.9) | CPO, Regional DPOs, Legal | 72 hours |
| Medium (2.0-2.9) | Regional DPOs, Privacy Operations | 1 week |
| Low (1.0-1.9) | Privacy Operations | Next scheduled review |
Annual Monitoring Metrics
| Metric | 2025 Actual | 2026 Target |
|---|---|---|
| Regulatory changes tracked | 287 | 300+ |
| Impact assessments completed | 42 | 50+ |
| Average assessment turnaround (days) | 12 | <10 |
| Implementation completion rate | 94% | >95% |
| Overdue implementations | 3 | 0 |
© 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/privacy-law-monitoring 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
Privacy Law Monitoring 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 |
|---|---|---|---|---|---|---|
| Privacy Law Monitoring this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.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 Privacy Law Monitoring
What does Privacy Law Monitoring do?
Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Privacy Law Monitoring is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations.
When should I use Privacy Law Monitoring?
Privacy Law Monitoring fits situations like: tasks that involve Privacy and GDPR; tasks that involve Prioritization frameworks.
How do I install Privacy Law Monitoring in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-law-monitoring -a claude-code`. Or copy the skill folder (skills/privacy/privacy-law-monitoring in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/privacy-law-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Privacy Law Monitoring in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-law-monitoring -a codex`. Or copy the skill folder (skills/privacy/privacy-law-monitoring in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/privacy-law-monitoring in your project. Codex loads it when a task matches its description.
Can I use Privacy Law Monitoring 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 privacy-law-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/privacy-law-monitoring, .gemini/skills/privacy-law-monitoring, .github/skills/privacy-law-monitoring and .opencode/skills/privacy-law-monitoring in your project.
What does Privacy Law Monitoring need to run?
Going by SKILL.md and its folder, Privacy Law Monitoring needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Privacy Law Monitoring 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 Privacy Law Monitoring 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 Privacy Law Monitoring use?
Privacy Law Monitoring 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 Privacy Law Monitoring use?
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Privacy Law Monitoring?
Skills that share tags, products or a category with Privacy Law Monitoring: 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 Privacy Law Monitoring?
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.