GitHub Airplane Mode
vincentkoc/dotskills
Inspect or switch the local Git and GitHub download guard using an already-installed compatible low-data command.
Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures.
Install Ropa Maintenance Workflow
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-maintenance-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-maintenance-workflow --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/ropa-maintenance-workflow .claude/skills/ropa-maintenance-workflow && 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 "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .claude/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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/ropa-maintenance-workflowType 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 ropa-maintenance-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-maintenance-workflow --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/ropa-maintenance-workflow .agents/skills/ropa-maintenance-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .agents/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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 ropa-maintenance-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-maintenance-workflow --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/ropa-maintenance-workflow .cursor/skills/ropa-maintenance-workflow && 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 "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .cursor/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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/ropa-maintenance-workflow--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 ropa-maintenance-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-maintenance-workflow --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/ropa-maintenance-workflow .gemini/skills/ropa-maintenance-workflow && 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 "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .gemini/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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 ropa-maintenance-workflowInstalls 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 ropa-maintenance-workflow -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/ropa-maintenance-workflow .github/skills/ropa-maintenance-workflow && 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 "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .github/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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 ropa-maintenance-workflow -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 ropa-maintenance-workflow --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/ropa-maintenance-workflow .opencode/skills/ropa-maintenance-workflow && 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 "ropa-maintenance-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-maintenance-workflow into .opencode/skills/ropa-maintenance-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-maintenance-workflow", 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
ropa-maintenance-workflow- GitHub stars
- 295
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,383 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures.
- Works in 4 steps: Change request form: Add a mandatory… → Privacy review gate: Any change request… → Pre-deployment checklist: Add "RoPA… → …
- Tasks that involve Git workflow
- SKILL.md covers Overview, Update Triggers, Change Management Integration and Version Control, plus 2 more sections
- Runs Python scripts from its folder
What it does
Ropa Maintenance Workflow is an agent skill from mukul975/Privacy-Data-Protection-Skills. Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures. Activate for RoPA updates, record maintenance, change management, version history, review scheduling.
Its SKILL.md is about 2.9k 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 Git workflow and Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Git workflow
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the ropa-maintenance-workflow skill to establish ongoing RoPA maintenance processes including update triggers, change management integration…”
- “/ropa-maintenance-workflow”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Change request form: Add a mandatory privacy impact field to the IT change request form: "Does this change introduce, modify, or…
- Privacy review gate: Any change request answered "Yes" or "Unsure" triggers a privacy review before approval. The DPO office assesses…
- Pre-deployment checklist: Add "RoPA updated and approved" as a mandatory checklist item before go-live for changes involving personal data.
- Post-deployment verification: Within 7 days of deployment, verify that the RoPA entry reflects the production system configuration.
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
Ropa Maintenance Workflow loads about 2.9k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 1,383 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,383 words, ~2,949 tokens.
Download SKILL.mdSave it as
.claude/skills/ropa-maintenance-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ropa-maintenance-workflow
- description
- Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures. Activate for RoPA updates, record maintenance, change management, version history, review scheduling.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- records-of-processing
- metadata.tags
- gdpr, ropa, maintenance, change-management, version-control, review-cycle, governance
RoPA Maintenance Workflow
Overview
Creating a RoPA is a point-in-time exercise; maintaining it is a continuous obligation. GDPR Art. 5(2) accountability requires that processing records reflect current reality at all times. The Belgian DPA in Decision 21/2022 sanctioned an organisation whose RoPA had not been updated for over two years despite significant processing changes. This skill establishes the governance framework, triggers, workflows, and verification procedures to keep the RoPA accurate, current, and audit-ready.
Update Triggers
A RoPA update must be initiated when any of the following events occur:
Mandatory Triggers (Immediate Update Required)
| Trigger Event | Affected Fields | Update Deadline |
|---|---|---|
| New processing activity introduced | All Art. 30(1) fields for new entry | Before processing commences |
| Processing activity discontinued | Entire entry archived | Within 30 days of cessation |
| Change in processing purpose | Art. 30(1)(b) — purposes | Before new purpose is acted upon |
| New category of data subjects added | Art. 30(1)(c) — data subjects | Before data collection from new category |
| New special category data processed | Art. 30(1)(c) — personal data; Art. 9(2) condition | Before processing begins |
| New processor engaged | Art. 30(1)(d) — recipients | Before processor begins processing |
| Processor terminated | Art. 30(1)(d) — recipients | Within 30 days of termination |
| New international transfer | Art. 30(1)(e) — transfers | Before transfer commences |
| Transfer mechanism invalidated | Art. 30(1)(e) — transfers | Immediately (processing must cease or alternative mechanism implemented) |
| Retention period changed (legal or policy) | Art. 30(1)(f) — retention | Within 30 days of change |
| Material change to security measures | Art. 30(1)(g) — security | Within 30 days of change |
| DPO appointment or change | Art. 30(1)(a) — controller identity | Within 14 days of change |
| Organisational restructuring affecting controller identity | Art. 30(1)(a) — controller identity | Within 30 days of effective date |
| Data breach involving the processing activity | Art. 30(1)(g) — security measures; potentially all fields | Within 30 days of remediation completion |
Periodic Triggers (Scheduled Review)
| Review Type | Frequency | Scope |
|---|---|---|
| Full RoPA review | Annually (minimum) | All entries, all fields |
| High-risk processing review | Every 6 months | Entries linked to DPIA, special category data, or large-scale processing |
| Processor/vendor review | Annually, aligned with DPA renewal | Recipient and transfer fields |
| Retention schedule alignment | Annually | Retention fields cross-referenced against retention policy |
| Post-audit remediation review | 30/60/90 days after audit findings | Entries with identified findings |
Conditional Triggers (Event-Driven)
- Supervisory authority investigation or inquiry
- Data subject complaint related to a processing activity
- Legislative or regulatory change affecting processing (e.g., new adequacy decision, SCC update, sector regulation)
- Completion of a DPIA that identifies changes to processing
- Merger, acquisition, or divestiture affecting entity structure
- New IT system deployment or significant system upgrade
- Office relocation or data centre migration
Change Management Integration
Integration with IT Change Management
The RoPA update workflow must be embedded in the organisation's IT change management process (e.g., ITIL change advisory board, DevOps deployment pipeline):
- Change request form: Add a mandatory privacy impact field to the IT change request form: "Does this change introduce, modify, or discontinue any processing of personal data? (Yes/No/Unsure)"
- Privacy review gate: Any change request answered "Yes" or "Unsure" triggers a privacy review before approval. The DPO office assesses whether a RoPA update is required.
- Pre-deployment checklist: Add "RoPA updated and approved" as a mandatory checklist item before go-live for changes involving personal data.
- Post-deployment verification: Within 7 days of deployment, verify that the RoPA entry reflects the production system configuration.
Example workflow for Helix Biotech Solutions:
IT Change Request Submitted
|
v
Privacy Impact Field = "Yes" or "Unsure"?
| \
v (Yes/Unsure) (No) -> Standard IT change process
DPO Office Review (2 business days)
|
v
RoPA Update Required?
| \
v (Yes) (No) -> Document decision, proceed with change
Draft RoPA Amendment
|
v
DPO Approval
|
v
Processing Owner Sign-off
|
v
RoPA System Updated
|
v
Change Approved for Deployment
|
v
Post-Deployment Verification (7 days)Integration with Vendor Management
- New vendor onboarding: The procurement process must include a step requiring the DPO office to create or update the relevant RoPA entry before the vendor begins processing personal data.
- Annual vendor review: The annual vendor review cycle triggers a review of all RoPA entries referencing that vendor.
- Vendor termination: The vendor offboarding checklist includes updating the RoPA to remove the vendor as a recipient and documenting data return/deletion.
Integration with HR Processes
- New department or team creation: Triggers a processing activity discovery session for the new unit.
- DPO change: Automatic update of DPO details across all RoPA entries within 14 days.
- Role changes: When a processing owner changes role, reassign RoPA entry ownership.
Version Control
Versioning Scheme
Adopt a structured version numbering system:
- Major version (X.0): Incremented when a processing activity is added or removed, or when the RoPA structure changes.
- Minor version (X.Y): Incremented when existing fields are updated (new purpose, changed retention, updated recipients).
- Patch version (X.Y.Z): Incremented for administrative corrections (typos, formatting, contact detail updates).
Example version history:
| Version | Date | Change Description | Changed By | Approved By |
|---|---|---|---|---|
| 3.0 | 2025-01-15 | Added RPA-048: Genomic data analysis for personalised medicine programme | Dr. Elena Voss | Prof. Schmidt (CEO) |
| 3.1 | 2025-04-22 | Updated RPA-007: Added Veeva Vault CRM as recipient with DPA reference | Anna Berger, Privacy Analyst | Dr. Elena Voss |
| 3.1.1 | 2025-05-10 | Corrected DPO phone number across all entries | System (bulk update) | Dr. Elena Voss |
| 3.2 | 2025-08-01 | Updated RPA-023: Retention period changed from 36 to 24 months per new marketing data retention policy | Julia Richter, Marketing | Dr. Elena Voss |
| 3.3 | 2025-11-20 | Updated RPA-001: Removed former payroll processor, added ADP as replacement | Markus Bauer, HR | Dr. Elena Voss |
| 4.0 | 2026-02-01 | Archived RPA-012: Legacy CRM decommissioned. Added RPA-049: New Salesforce implementation | Dr. Elena Voss | Prof. Schmidt |
Show full SKILL.md (542 more words)Show less
Change Log Requirements
Each change must record:
- What changed: Specific field(s) and old vs new values.
- Why it changed: The trigger event (new system, regulatory change, audit finding, vendor change).
- Who made the change: Name and role of the person who drafted the update.
- Who approved the change: DPO or delegated approver signature.
- When it was changed: Date of approval and date of system entry.
- Evidence reference: Link to the triggering document (change request, DPA, audit finding, DPIA).
Retention of Previous Versions
Maintain previous RoPA versions for a minimum of 5 years (or longer if required by sector regulation) to demonstrate accountability and support supervisory authority investigations that may inquire about historical processing activities.
Stakeholder Review Cycles
Annual Full Review Process
Timeline: 8 weeks
| Week | Activity | Responsible | Deliverable |
|---|---|---|---|
| 1-2 | DPO office distributes current RoPA entries to processing owners for self-review | DPO office | Distribution log |
| 3-4 | Processing owners review and annotate their entries, flagging changes | Processing owners | Annotated entries |
| 5 | DPO office consolidates changes and resolves conflicts | Privacy analyst | Consolidated change list |
| 6 | DPO reviews consolidated changes for legal accuracy | DPO | Reviewed change list |
| 7 | Updated entries submitted for processing owner final sign-off | Processing owners | Signed entries |
| 8 | Updated RoPA published, version incremented, change log updated | DPO office | Updated RoPA v.X.0 |
Quarterly Quick Review (High-Risk Processing)
For entries linked to DPIAs or involving special category data:
- DPO office sends a confirmation request to the processing owner: "Has anything changed about this processing activity since [last review date]?"
- If no changes, the processing owner confirms in writing (email or system acknowledgement). The last_reviewed_date is updated.
- If changes are identified, the full update workflow is triggered.
Completeness Verification Procedures
Automated Verification (Monthly)
Run the RoPA validation script monthly to check:
- All mandatory fields are populated (no empty/null values).
- No vague purpose terms are present.
- No vague retention terms are present.
- All international transfers have documented safeguard mechanisms.
- All entries have been reviewed within the past 12 months (staleness check).
- All entries have an assigned processing owner who is still active in the organisation.
- All referenced DPAs have not expired.
Manual Verification (Annually)
- Cross-reference the RoPA against the IT application inventory: every system processing personal data should map to at least one RoPA entry.
- Cross-reference against the vendor/processor register: every processor should appear as a recipient in at least one RoPA entry.
- Cross-reference against the DPIA register: every DPIA should link to a RoPA entry, and vice versa for high-risk processing.
- Sample verification: interview 20% of processing owners to confirm RoPA accuracy.
- Review privacy notices against RoPA purposes to ensure alignment.
Completeness Score
Calculate a completeness score for supervisory authority readiness:
| Metric | Weight | Scoring |
|---|---|---|
| All mandatory fields populated | 30% | 100% if all entries complete, deduct proportionally |
| No vague terms in purposes or retention | 15% | 100% if none detected, deduct per occurrence |
| All transfers have safeguards documented | 15% | 100% if all documented |
| All entries reviewed within 12 months | 20% | 100% if all current, deduct per stale entry |
| All processors have current DPAs | 10% | 100% if all current |
| All high-risk entries linked to DPIAs | 10% | 100% if all linked |
Target: 95% or above for supervisory authority readiness.
© 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/ropa-maintenance-workflow 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
Ropa Maintenance Workflow 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 |
|---|---|---|---|---|---|---|
| Ropa Maintenance Workflow this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Airplane Modevincentkoc/dotskills | 107 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Repo Prepglebis/claude-skills | 389 | — | ~1.6k | Automated safety check: Pass | MIT | |
| 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 |
Similar skills
Repo Prep
glebis/claude-skills
Interactively prepare a code repository for publication — LICENSE, NOTICE, AUTHORSHIP, README sections, package metadata, .gitignore, community docs (CONTRIBUTING/CODEOFCONDUCT/SECURITY/CHANGELOG)…
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
More from mukul975/Privacy-Data-Protection-Skills
All 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 Ropa Maintenance Workflow
What does Ropa Maintenance Workflow do?
Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures. Ropa Maintenance Workflow is an agent skill from mukul975/Privacy-Data-Protection-Skills. Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures.
When should I use Ropa Maintenance Workflow?
Ropa Maintenance Workflow fits situations like: tasks that involve Git workflow; tasks that involve Privacy and GDPR.
How do I install Ropa Maintenance Workflow in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-maintenance-workflow -a claude-code`. Or copy the skill folder (skills/privacy/ropa-maintenance-workflow in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/ropa-maintenance-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ropa Maintenance Workflow in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-maintenance-workflow -a codex`. Or copy the skill folder (skills/privacy/ropa-maintenance-workflow in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/ropa-maintenance-workflow in your project. Codex loads it when a task matches its description.
Can I use Ropa Maintenance Workflow 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 ropa-maintenance-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ropa-maintenance-workflow, .gemini/skills/ropa-maintenance-workflow, .github/skills/ropa-maintenance-workflow and .opencode/skills/ropa-maintenance-workflow in your project.
What does Ropa Maintenance Workflow need to run?
Going by SKILL.md and its folder, Ropa Maintenance Workflow needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Ropa Maintenance Workflow 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 Ropa Maintenance Workflow 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 Ropa Maintenance Workflow use?
Ropa Maintenance Workflow 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 Ropa Maintenance Workflow use?
About 2.9k tokens (SKILL.md is roughly 12k 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 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Ropa Maintenance Workflow?
Skills that share tags, products or a category with Ropa Maintenance Workflow: GitHub Airplane Mode (vincentkoc/dotskills, 107 stars), Repo Prep (glebis/claude-skills, 389 stars), C15t (c15t/c15t, 1.9k stars) and HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ropa Maintenance Workflow?
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.