C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology.
Install Transfer Impact Assessment
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill transfer-impact-assessment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills transfer-impact-assessment --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/transfer-impact-assessment .claude/skills/transfer-impact-assessment && 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 "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .claude/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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/transfer-impact-assessmentType 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 transfer-impact-assessment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills transfer-impact-assessment --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/transfer-impact-assessment .agents/skills/transfer-impact-assessment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .agents/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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 transfer-impact-assessment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills transfer-impact-assessment --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/transfer-impact-assessment .cursor/skills/transfer-impact-assessment && 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 "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .cursor/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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/transfer-impact-assessment--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 transfer-impact-assessment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills transfer-impact-assessment --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/transfer-impact-assessment .gemini/skills/transfer-impact-assessment && 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 "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .gemini/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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 transfer-impact-assessmentInstalls 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 transfer-impact-assessment -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/transfer-impact-assessment .github/skills/transfer-impact-assessment && 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 "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .github/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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 transfer-impact-assessment -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 transfer-impact-assessment --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/transfer-impact-assessment .opencode/skills/transfer-impact-assessment && 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 "transfer-impact-assessment" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/transfer-impact-assessment into .opencode/skills/transfer-impact-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transfer-impact-assessment", 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
transfer-impact-assessment- GitHub stars
- 301
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,708 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology.
- Works in 6 steps: Know Your Transfers → Identify the Transfer Tool Relied Upon → Assess Whether the Transfer Tool Is… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, EDPB Six-Step Methodology, Country-Specific Assessment… and TIA Documentation Requirements
- Runs Python scripts from its folder
What it does
Transfer Impact Assessment is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology. Covers destination country surveillance law assessment, European Essential Guarantees evaluation, and supplementary measures determination. Keywords: TIA, transfer impact assessment, Schrems II, EDPB recommendations, supplementary measures.
Its SKILL.md is about 3.7k 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 transfer-impact-assessment skill to guide the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020…”
- “/transfer-impact-assessment”
Requirements
- Python 3
Workflow steps
6 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
Transfer Impact Assessment loads about 3.7k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,708 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,708 words, ~3,664 tokens.
Download SKILL.mdSave it as
.claude/skills/transfer-impact-assessment/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- transfer-impact-assessment
- description
- Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology. Covers destination country surveillance law assessment, European Essential Guarantees evaluation, and supplementary measures determination. Keywords: TIA, transfer impact assessment, Schrems II, EDPB recommendations, supplementary measures.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- cross-border-transfers
- metadata.tags
- tia, transfer-impact-assessment, schrems-ii, edpb-recommendations, surveillance-assessment
Conducting Transfer Impact Assessment
Overview
Following the Court of Justice of the European Union's judgment in Schrems II (Case C-311/18, 16 July 2020), organisations relying on Standard Contractual Clauses (SCCs) or other Art. 46 GDPR transfer mechanisms must conduct a Transfer Impact Assessment (TIA) to evaluate whether the legal framework of the destination country provides an essentially equivalent level of protection for personal data. The EDPB adopted Recommendations 01/2020 on measures that supplement transfer tools to ensure compliance with the EU level of protection of personal data (Version 2.0, adopted 18 June 2021), establishing a six-step methodology for this assessment.
EDPB Six-Step Methodology
Step 1: Know Your Transfers
Map all personal data transfers to third countries, identifying:
| Element | Required Information |
|---|---|
| Transfer identification | Unique reference for each transfer or set of transfers |
| Data exporter | Legal entity name, establishment, role (controller/processor) |
| Data importer | Legal entity name, establishment, role (controller/processor) |
| Transfer mechanism | SCCs (specifying module), BCRs, Art. 49 derogation |
| Data categories | Personal data types transferred, including any special categories |
| Data subjects | Categories of individuals whose data is transferred |
| Purpose | Specific purpose(s) for which the data is processed after transfer |
| Destination country | Country where the importer processes the data |
| Onward transfers | Any further transfers from the importer to other jurisdictions |
| Format and channel | How data is transmitted (API, SFTP, email, physical media) |
| Storage duration | How long data is retained in the destination country |
Athena Global Logistics example transfer mapping:
| Transfer Ref | Exporter | Importer | Destination | Mechanism | Data Categories |
|---|---|---|---|---|---|
| TIA-2025-HK-001 | Athena Global Logistics GmbH | TransPacific Freight Solutions Ltd | Hong Kong SAR | SCCs Module 2 | Customer names, addresses, customs IDs, consignment data |
| TIA-2025-IN-001 | Athena Global Logistics GmbH | Athena Freight Services India Pvt Ltd | India | SCCs Module 1 | Employee names, contact details, performance records |
| TIA-2025-US-001 | Athena Global Logistics GmbH | Meridian Cloud Services Inc | United States | EU-US DPF + SCCs backup | Customer data, operational analytics |
Step 2: Identify the Transfer Tool Relied Upon
For each transfer, confirm the Art. 46 transfer mechanism:
- SCCs (Art. 46(2)(c)): Identify the specific module (1-4) and version (2021/914).
- BCRs (Art. 47): Confirm approval status and scope coverage.
- Ad hoc contractual clauses (Art. 46(3)(a)): Confirm SA authorisation.
- Codes of conduct (Art. 46(2)(e)): Confirm approved code and binding commitments.
- Certification mechanisms (Art. 46(2)(f)): Confirm certification status and scope.
Document the specific clauses that may be affected by the destination country legal framework, particularly:
- Clause 14 (SCCs) — local laws and obligations relating to access by public authorities
- Clause 15 (SCCs) — obligations of the data importer in case of government access
Step 3: Assess Whether the Transfer Tool Is Effective in Light of All Circumstances
This is the core of the TIA. Assess the legal framework of the destination country against the four European Essential Guarantees (EDPB Recommendations 02/2020):
Essential Guarantee 1: Processing Should Be Based on Clear, Precise, and Accessible Rules
| Assessment Question | Analysis |
|---|---|
| Is government access to personal data based on legislation? | Identify the specific statutes authorising government access (e.g., FISA Section 702, EO 12333 for US; National Security Law for Hong Kong; IT Act Section 69 for India) |
| Are the rules publicly available? | Assess whether the legislation and its implementing regulations are published and accessible |
| Is the scope of government access clearly defined? | Assess whether the legislation specifies the categories of data, persons, or situations subject to access |
| Are there exceptions or conditions for access? | Identify any limitations, thresholds, or prior authorisation requirements |
Essential Guarantee 2: Necessity and Proportionality
| Assessment Question | Analysis |
|---|---|
| Is government access limited to what is strictly necessary? | Assess whether the legislation requires a showing of necessity for each access request |
| Is the scope proportionate to the stated objective? | Evaluate whether bulk/mass surveillance is permitted or whether access must be targeted |
| Are there safeguards against abuse? | Assess minimisation requirements, purpose limitations, and retention limits for accessed data |
Essential Guarantee 3: Independent Oversight Mechanism
| Assessment Question | Analysis |
|---|---|
| Is there prior judicial or independent authorisation? | Determine whether a court or independent body must approve access requests before execution |
| Is there ongoing oversight? | Assess whether an independent body monitors government access activities |
| Are oversight bodies genuinely independent? | Evaluate the appointment, tenure, and dismissal conditions of oversight body members |
Essential Guarantee 4: Effective Remedies Available to the Individual
| Assessment Question | Analysis |
|---|---|
| Can individuals challenge government access in court? | Assess whether there is a right to judicial review of surveillance measures |
| Is there an effective notification mechanism? | Determine whether individuals are notified of surveillance (even if delayed) |
| Can individuals obtain a remedy? | Assess available remedies (compensation, data deletion, injunctive relief) |
Step 4: Adopt Supplementary Measures
If Step 3 reveals that the transfer tool is not effective on its own, identify and implement supplementary measures to bridge the protection gap:
Technical Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| End-to-end encryption (data in transit and at rest) with EU-held keys | High — prevents importer and government access to plaintext | Data storage or transit where importer does not need to process plaintext |
| Pseudonymisation with EU-held mapping table | High — transferred data cannot be attributed to identified individuals | Analytics, research, or aggregation where identification is not needed at the importer |
| Split processing | High — no single entity in the third country holds the complete dataset | Multi-party computation or processing split between jurisdictions |
| Transport-layer encryption (TLS 1.3) | Medium — protects data in transit but not against compelled disclosure at rest | All transfers as a baseline measure; insufficient alone for high-risk jurisdictions |
Contractual Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| Obligation to challenge disproportionate government access requests | Medium — depends on legal standing and judicial independence in destination country | All SCC-based transfers (already required under Clause 15) |
| Transparency obligation for government access requests received | Medium — provides visibility but does not prevent access | All transfers |
| Audit rights exercisable by the exporter or independent auditor | Medium — verifies compliance but is retrospective | All transfers |
| Warrant canary (commitment to publish regular transparency reports) | Low-Medium — provides indirect signal but does not prevent access | US transfers where gag orders may apply |
Organisational Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| Strict internal access policies limiting who can access transferred data | Medium — reduces the surface of potential government access | All transfers |
| Regular transparency reports on government access requests | Medium — provides accountability | All transfers |
| Data protection impact assessment for government access scenarios | Medium — proactive risk identification | High-risk jurisdiction transfers |
| Adoption of ISO 27001/27701 certification by the importer | Medium — independent verification of security and privacy controls | All transfers |
Show full SKILL.md (660 more words)Show less
Step 5: Procedural Steps If Supplementary Measures Are Adopted
- Document the supplementary measures in the SCC Annex or in a separate addendum.
- Implement the technical measures before commencing or continuing the transfer.
- Execute contractual amendments reflecting the supplementary measures.
- Verify the importer has the technical capability and legal ability to implement the measures.
- Notify the competent SA if required (for ad hoc contractual clauses under Art. 46(3)(a)).
Step 6: Re-Evaluate at Appropriate Intervals
- Schedule periodic TIA reviews: at minimum annually, or upon any of the following triggers:
- New legislation enacted in the destination country affecting government access
- Court rulings in the destination country affecting privacy protections
- Changes to the EC adequacy decision landscape
- EDPB or national SA guidance updates
- Material change in the nature, volume, or sensitivity of transferred data
- Government access request received by the importer
- Document each re-evaluation with the date, trigger, findings, and any changes to supplementary measures.
- If re-evaluation concludes that effective protection cannot be ensured, suspend the transfer and notify the competent SA.
Country-Specific Assessment Summaries
United States
| Factor | Assessment |
|---|---|
| Key surveillance laws | FISA Section 702, EO 12333, CLOUD Act, National Security Letters (18 USC 2709) |
| Necessity/proportionality | EO 14086 (October 2022) introduced necessity and proportionality requirements; applies to all signals intelligence activities |
| Independent oversight | FISC (prior authorisation for Section 702); PCLOB (oversight); DPRC (redress for EU data subjects) |
| Remedies | DPRC mechanism established under EO 14086; binding determinations |
| Overall assessment | If importer is DPF-certified: adequacy decision applies. If not DPF-certified: SCCs with supplementary measures (encryption, contractual transparency) |
People's Republic of China
| Factor | Assessment |
|---|---|
| Key surveillance laws | Cybersecurity Law (Art. 28, 37), National Intelligence Law (Art. 7, 14), Data Security Law (Art. 35-36), PIPL (Art. 38-43) |
| Necessity/proportionality | National Intelligence Law Art. 7 imposes broad cooperation obligations; no explicit proportionality requirement |
| Independent oversight | No independent judicial oversight of intelligence access; procuratorate oversight is not independent from the state |
| Remedies | Limited judicial remedies for foreign data subjects against state surveillance |
| Overall assessment | High risk; supplementary measures must include strong encryption with EU-held keys; consider data minimisation and pseudonymisation before transfer; for some data categories, transfer may not be possible with effective protection |
India
| Factor | Assessment |
|---|---|
| Key surveillance laws | IT Act 2000 Section 69 (interception), Telegraph Act 1885 Section 5, DPDP Act 2023 Section 36 (government exemptions) |
| Necessity/proportionality | Section 69 requires ministerial authorisation but proportionality review is limited; mass surveillance capability through CMS (Central Monitoring System) |
| Independent oversight | No prior judicial authorisation for interception; review committee is executive-appointed |
| Remedies | Limited remedies under IT Act; High Court writ jurisdiction available but practical access is constrained |
| Overall assessment | Medium-High risk; supplementary measures should include encryption, contractual transparency, and audit rights; TIA should assess specific risk based on data category and importer profile |
Hong Kong SAR
| Factor | Assessment |
|---|---|
| Key surveillance laws | Interception of Communications and Surveillance Ordinance (Cap. 589), National Security Law (2020), Safeguarding National Security Ordinance (2024) |
| Necessity/proportionality | Cap. 589 requires judicial authorisation for interception; however, NSL provides broad powers with limited proportionality review |
| Independent oversight | Commissioner on Interception of Communications and Surveillance provides oversight under Cap. 589; NSL cases subject to designated judges |
| Remedies | Judicial review available under Cap. 589; limited practical remedies under NSL |
| Overall assessment | Medium risk (elevated since NSL enactment); supplementary measures should include encryption and contractual obligations; assess sensitivity of data and likelihood of government interest |
TIA Documentation Requirements
Each TIA must be documented and include:
- Transfer identification (Step 1 mapping data)
- Transfer mechanism details (Step 2 analysis)
- Destination country legal assessment with specific legislation citations (Step 3)
- European Essential Guarantees analysis for each identified law (Step 3)
- Supplementary measures identified and rationale (Step 4)
- Implementation status of supplementary measures (Step 5)
- Re-evaluation schedule and triggers (Step 6)
- Overall conclusion: transfer may proceed / transfer may proceed with supplementary measures / transfer must be suspended
- Sign-off by the DPO or Head of Data Protection
- Version history tracking all updates and re-evaluations
© 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/transfer-impact-assessment 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
Transfer Impact Assessment 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 |
|---|---|---|---|---|---|---|
| Transfer Impact Assessment this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~3.7k | 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 Transfer Impact Assessment
What does Transfer Impact Assessment do?
Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology. Transfer Impact Assessment is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology.
When should I use Transfer Impact Assessment?
Transfer Impact Assessment fits situations like: tasks that involve Privacy and GDPR.
How do I install Transfer Impact Assessment in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill transfer-impact-assessment -a claude-code`. Or copy the skill folder (skills/privacy/transfer-impact-assessment in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/transfer-impact-assessment in your project. Claude Code loads it when a task matches its description.
How do I install Transfer Impact Assessment in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill transfer-impact-assessment -a codex`. Or copy the skill folder (skills/privacy/transfer-impact-assessment in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/transfer-impact-assessment in your project. Codex loads it when a task matches its description.
Can I use Transfer Impact Assessment 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 transfer-impact-assessment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/transfer-impact-assessment, .gemini/skills/transfer-impact-assessment, .github/skills/transfer-impact-assessment and .opencode/skills/transfer-impact-assessment in your project.
What does Transfer Impact Assessment need to run?
Going by SKILL.md and its folder, Transfer Impact Assessment needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Transfer Impact Assessment 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 Transfer Impact Assessment 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 Transfer Impact Assessment use?
Transfer Impact Assessment 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 Transfer Impact Assessment use?
About 3.7k tokens (SKILL.md is roughly 15k 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 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Transfer Impact Assessment?
Skills that share tags, products or a category with Transfer Impact Assessment: 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 Transfer Impact Assessment?
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.