C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Harmonises data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI (1798.140(ae)) vs HIPAA PHI (160.103) vs LGPD sensitive data (Art.
Install Cross Jurisdiction Class
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cross-jurisdiction-class -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cross-jurisdiction-class --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/cross-jurisdiction-class .claude/skills/cross-jurisdiction-class && 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 "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .claude/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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/cross-jurisdiction-classType 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 cross-jurisdiction-class -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cross-jurisdiction-class --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/cross-jurisdiction-class .agents/skills/cross-jurisdiction-class && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .agents/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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 cross-jurisdiction-class -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cross-jurisdiction-class --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/cross-jurisdiction-class .cursor/skills/cross-jurisdiction-class && 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 "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .cursor/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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/cross-jurisdiction-class--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 cross-jurisdiction-class -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cross-jurisdiction-class --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/cross-jurisdiction-class .gemini/skills/cross-jurisdiction-class && 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 "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .gemini/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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 cross-jurisdiction-classInstalls 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 cross-jurisdiction-class -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/cross-jurisdiction-class .github/skills/cross-jurisdiction-class && 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 "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .github/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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 cross-jurisdiction-class -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 cross-jurisdiction-class --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/cross-jurisdiction-class .opencode/skills/cross-jurisdiction-class && 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 "cross-jurisdiction-class" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cross-jurisdiction-class into .opencode/skills/cross-jurisdiction-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-jurisdiction-class", 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
cross-jurisdiction-class- GitHub stars
- 301
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,005 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Harmonises data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI (1798.140(ae)) vs HIPAA PHI (160.103) vs LGPD sensitive data (Art.
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Jurisdictional Definitions…, Cross-Regulation Mapping Matrix and Harmonised Classification…, plus 3 more sections
- Runs Python scripts from its folder
What it does
Cross Jurisdiction Class is an agent skill from mukul975/Privacy-Data-Protection-Skills. Harmonises data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI (1798.140(ae)) vs HIPAA PHI (160.103) vs LGPD sensitive data (Art. 5-II). Provides cross-regulation mapping matrix for multinational compliance. Keywords: cross-jurisdiction, GDPR, CCPA, HIPAA, LGPD, sensitive data, multinational, classification mapping.
Its SKILL.md is about 2.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 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 cross-jurisdiction-class skill to harmonise data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI…”
- “/cross-jurisdiction-class”
Requirements
- Python 3
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
Cross Jurisdiction Class loads about 2.6k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 1,005 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,005 words, ~2,564 tokens.
Download SKILL.mdSave it as
.claude/skills/cross-jurisdiction-class/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cross-jurisdiction-class
- description
- Harmonises data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI (1798.140(ae)) vs HIPAA PHI (160.103) vs LGPD sensitive data (Art. 5-II). Provides cross-regulation mapping matrix for multinational compliance. Keywords: cross-jurisdiction, GDPR, CCPA, HIPAA, LGPD, sensitive data, multinational, classification mapping.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-classification
- metadata.tags
- cross-jurisdiction, gdpr, ccpa, hipaa, lgpd, multinational, classification-mapping
Cross-Jurisdiction Data Classification Harmonisation
Overview
Multinational organisations must classify data under multiple regulatory frameworks simultaneously. GDPR special categories (Art. 9), CCPA sensitive personal information (Cal. Civ. Code §1798.140(ae)), HIPAA protected health information (45 CFR §160.103), and LGPD sensitive personal data (Art. 5-II) each define sensitive data differently with distinct requirements. This skill provides a cross-regulation mapping matrix enabling unified classification that satisfies all applicable jurisdictions, supporting Vanguard Financial Services' operations across the UK/EU, United States, and Brazil.
Jurisdictional Definitions Compared
GDPR Art. 9 — Special Categories (EU/UK)
| Category | Definition Summary |
|---|---|
| Racial or ethnic origin | Data revealing racial or ethnic background |
| Political opinions | Political views, party membership, voting |
| Religious or philosophical beliefs | Faith, atheism, philosophical convictions |
| Trade union membership | Union membership status or activities |
| Genetic data | Inherited/acquired genetic characteristics (Art. 4(13)) |
| Biometric data | Physical/behavioural characteristics for unique identification (Art. 4(14)) |
| Health data | Physical/mental health, healthcare provision (Recital 35) |
| Sex life or sexual orientation | Sexual behaviour, preferences, orientation |
Processing standard: General prohibition with ten exceptions (Art. 9(2)(a)-(j))
CCPA/CPRA — Sensitive Personal Information (California)
Cal. Civ. Code §1798.140(ae) defines sensitive personal information as:
| Category | Definition Summary |
|---|---|
| Social Security, driver's licence, state ID, passport | Government-issued identifiers |
| Account log-in with password/security credentials | Financial account access data |
| Debit/credit card combined with security code | Payment card data with authentication |
| Precise geolocation | Location within 1,850 feet (GPS-level) |
| Racial or ethnic origin | Same scope as GDPR |
| Religious or philosophical beliefs | Same scope as GDPR |
| Union membership | Same scope as GDPR |
| Personal communications (mail, email, text) | Content of non-public communications |
| Genetic data | DNA, genetic test results |
| Biometric data | Physiological, biological, behavioural characteristics for identification |
| Health information | Physical/mental health condition, diagnosis, treatment |
| Sex life or sexual orientation | Sexual activity, preferences |
Consumer right: Right to limit use and disclosure of sensitive PI (§1798.121)
HIPAA — Protected Health Information (United States)
45 CFR §160.103 defines PHI as individually identifiable health information held or transmitted by a covered entity or business associate, in any form, that relates to:
| Element | Description |
|---|---|
| Physical or mental health condition | Past, present, or future |
| Provision of health care | Treatment, services, payments |
| Payment for health care | Claims, billing, insurance |
| Identifiability | Information that identifies or could identify the individual |
18 HIPAA Identifiers (45 CFR §164.514(b)): Names, geographic data (smaller than state), dates (except year), phone, fax, email, SSN, medical record number, health plan beneficiary number, account number, certificate/licence number, vehicle identifiers, device identifiers, web URLs, IP addresses, biometric identifiers, full-face photographs, any unique identifying number
Standard: Minimum necessary standard; use and disclosure limited to minimum necessary for purpose
LGPD Art. 5-II — Sensitive Personal Data (Brazil)
| Category | Definition Summary |
|---|---|
| Racial or ethnic origin | Same scope as GDPR |
| Religious belief | Religious conviction or practice |
| Political opinion | Political views or affiliations |
| Trade union membership | Union affiliation |
| Religious, philosophical, or political organisation | Broader than GDPR — includes organisational membership |
| Health data | Physical/mental health |
| Sex life | Sexual activity |
| Genetic data | Genetic information |
| Biometric data | Biometric characteristics for identification |
Processing standard: Consent must be specific and highlighted; other bases available under Art. 11(II)
Cross-Regulation Mapping Matrix
| Data Category | GDPR Art. 9 | CCPA §1798.140(ae) | HIPAA PHI | LGPD Art. 5-II | Unified Tier |
|---|---|---|---|---|---|
| Racial/ethnic origin | Special category | Sensitive PI | N/A (unless health-related) | Sensitive | RESTRICTED |
| Political opinions | Special category | N/A | N/A | Sensitive | RESTRICTED |
| Religious beliefs | Special category | Sensitive PI | N/A | Sensitive | RESTRICTED |
| Trade union membership | Special category | Sensitive PI | N/A | Sensitive | RESTRICTED |
| Genetic data | Special category | Sensitive PI | PHI (if health-related) | Sensitive | RESTRICTED |
| Biometric data (for identification) | Special category | Sensitive PI | PHI (identifier) | Sensitive | RESTRICTED |
| Health data | Special category | Sensitive PI | PHI | Sensitive | RESTRICTED |
| Sex life/orientation | Special category | Sensitive PI | N/A (unless health-related) | Sensitive | RESTRICTED |
| Social Security Number | Personal (direct identifier) | Sensitive PI | PHI (identifier) | Personal (direct) | RESTRICTED |
| Precise geolocation | Personal (may be special if reveals religion/health) | Sensitive PI | PHI (if health-related) | Personal | CONFIDENTIAL+ |
| Financial account with credentials | Personal (financial) | Sensitive PI | N/A | Personal | RESTRICTED |
| Personal communications content | Personal | Sensitive PI | N/A | Personal | CONFIDENTIAL |
| Medical record number | Personal (indirect) | N/A (separate HIPAA regime) | PHI (identifier) | Personal | RESTRICTED (in healthcare context) |
| Health insurance ID | Personal (indirect) | N/A | PHI (identifier) | Personal | RESTRICTED (in healthcare context) |
Show full SKILL.md (337 more words)Show less
Harmonised Classification Approach
Principle: Apply the Highest Standard
When data falls under multiple jurisdictions, apply the most protective classification:
For each data element:
1. Classify under GDPR (personal / special category / criminal)
2. Classify under CCPA (personal information / sensitive PI)
3. Classify under HIPAA (PHI / non-PHI) — if applicable
4. Classify under LGPD (personal / sensitive) — if applicable
5. Assign the unified tier = MAX(all jurisdictional classifications)Unified Tier Assignment Rules
| Jurisdictional Classification | Unified Tier |
|---|---|
| Any regulation classifies as most-sensitive | RESTRICTED |
| GDPR special category OR CCPA sensitive PI OR LGPD sensitive | RESTRICTED |
| HIPAA PHI (any) | RESTRICTED |
| GDPR personal data AND CCPA personal information (not sensitive) | CONFIDENTIAL |
| Non-personal under all applicable regulations | PUBLIC or INTERNAL |
Implementation for Vanguard Financial Services
Jurisdictional Scope
| Jurisdiction | Applicable Law | Vanguard Operations |
|---|---|---|
| EU/EEA | GDPR | EU customer base, Frankfurt data centre |
| United Kingdom | UK GDPR + DPA 2018 | London headquarters, UK customer base |
| California, USA | CCPA/CPRA | US operations, California residents' data |
| Other US States | Various (VCDPA, CPA, CTDPA, etc.) | US operations |
| Brazil | LGPD | Brazilian customer base |
Cross-Jurisdiction Handling Requirements
For data that falls under multiple jurisdictions:
| Scenario | Jurisdictions | Handling |
|---|---|---|
| UK customer health data | UK GDPR + potentially HIPAA if shared with US health insurer | RESTRICTED; Art. 9(2) condition + HIPAA BAA if shared with US covered entity |
| California employee biometric data (fingerprint) | CCPA + Illinois BIPA + GDPR (if EU data subject) | RESTRICTED; CCPA consent + BIPA written consent + GDPR Art. 9(2)(a) |
| Brazilian customer financial data | LGPD + GDPR (if transferred from EU) | CONFIDENTIAL; LGPD lawful basis + GDPR Chapter V transfer safeguards |
| Cross-border employee HR data | UK GDPR + CCPA + LGPD | CONFIDENTIAL (RESTRICTED if contains health/diversity data); satisfy all three frameworks simultaneously |
Regulatory Precedents
- Meta Platforms Ireland (EDPB Binding Decision 01/2023): EUR 1.2 billion fine for EU-US data transfers — underscores the importance of jurisdictional mapping when data crosses borders
- Sephora (CCPA Enforcement, 2022): USD 1.2 million settlement with California AG for failure to honour opt-out of sale of personal information — demonstrated CCPA-specific classification obligations
- ANPD Brazil (2023): First LGPD administrative sanctions for inadequate security measures on sensitive personal data — confirmed LGPD enforcement trajectory
Integration Points
- personal-data-test: GDPR personal data test is the foundation; cross-jurisdiction classification layers additional requirements
- special-category-data: GDPR special categories map to sensitive data across other jurisdictions
- classification-policy: Unified tier from cross-jurisdiction mapping feeds the enterprise classification policy
- data-inventory-mapping: Data inventory must record applicable jurisdictions per data element
© 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/cross-jurisdiction-class 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
Cross Jurisdiction Class 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 |
|---|---|---|---|---|---|---|
| Cross Jurisdiction Class this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.6k | 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 Cross Jurisdiction Class
What does Cross Jurisdiction Class do?
Harmonises data classification across jurisdictions mapping GDPR special categories vs CCPA sensitive PI (1798.140(ae)) vs HIPAA PHI (160.103) vs LGPD sensitive data (Art. Cross Jurisdiction Class is an agent skill from mukul975/Privacy-Data-Protection-Skills.103) vs LGPD sensitive data (Art.
When should I use Cross Jurisdiction Class?
Cross Jurisdiction Class fits situations like: tasks that involve Privacy and GDPR.
How do I install Cross Jurisdiction Class in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cross-jurisdiction-class -a claude-code`. Or copy the skill folder (skills/privacy/cross-jurisdiction-class in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cross-jurisdiction-class in your project. Claude Code loads it when a task matches its description.
How do I install Cross Jurisdiction Class in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cross-jurisdiction-class -a codex`. Or copy the skill folder (skills/privacy/cross-jurisdiction-class in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cross-jurisdiction-class in your project. Codex loads it when a task matches its description.
Can I use Cross Jurisdiction Class 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 cross-jurisdiction-class -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-jurisdiction-class, .gemini/skills/cross-jurisdiction-class, .github/skills/cross-jurisdiction-class and .opencode/skills/cross-jurisdiction-class in your project.
What does Cross Jurisdiction Class need to run?
Going by SKILL.md and its folder, Cross Jurisdiction Class needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Cross Jurisdiction Class 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 Cross Jurisdiction Class 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 Cross Jurisdiction Class use?
Cross Jurisdiction Class 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 Cross Jurisdiction Class use?
About 2.6k 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.8k tokens, read only when the agent opens those files.
What are the alternatives to Cross Jurisdiction Class?
Skills that share tags, products or a category with Cross Jurisdiction Class: 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 Cross Jurisdiction Class?
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.