Data Export
gustavscirulis/snapgrid
Generates data export/import infrastructure for JSON, CSV, PDF formats with GDPR data portability, share sheet integration, and file import.
Integrates Records of Processing Activities with privacy management platforms including OneTrust, TrustArc, Collibra, and DataGrail.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-tool-integration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-tool-integration --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-tool-integration .claude/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .claude/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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-tool-integrationType 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-tool-integration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-tool-integration --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-tool-integration .agents/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .agents/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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-tool-integration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-tool-integration --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-tool-integration .cursor/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .cursor/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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-tool-integration--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-tool-integration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ropa-tool-integration --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-tool-integration .gemini/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .gemini/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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-tool-integrationInstalls 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-tool-integration -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-tool-integration .github/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .github/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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-tool-integration -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-tool-integration --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-tool-integration .opencode/skills/ropa-tool-integration && 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-tool-integration" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ropa-tool-integration into .opencode/skills/ropa-tool-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ropa-tool-integration", 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.
ropa-tool-integrationIntegrates Records of Processing Activities with privacy management platforms including OneTrust, TrustArc, Collibra, and DataGrail.
Ropa Tool Integration is an agent skill from mukul975/Privacy-Data-Protection-Skills. Integrates Records of Processing Activities with privacy management platforms including OneTrust, TrustArc, Collibra, and DataGrail. Covers API-based synchronization, data mapping import, and automated RoPA population from enterprise tools. Activate for RoPA tool setup, OneTrust integration, TrustArc sync, privacy platform configuration.
Its SKILL.md is about 4.2k 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
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.
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.
Hosts in commands or code, which the agent is likely to contact:
api.trustarc.comhelix-biotech.collibra.comapi.datagrail.ioFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
ONETRUST_CLIENT_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ropa Tool Integration loads about 4.2k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 1,132 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.
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.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,132 words, ~4,172 tokens.
.claude/skills/ropa-tool-integration/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Manual RoPA maintenance using spreadsheets is error-prone, does not scale, and lacks the auditability required for accountability under GDPR Art. 5(2). Privacy management platforms such as OneTrust, TrustArc, Collibra, and DataGrail provide purpose-built RoPA capabilities with workflow automation, audit trails, and regulatory reporting. This skill covers the integration architecture, API-based synchronisation, and data mapping strategies for connecting enterprise IT systems with RoPA management platforms.
| Capability | OneTrust | TrustArc | Collibra | DataGrail |
|---|---|---|---|---|
| Art. 30(1) controller records | Full support with all 7 fields | Full support | Full support via data catalog | Partial — focuses on data mapping |
| Art. 30(2) processor records | Full support | Full support | Supported via custom asset types | Limited |
| Automated discovery | Data discovery module scans systems | Privacy intelligence scans | Data catalog integrations | Real-time data mapping |
| API availability | REST API with OAuth 2.0 | REST API with API key | REST API with OAuth 2.0 | REST API with API key |
| Workflow automation | Built-in approval workflows | Assessment-based workflows | Governance workflows | Request-driven workflows |
| Supervisory authority templates | CNIL, ICO, BfDI, AEPD templates | Multiple SA templates | Custom templates | Limited templates |
| Data mapping integration | Connectors for 500+ systems | Integration hub | Native data catalog connectors | 1,800+ SaaS connectors |
| Export formats | JSON, CSV, PDF, XLSX | PDF, CSV, XLSX | JSON, CSV | JSON, CSV |
| Version control | Built-in versioning and audit trail | Change log | Full lineage and version history | Basic version tracking |
| DPIA linkage | Native linkage to DPIA module | Linked assessments | Cross-reference via catalog | Limited |
OneTrust's Data Mapping module forms the foundation of its RoPA capability. Processing activities are represented as "Processing Activity" records that map directly to Art. 30(1) fields.
Integration points:
Base URL: https://helix-biotech.my.onetrust.com/api/
Authentication: OAuth 2.0 client credentials flow.
import requests
ONETRUST_BASE_URL = "https://helix-biotech.my.onetrust.com/api"
CLIENT_ID = "helix-ropa-integration"
CLIENT_SECRET_ENV = "ONETRUST_CLIENT_SECRET" # Stored in vault
def get_access_token(client_id: str, client_secret: str) -> str:
"""Obtain OAuth 2.0 access token from OneTrust."""
response = requests.post(
f"{ONETRUST_BASE_URL}/auth/oauth/token",
data={
"grant_type": "client_credentials",
"client_id": client_id,
"client_secret": client_secret,
},
headers={"Content-Type": "application/x-www-form-urlencoded"},
)
response.raise_for_status()
return response.json()["access_token"]Fetching processing activities:
def get_processing_activities(token: str, page: int = 0, size: int = 50) -> dict:
"""Retrieve processing activities from OneTrust Data Mapping."""
response = requests.get(
f"{ONETRUST_BASE_URL}/datasubject/v3/processingactivities",
headers={"Authorization": f"Bearer {token}"},
params={"page": page, "size": size},
)
response.raise_for_status()
return response.json()Creating a processing activity:
def create_processing_activity(token: str, activity: dict) -> dict:
"""Create a new processing activity record in OneTrust."""
payload = {
"name": activity["processing_activity"],
"description": activity.get("description", ""),
"organizationId": activity["organization_id"],
"purposes": [
{"name": p, "legalBasis": activity.get("lawful_basis", "")}
for p in activity.get("purposes", [])
],
"dataSubjectCategories": [
{"name": c} for c in activity.get("data_subject_categories", [])
],
"dataElementCategories": [
{"name": c} for c in activity.get("personal_data_categories", [])
],
"retentionPeriod": activity.get("retention_periods", ""),
"securityMeasures": activity.get("security_measures", ""),
}
response = requests.post(
f"{ONETRUST_BASE_URL}/datasubject/v3/processingactivities",
headers={
"Authorization": f"Bearer {token}",
"Content-Type": "application/json",
},
json=payload,
)
response.raise_for_status()
return response.json()| Art. 30(1) Field | OneTrust Field | OneTrust Module |
|---|---|---|
| Controller identity (a) | Organization > Legal Entity | Organization Management |
| Purposes (b) | Processing Activity > Purposes | Data Mapping |
| Data subject categories (c) | Processing Activity > Data Subjects | Data Mapping |
| Personal data categories (c) | Processing Activity > Data Elements | Data Mapping |
| Recipient categories (d) | Processing Activity > Third Parties / Vendors | Data Mapping + Vendorpedia |
| International transfers (e) | Processing Activity > Transfers > Cross Border | Data Mapping |
| Retention periods (f) | Processing Activity > Retention | Data Mapping |
| Security measures (g) | Processing Activity > Security Measures | Data Mapping |
TrustArc (formerly TRUSTe) manages RoPA through its Privacy Operations Manager (PrivacyOps) module. Processing activities are documented through structured assessments that map to Art. 30 fields.
Key integration approach:
Authentication: API key-based.
TRUSTARC_BASE_URL = "https://api.trustarc.com/v1"
def get_processing_records(api_key: str, organization_id: str) -> dict:
"""Retrieve RoPA records from TrustArc PrivacyOps."""
response = requests.get(
f"{TRUSTARC_BASE_URL}/organizations/{organization_id}/processing-records",
headers={
"Authorization": f"Bearer {api_key}",
"Accept": "application/json",
},
)
response.raise_for_status()
return response.json()
def create_assessment(api_key: str, organization_id: str, assessment: dict) -> dict:
"""Create a new processing activity assessment in TrustArc."""
payload = {
"name": assessment["name"],
"type": "PROCESSING_ACTIVITY",
"templateId": assessment.get("template_id", "art30-controller"),
"assignee": assessment.get("owner_email"),
"responses": {
"purposes": assessment.get("purposes", []),
"dataSubjects": assessment.get("data_subject_categories", []),
"dataCategories": assessment.get("personal_data_categories", []),
"recipients": assessment.get("recipient_categories", []),
"transfers": assessment.get("international_transfers", []),
"retention": assessment.get("retention_periods", ""),
"securityMeasures": assessment.get("security_measures", ""),
},
}
response = requests.post(
f"{TRUSTARC_BASE_URL}/organizations/{organization_id}/assessments",
headers={
"Authorization": f"Bearer {api_key}",
"Content-Type": "application/json",
},
json=payload,
)
response.raise_for_status()
return response.json()Collibra is a data intelligence platform with a governance-centric approach to RoPA. Processing activities are modelled as assets within the Collibra Data Catalog, with relationships linking them to data sets, systems, business terms, and governance policies.
Key advantages for RoPA:
COLLIBRA_BASE_URL = "https://helix-biotech.collibra.com/rest/2.0"
def get_processing_activities(token: str) -> dict:
"""Retrieve processing activity assets from Collibra."""
response = requests.get(
f"{COLLIBRA_BASE_URL}/assets",
headers={"Authorization": f"Bearer {token}"},
params={
"typeId": "processing-activity-type-id",
"limit": 100,
"offset": 0,
},
)
response.raise_for_status()
return response.json()
def create_processing_activity_asset(token: str, activity: dict) -> dict:
"""Create a processing activity asset in Collibra."""
payload = {
"name": activity["name"],
"typeId": "processing-activity-type-id",
"domainId": activity["domain_id"],
"statusId": "draft-status-id",
}
response = requests.post(
f"{COLLIBRA_BASE_URL}/assets",
headers={
"Authorization": f"Bearer {token}",
"Content-Type": "application/json",
},
json=payload,
)
response.raise_for_status()
asset_id = response.json()["id"]
# Add attributes for each Art. 30(1) field
attributes = [
{"typeId": "purpose-attr-id", "value": "; ".join(activity.get("purposes", []))},
{"typeId": "retention-attr-id", "value": activity.get("retention_periods", "")},
{"typeId": "security-measures-attr-id", "value": activity.get("security_measures", "")},
]
for attr in attributes:
attr["assetId"] = asset_id
requests.post(
f"{COLLIBRA_BASE_URL}/attributes",
headers={
"Authorization": f"Bearer {token}",
"Content-Type": "application/json",
},
json=attr,
)
return {"asset_id": asset_id, "name": activity["name"]}| Art. 30(1) Field | Collibra Asset/Relation Type | Collibra Domain |
|---|---|---|
| Controller identity (a) | Business Asset > Organisation | Governance |
| Purposes (b) | Attribute on Processing Activity asset | Privacy |
| Data subject categories (c) | Related asset: Data Subject Category | Privacy |
| Personal data categories (c) | Related asset: Data Category (from Business Glossary) | Data Catalog |
| Recipient categories (d) | Relation: "shares data with" > Organisation/System | Privacy |
| International transfers (e) | Relation: "transfers to" > Geography asset | Privacy |
| Retention periods (f) | Attribute on Processing Activity asset | Privacy |
| Security measures (g) | Related asset: Security Control | IT Governance |
DataGrail focuses on real-time data mapping by connecting directly to an organisation's SaaS applications, databases, and internal systems through its integration library (1,800+ connectors). This automated discovery approach populates RoPA fields from live system metadata.
Key integration approach:
DATAGRAIL_BASE_URL = "https://api.datagrail.io/v1"
def get_data_map(api_key: str) -> dict:
"""Retrieve the live data map from DataGrail."""
response = requests.get(
f"{DATAGRAIL_BASE_URL}/data-map",
headers={
"Authorization": f"Bearer {api_key}",
"Accept": "application/json",
},
)
response.raise_for_status()
return response.json()
def get_system_inventory(api_key: str) -> dict:
"""Retrieve connected system inventory."""
response = requests.get(
f"{DATAGRAIL_BASE_URL}/systems",
headers={
"Authorization": f"Bearer {api_key}",
"Accept": "application/json",
},
)
response.raise_for_status()
return response.json()Many organisations begin with spreadsheet-based RoPA and need to migrate to a platform. The migration process:
When multiple privacy tools are in use (e.g., Collibra for data governance and OneTrust for privacy operations), synchronise RoPA data:
| Phase | Duration | Activities | Deliverables |
|---|---|---|---|
| 1. Platform selection | 4 weeks | RFP process, vendor demos, security assessment, DPA negotiation | Selected platform, executed DPA |
| 2. Configuration | 6 weeks | Custom field setup, template creation, workflow configuration, SA template import | Configured platform |
| 3. Integration | 4 weeks | API integration with AD, ServiceNow, Vendorpedia. SSO configuration. | Working integrations |
| 4. Data migration | 3 weeks | Import existing spreadsheet RoPA, validate, establish relationships | Migrated records |
| 5. UAT and training | 2 weeks | User acceptance testing, training for DPO office and processing owners | Trained users |
| 6. Go-live | 1 week | Cut over from spreadsheet, decommission old process | Production RoPA system |
| 7. Optimisation | Ongoing | Automated discovery, advanced reporting, cross-platform sync | Mature RoPA management |
© 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
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/ropa-tool-integration of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Ropa Tool Integration 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 Tool Integration this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Data Exportgustavscirulis/snapgrid | 117 | 1 repos | ~2.9k | Automated safety check: Notes | Custom licence | |
| Transfer Impact Assessment Tia Oliver Schmidt Prietzlawve-ai/awesome-legal-skills | 842 | — | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
gustavscirulis/snapgrid
Generates data export/import infrastructure for JSON, CSV, PDF formats with GDPR data portability, share sheet integration, and file import.
lawve-ai/awesome-legal-skills
GDPR Transfer Impact Assessment for Chapter V transfers under the EDPB Recommendations 01/2020 six-step methodology, the CNIL TIA Guide (January 2025), and EDPB essential guarantees.
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
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…
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
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.
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.
Categories
Integrates Records of Processing Activities with privacy management platforms including OneTrust, TrustArc, Collibra, and DataGrail. Ropa Tool Integration is an agent skill from mukul975/Privacy-Data-Protection-Skills. Integrates Records of Processing Activities with privacy management platforms including OneTrust, TrustArc, Collibra, and DataGrail.
Ropa Tool Integration fits situations like: tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-tool-integration -a claude-code`. Or copy the skill folder (skills/privacy/ropa-tool-integration in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/ropa-tool-integration in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ropa-tool-integration -a codex`. Or copy the skill folder (skills/privacy/ropa-tool-integration in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/ropa-tool-integration in your project. Codex loads it when a task matches its description.
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-tool-integration -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-tool-integration, .gemini/skills/ropa-tool-integration, .github/skills/ropa-tool-integration and .opencode/skills/ropa-tool-integration in your project.
Going by SKILL.md and its folder, Ropa Tool Integration needs Python for the scripts in its folder and credentials named ONETRUST_CLIENT_SECRET. Our summary lists: Python 3; A credential in ONETRUST_CLIENT_SECRET.
SKILL.md names 3 domains. In commands or code: api.trustarc.com, helix-biotech.collibra.com and api.datagrail.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
Ropa Tool Integration 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.
About 4.2k tokens (SKILL.md is roughly 17k 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.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Ropa Tool Integration: Data Export (gustavscirulis/snapgrid, 117 stars), Transfer Impact Assessment Tia Oliver Schmidt Prietz (lawve-ai/awesome-legal-skills, 842 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.
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 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.