Google Cloud Waf Security
google/skills
Generates security-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework (WAF).
Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art.
Install Cloud Migration Dpia
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-migration-dpia -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cloud-migration-dpia --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/cloud-migration-dpia .claude/skills/cloud-migration-dpia && 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 "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .claude/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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/cloud-migration-dpiaType 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 cloud-migration-dpia -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cloud-migration-dpia --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/cloud-migration-dpia .agents/skills/cloud-migration-dpia && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .agents/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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 cloud-migration-dpia -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cloud-migration-dpia --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/cloud-migration-dpia .cursor/skills/cloud-migration-dpia && 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 "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .cursor/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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/cloud-migration-dpia--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 cloud-migration-dpia -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cloud-migration-dpia --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/cloud-migration-dpia .gemini/skills/cloud-migration-dpia && 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 "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .gemini/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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 cloud-migration-dpiaInstalls 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 cloud-migration-dpia -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/cloud-migration-dpia .github/skills/cloud-migration-dpia && 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 "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .github/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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 cloud-migration-dpia -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 cloud-migration-dpia --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/cloud-migration-dpia .opencode/skills/cloud-migration-dpia && 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 "cloud-migration-dpia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cloud-migration-dpia into .opencode/skills/cloud-migration-dpia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-migration-dpia", 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
cloud-migration-dpia- GitHub stars
- 295
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,292 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art.
- Works in 6 steps: Cloud Processing Mapping (Week 1) → Controller-Processor Analysis (Week 2) → International Transfer Assessment (Week 3) → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Framework, Cloud Service Models and… and DPIA Methodology for Cloud…, plus 2 more sections
- Runs Python scripts from its folder
What it does
Cloud Migration Dpia is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art. 28, international transfer assessment, encryption requirements, and shared responsibility model evaluation. Activate for cloud adoption, SaaS procurement, or data centre migration projects. Keywords: cloud migration, DPIA, Art. 28, processor, encryption, shared responsibility, SaaS, IaaS, PaaS.
Its SKILL.md is about 2.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 and Cloud architecture. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
- Tasks that involve Cloud architecture
Example prompts
- “Use the cloud-migration-dpia skill to guide DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art”
- “/cloud-migration-dpia”
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
Cloud Migration Dpia loads about 2.7k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 1,292 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,292 words, ~2,749 tokens.
Download SKILL.mdSave it as
.claude/skills/cloud-migration-dpia/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cloud-migration-dpia
- description
- Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art. 28, international transfer assessment, encryption requirements, and shared responsibility model evaluation. Activate for cloud adoption, SaaS procurement, or data centre migration projects. Keywords: cloud migration, DPIA, Art. 28, processor, encryption, shared responsibility, SaaS, IaaS, PaaS.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-impact-assessment
- metadata.tags
- cloud-migration, dpia, art-28, processor, encryption, shared-responsibility
Assessing Cloud Migration Privacy
Overview
Migrating personal data to cloud infrastructure (IaaS, PaaS, SaaS) introduces fundamental changes to the data protection landscape: the controller cedes physical control over personal data to a cloud service provider (CSP) acting as processor, creating dependencies on the CSP's security measures, geographic infrastructure, and sub-processor chain. This skill provides a DPIA methodology covering the Art. 28 controller-processor relationship, international transfer assessment under Chapter V, encryption and key management requirements, the shared responsibility model, and sub-processor governance.
Legal Framework
GDPR Art. 28 — Processor Obligations
Art. 28(1) requires the controller to use only processors providing sufficient guarantees to implement appropriate technical and organisational measures to ensure processing meets GDPR requirements.
Art. 28(3) mandates a binding contract or legal act setting out:
- Subject matter and duration of processing
- Nature and purpose of processing
- Type of personal data and categories of data subjects
- Obligations and rights of the controller
- Specific processor obligations including: processing only on documented instructions, confidentiality, security measures, sub-processor approval, data subject rights assistance, deletion/return on termination, audits and inspections
Art. 28(2) — Sub-Processor Authorisation
The processor shall not engage another processor without prior specific or general written authorisation of the controller. In the case of general written authorisation, the processor shall inform the controller of any intended changes concerning the addition or replacement of sub-processors, giving the controller the opportunity to object.
Cloud-Specific Regulatory Guidance
| Authority | Guidance | Key Requirements |
|---|---|---|
| EDPB | Guidelines 07/2020 on controller and processor concepts | Clarified CSP role determination: CSPs acting strictly under controller instructions are processors; CSPs determining purposes of processing for their own use are (joint) controllers |
| CNIL | Recommendations on cloud computing (2022) | Recommended DPIA for cloud migrations involving sensitive data; encryption with customer-held keys; exit strategy requirements |
| BSI (Germany) | C5 Cloud Computing Compliance Catalogue | Technical security criteria for cloud services used by German public sector and recommended for private sector |
| ENISA | Cloud Security Guide for SMEs (2015, updated 2023) | Risk assessment framework for cloud adoption including data protection considerations |
Cloud Service Models and Privacy Responsibilities
Shared Responsibility Model
| Responsibility | IaaS | PaaS | SaaS |
|---|---|---|---|
| Physical infrastructure security | CSP | CSP | CSP |
| Network security | Shared | CSP | CSP |
| Operating system | Customer | CSP | CSP |
| Application security | Customer | Shared | CSP |
| Data classification | Customer | Customer | Customer |
| Data encryption (at rest) | Customer | Shared | CSP (configuration by customer) |
| Data encryption (in transit) | Customer | Shared | CSP |
| Identity and access management | Customer | Shared | Shared |
| Data backup and recovery | Customer | Shared | CSP (configuration by customer) |
| Logging and monitoring | Customer | Shared | CSP (access by customer) |
| Compliance and governance | Customer | Customer | Customer |
| Data subject rights facilitation | Customer | Customer | Customer |
| DPIA | Customer | Customer | Customer |
| Data processing agreement | Customer | Customer | Customer |
Key Privacy Considerations by Service Model
IaaS (Infrastructure as a Service)
- Controller retains most control but also most responsibility
- CSP has physical access to infrastructure but not application-layer data if encrypted
- Customer responsible for OS patching, application security, encryption implementation
- Data residency controlled by customer's region selection
PaaS (Platform as a Service)
- CSP manages infrastructure and platform; customer manages application and data
- CSP may have access to data through platform diagnostics and logging
- Sub-processor chain may be extensive (platform dependencies)
- Data portability may be limited by platform lock-in
SaaS (Software as a Service)
- CSP has broadest access to personal data (application-level access)
- Customer has least control over security measures
- Sub-processor chain often complex and opaque
- Data portability and exit strategy are critical concerns
DPIA Methodology for Cloud Migration
Phase 1: Cloud Processing Mapping (Week 1)
- Inventory all personal data to be migrated to cloud.
- Classify data by sensitivity: public, internal, confidential, restricted.
- Map data flows: on-premises to cloud, cloud to cloud, cloud to third parties.
- Identify all CSP services that will process personal data.
- Determine CSP data processing locations (regions, zones, edge locations).
- Identify the complete sub-processor chain for each CSP service.
Phase 2: Controller-Processor Analysis (Week 2)
- Determine the CSP's role for each service:
- Processor: CSP processes data only on controller's documented instructions
- Joint controller: CSP determines purposes of processing (e.g., CSP uses data for service improvement, analytics, AI training)
- Review the CSP's Data Processing Agreement (DPA) for Art. 28(3) compliance.
- Verify the CSP's sub-processor list and notification mechanism.
- Assess the CSP's audit provisions: on-site audit rights, SOC 2 reports, ISO 27001 certification, penetration test results.
- Review data return and deletion provisions for contract termination.
Phase 3: International Transfer Assessment (Week 3)
- Identify all CSP data processing locations.
- For each location outside the EEA:
- Check for an adequacy decision (Art. 45)
- Verify SCCs are in place (Art. 46(2)(c))
- Conduct Transfer Impact Assessment per EDPB Recommendations 01/2020
- Assess sub-processor locations for international transfers.
- Evaluate technical supplementary measures (encryption with customer-held keys).
- Document the transfer mechanism for each third-country transfer.
Show full SKILL.md (504 more words)Show less
Phase 4: Security and Encryption Assessment (Week 3-4)
- Evaluate CSP encryption capabilities:
- Encryption at rest (algorithm, key length, key management)
- Encryption in transit (TLS version, cipher suites)
- Customer-managed encryption keys (BYOK/HYOK) availability
- Client-side encryption capability
- Assess access controls:
- CSP staff access to customer data (break-glass procedures, access logging)
- Customer IAM integration (SSO, MFA, RBAC)
- Privileged access management
- Evaluate data isolation:
- Multi-tenant vs dedicated infrastructure
- Logical isolation controls
- Data commingling risks
- Review incident response:
- CSP breach notification timeline (Art. 33(2) requires processor to notify controller without undue delay)
- CSP incident response capabilities
- Customer access to security event logs
Phase 5: Risk Assessment (Week 4-5)
| Risk | Description | Typical Level |
|---|---|---|
| CR-R1 | CSP data breach exposing customer personal data | High |
| CR-R2 | Government access to data via CSP (FISA 702, CLOUD Act for US CSPs) | Medium-High |
| CR-R3 | Sub-processor change introducing new risks without controller awareness | Medium |
| CR-R4 | Vendor lock-in preventing data portability or migration to alternative provider | Medium |
| CR-R5 | CSP service termination or insolvency | Medium |
| CR-R6 | CSP using personal data for own purposes (service improvement, AI training) | Medium |
| CR-R7 | Insufficient logging preventing incident investigation | Medium |
| CR-R8 | Data residency violation through CSP infrastructure changes | Medium |
Phase 6: Mitigation and Approval (Week 5-6)
- Implement mitigations for each identified risk.
- Negotiate DPA amendments where CSP standard terms are insufficient.
- Implement customer-managed encryption keys where feasible.
- Establish CSP monitoring procedures (certification renewals, sub-processor changes, incident notifications).
- DPO review and approval.
- Schedule review: annually or upon CSP service change, new sub-processor, or security incident.
Common Cloud Migration DPIA Deficiencies
- Accepting CSP DPA without review: CSP standard DPAs may not meet all Art. 28(3) requirements or may include controller-unfavourable terms (e.g., broad sub-processor general authorisation without objection right).
- Ignoring sub-processor chain: CSPs may use dozens of sub-processors; the controller remains responsible for ensuring adequate protection at each level.
- Relying on CSP-managed encryption only: CSP-managed keys provide protection against physical theft but not against government compulsion to the CSP or CSP staff access.
- No exit strategy: Failure to plan for data return and deletion on contract termination, creating lock-in risk and residual data risk.
- No transfer assessment for multi-region CSP: CSP may replicate data across regions including non-EEA locations for redundancy, backup, or CDN purposes.
Enforcement Precedents
- DPC Ireland vs Meta (2023): EUR 1.2 billion fine for transferring EU user data to US-based cloud infrastructure without valid transfer mechanism.
- DPC Ireland vs Microsoft (LinkedIn, 2023): EUR 310 million fine related to advertising data processing; highlighted the importance of controller-processor role clarity in cloud services.
- CNIL vs Microsoft 365 Education (2022): Raised concerns about data transfers to the US through Microsoft cloud services and insufficient DPA provisions.
- German Federal Data Protection Commissioner (2022): Advised against use of Microsoft 365 in federal agencies due to insufficient transparency about data processing and transfers.
- Dutch DPA DPIA on Microsoft Office 365 (SLM Rijk, 2022): Identified eight high-risk areas in Microsoft 365 processing including diagnostic data collection, data transfers, and insufficient controller access to processing records.
© 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/cloud-migration-dpia 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
Cloud Migration Dpia 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 |
|---|---|---|---|---|---|---|
| Cloud Migration Dpia this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Google Cloud Waf Securitygoogle/skills | 21k | 1 repos | ~4.2k | 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 | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 1 repos | ~3.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
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…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
More from mukul975/Privacy-Data-Protection-Skills
All 278 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.
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.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Cloud Migration Dpia
What does Cloud Migration Dpia do?
Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art. Cloud Migration Dpia is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides DPIA for migrating personal data to cloud infrastructure covering controller-processor analysis under Art.
When should I use Cloud Migration Dpia?
Cloud Migration Dpia fits situations like: tasks that involve Privacy and GDPR; tasks that involve Cloud architecture.
How do I install Cloud Migration Dpia in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-migration-dpia -a claude-code`. Or copy the skill folder (skills/privacy/cloud-migration-dpia in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cloud-migration-dpia in your project. Claude Code loads it when a task matches its description.
How do I install Cloud Migration Dpia in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-migration-dpia -a codex`. Or copy the skill folder (skills/privacy/cloud-migration-dpia in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cloud-migration-dpia in your project. Codex loads it when a task matches its description.
Can I use Cloud Migration Dpia 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 cloud-migration-dpia -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-migration-dpia, .gemini/skills/cloud-migration-dpia, .github/skills/cloud-migration-dpia and .opencode/skills/cloud-migration-dpia in your project.
What does Cloud Migration Dpia need to run?
Going by SKILL.md and its folder, Cloud Migration Dpia needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Cloud Migration Dpia 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 Cloud Migration Dpia 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 Cloud Migration Dpia use?
Cloud Migration Dpia 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 Cloud Migration Dpia use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Cloud Migration Dpia?
Skills that share tags, products or a category with Cloud Migration Dpia: Google Cloud Waf Security (google/skills, 21k stars), C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars) and Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cloud Migration Dpia?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.