Uae Grc
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
United Arab Emirates Governance, Risk & Compliance advisor — a jurisdiction-first compliance router.
Guides managing conflicting privacy requirements across jurisdictions.
Install Conflicting Laws Mgmt
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill conflicting-laws-mgmt -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills conflicting-laws-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/conflicting-laws-mgmt .claude/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .claude/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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/conflicting-laws-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 conflicting-laws-mgmt -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills conflicting-laws-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/conflicting-laws-mgmt .agents/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .agents/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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 conflicting-laws-mgmt -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills conflicting-laws-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/conflicting-laws-mgmt .cursor/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .cursor/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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/conflicting-laws-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 conflicting-laws-mgmt -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills conflicting-laws-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/conflicting-laws-mgmt .gemini/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .gemini/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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 conflicting-laws-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 conflicting-laws-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/conflicting-laws-mgmt .github/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .github/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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 conflicting-laws-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 conflicting-laws-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/conflicting-laws-mgmt .opencode/skills/conflicting-laws-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 "conflicting-laws-mgmt" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/conflicting-laws-mgmt into .opencode/skills/conflicting-laws-mgmt/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conflicting-laws-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
conflicting-laws-mgmt- GitHub stars
- 301
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,017 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides managing conflicting privacy requirements across jurisdictions.
- Works in 3 steps: Global fast track: Begin assessment… → Assessment track: Continue assessment… → Content: Preliminary 72-hour…
- Tasks that involve Internationalization
- SKILL.md covers Overview, Categories of Conflict, Resolution Framework and Governance
- Runs Python scripts from its folder
What it does
Conflicting Laws Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides managing conflicting privacy requirements across jurisdictions. Covers data localisation vs transfer freedom, consent standards variation, age thresholds, breach timelines, and resolution frameworks for incompatible obligations. Keywords: conflicting laws, data localisation, consent variation, age thresholds, resolution framework.
Its SKILL.md is about 2.5k 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 Internationalization 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.
When your agent uses it
- Tasks that involve Internationalization
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the conflicting-laws-mgmt skill to guide managing conflicting privacy requirements across jurisdictions”
- “/conflicting-laws-mgmt”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Global fast track: Begin assessment immediately upon awareness; prepare notification within 72 hours for jurisdictions requiring it
- Assessment track: Continue assessment for up to 30 days for jurisdictions permitting it, but issue preliminary notification at 72 hours to…
- Content: Preliminary 72-hour notification may be updated as assessment continues
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
Conflicting Laws Mgmt loads about 2.5k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 1,017 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). 1,017 words, ~2,493 tokens.
Download SKILL.mdSave it as
.claude/skills/conflicting-laws-mgmt/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- conflicting-laws-mgmt
- description
- Guides managing conflicting privacy requirements across jurisdictions. Covers data localisation vs transfer freedom, consent standards variation, age thresholds, breach timelines, and resolution frameworks for incompatible obligations. Keywords: conflicting laws, data localisation, consent variation, age thresholds, resolution framework.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- global-privacy-regulations
- metadata.tags
- conflicting-laws, data-localisation, consent-variation, resolution-framework, cross-jurisdiction
Managing Conflicting Privacy Requirements
Overview
Organisations operating across multiple jurisdictions inevitably encounter situations where privacy requirements in different countries conflict, are incompatible, or create compliance tensions. These conflicts arise because privacy laws reflect different legal traditions, cultural values, and policy priorities. A structured resolution framework enables organisations to navigate these conflicts while maintaining defensible compliance positions in all jurisdictions.
Categories of Conflict
Category 1: Data Localisation vs Transfer Freedom
| Conflict | Detail |
|---|---|
| Localisation requirement | China PIPL Art. 40 requires CIIOs to store personal information within the PRC; India RBI circular requires payment data stored in India |
| Transfer freedom | EU GDPR Art. 44-49 permits transfers with appropriate safeguards; Singapore PDPA Section 26 permits transfers with comparable protection |
| Resolution challenge | An organisation may need to store data locally while also making it available to a global headquarters |
Resolution Framework for Zenith Global Enterprises:
| Scenario | Approach |
|---|---|
| China CIIO data + EU HQ access | Store primary data in PRC; transfer processed copies via CAC-approved mechanism; maintain PRC as system of record |
| India payment data + Global Treasury | Store payment system data in India (RBI compliance); process copies transferred to Treasury with contractual safeguards |
| Cross-jurisdiction analytics | Implement federated analytics: run queries locally, aggregate results centrally; avoid moving raw personal data |
Category 2: Consent Standards Variation
| Jurisdiction | Consent Standard |
|---|---|
| EU (GDPR) | Freely given, specific, informed, unambiguous; not required if other lawful basis applies |
| China (PIPL) | Default basis; separate consent (单独同意) for five scenarios |
| Korea (PIPA) | Prescriptive display requirements (font size, colour); separate consent for marketing |
| Brazil (LGPD) | Standalone consent clause separate from contract terms; 10 alternative bases |
| India (DPDP) | Free, specific, informed, unconditional, unambiguous; Consent Manager integration |
| Japan (APPI) | Implied consent model for general processing; explicit for special care-required info |
Conflict examples:
- GDPR allows legitimate interest without consent; PIPL requires consent as default with no legitimate interest basis
- LGPD separates consent from contract clauses; some jurisdictions permit integrated consent
- Korea prescribes font size and display; other jurisdictions are principle-based
Resolution: Apply the most restrictive consent standard globally (separate, explicit, purpose-specific consent with clear display) as the harmonised baseline. Where a jurisdiction permits processing without consent (e.g., GDPR legitimate interest), document the jurisdiction-specific basis but maintain the consent infrastructure as a fallback.
Category 3: Age Thresholds for Children
| Jurisdiction | Age | Implication |
|---|---|---|
| India (DPDP) | Under 18 | All under-18 processing requires parental consent |
| Australia (2024) | Under 18 | Children's code applies |
| EU (GDPR) | Under 16 (lowerable to 13) | Parental consent for ISS |
| China (PIPL) | Under 14 | Parental consent + additional protections |
| Korea (PIPA) | Under 14 | Legal representative consent |
| Thailand (PDPA) | Under 10 | Parental consent |
Conflict: Different age thresholds create operational complexity for global platforms.
Resolution: Apply the highest global threshold (18, from India DPDP) as the harmonised standard for all markets. This ensures compliance everywhere at the cost of stricter treatment in jurisdictions with lower thresholds. Where the highest threshold creates significant business impact, implement jurisdiction-specific age logic in the consent management platform.
Category 4: Breach Notification Timelines
| Jurisdiction | Timeline | Trigger |
|---|---|---|
| EU GDPR | 72 hours | Risk to rights and freedoms |
| Korea PIPA | 72 hours | 1,000+ individuals affected |
| India DPDP | 72 hours (draft) | Likely harm |
| Brazil LGPD | 3 business days | Relevant risk or damage |
| Singapore PDPA | 3 days after assessment (30-day assessment window) | Significant harm or 500+ individuals |
| Australia Privacy Act | As soon as practicable (30-day assessment) | Likely serious harm |
| Japan APPI | 3-5 business days (preliminary) | PPC-defined thresholds |
Conflict: The 72-hour clock (EU/Korea/India) conflicts with the 30-day assessment window (Singapore/Australia).
Resolution: Implement a two-track notification process:
- Global fast track: Begin assessment immediately upon awareness; prepare notification within 72 hours for jurisdictions requiring it
- Assessment track: Continue assessment for up to 30 days for jurisdictions permitting it, but issue preliminary notification at 72 hours to the fast-track jurisdictions
- Content: Preliminary 72-hour notification may be updated as assessment continues
Show full SKILL.md (392 more words)Show less
Category 5: Legitimate Interest Availability
| Jurisdiction | Legitimate Interest Available |
|---|---|
| EU (GDPR) | Yes — Art. 6(1)(f) |
| UK GDPR | Yes — Art. 6(1)(f) |
| Korea (PIPA) | Yes — Art. 15(1)(6) (2023 amendment) |
| Brazil (LGPD) | Yes — Art. 7, IX |
| Thailand (PDPA) | Yes — Section 24(5) |
| China (PIPL) | No |
| India (DPDP) | No (legitimate uses under Section 7 are narrower) |
| Japan (APPI) | No (use limitation approach) |
| Singapore (PDPA) | No (consent + deemed consent model) |
Conflict: An organisation relying on legitimate interest in the EU cannot use the same basis in China, India, or Singapore.
Resolution: For processing activities that rely on legitimate interest in some jurisdictions, maintain consent collection infrastructure as a parallel mechanism. In jurisdictions without legitimate interest, obtain consent or identify an applicable alternative basis. Document both bases in the processing register with jurisdiction-specific applicability.
Category 6: DPO Independence vs Organisational Structure
| Conflict | Detail |
|---|---|
| GDPR Art. 38(3) | DPO cannot be dismissed or penalised for performing duties; must report to highest management |
| National employment laws | Some jurisdictions limit the enforceability of dismissal protections for senior employees |
| Multi-jurisdiction DPO | A single global DPO may face conflicting reporting requirements across jurisdictions |
Resolution: Appoint regional DPOs with local employment protections consistent with national law, reporting to a global Chief Privacy Officer. Each regional DPO holds the statutory DPO role for their jurisdiction while the global CPO provides strategic coordination.
Resolution Framework
Decision Tree for Conflicting Requirements
START: Identify the conflict
|
├── Can a single harmonised standard satisfy all jurisdictions?
| |
| ├── YES → Apply the most stringent standard globally
| |
| └── NO → Are the requirements truly incompatible?
| |
| ├── YES → Implement jurisdiction-specific controls
| | |
| | └── Document: (a) the conflict, (b) the resolution,
| | (c) the risk accepted in each jurisdiction
| |
| └── NO (tension but not incompatible) → Apply layered approach:
| global baseline + jurisdiction-specific supplements
|
└── Record the resolution in the conflict registerConflict Register Template
| Conflict ID | Category | Jurisdictions | Description | Resolution | Risk Assessment | Review Date |
|---|---|---|---|---|---|---|
| CON-001 | Data localisation | China, India, EU | CIIO data must stay in PRC but EU HQ needs access | Local storage + processed copies transferred via CAC mechanism | Medium — residual risk of CAC rejection on renewal | March 2027 |
| CON-002 | Consent standards | China, EU, Korea | PIPL requires consent; GDPR permits legitimate interest | Dual-basis approach: consent in China/Korea, legitimate interest in EU | Low — consent infrastructure maintained globally | March 2027 |
| CON-003 | Children's age | India (18), EU (16), Korea (14) | Different parental consent thresholds | Global 18 threshold | Low — over-compliant in lower-threshold jurisdictions | March 2027 |
| CON-004 | Breach timeline | EU (72h), Singapore (30d assessment) | Different notification clocks | Two-track: 72h preliminary + 30d full assessment | Low — preliminary notification satisfies fast-track jurisdictions | March 2027 |
Governance
| Element | Detail |
|---|---|
| Conflict register owner | Chief Privacy Officer |
| Review frequency | Semi-annually or upon law change |
| Escalation path | CPO → General Counsel → Board Privacy Committee |
| External counsel | Engaged for novel conflicts requiring jurisdiction-specific legal opinion |
| Documentation | All resolutions documented with legal analysis and risk assessment |
© 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/conflicting-laws-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
Conflicting Laws 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 |
|---|---|---|---|---|---|---|
| Conflicting Laws Mgmt this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Uae GrcSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Privacy Policy Generator Localizationnisrulz/app-privacy-policy-generator | 4.7k | — | ~526 | Automated safety check: Pass | AGPL-3.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 |
Similar skills
Privacy Policy Generator Localization
nisrulz/app-privacy-policy-generator
Adds or updates a language translation in the app privacy policy generator by copying the English locale file, translating its values and building the site.
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
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…
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 Conflicting Laws Mgmt
What does Conflicting Laws Mgmt do?
Guides managing conflicting privacy requirements across jurisdictions. Conflicting Laws Mgmt is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides managing conflicting privacy requirements across jurisdictions.
When should I use Conflicting Laws Mgmt?
Conflicting Laws Mgmt fits situations like: tasks that involve Internationalization; tasks that involve Privacy and GDPR.
How do I install Conflicting Laws Mgmt in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill conflicting-laws-mgmt -a claude-code`. Or copy the skill folder (skills/privacy/conflicting-laws-mgmt in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/conflicting-laws-mgmt in your project. Claude Code loads it when a task matches its description.
How do I install Conflicting Laws Mgmt in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill conflicting-laws-mgmt -a codex`. Or copy the skill folder (skills/privacy/conflicting-laws-mgmt in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/conflicting-laws-mgmt in your project. Codex loads it when a task matches its description.
Can I use Conflicting Laws 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 conflicting-laws-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/conflicting-laws-mgmt, .gemini/skills/conflicting-laws-mgmt, .github/skills/conflicting-laws-mgmt and .opencode/skills/conflicting-laws-mgmt in your project.
What does Conflicting Laws Mgmt need to run?
Going by SKILL.md and its folder, Conflicting Laws Mgmt needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Conflicting Laws 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 Conflicting Laws 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 Conflicting Laws Mgmt use?
Conflicting Laws 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 Conflicting Laws Mgmt use?
About 2.5k tokens (SKILL.md is roughly 10k 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.3k tokens, read only when the agent opens those files.
What are the alternatives to Conflicting Laws Mgmt?
Skills that share tags, products or a category with Conflicting Laws Mgmt: Uae Grc (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Privacy Policy Generator Localization (nisrulz/app-privacy-policy-generator, 4.7k stars), C15t (c15t/c15t, 1.9k stars) and HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conflicting Laws 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.