Ropa Dpia Linkage

What it does

When your agent uses it

• Lawful basis documentation
• Tasks that involve Privacy and GDPR

Example prompts

• “Use the ropa-dpia-linkage skill to link RoPA entries to Data Protection Impact Assessments and lawful basis assessments”
• “/ropa-dpia-linkage”

Requirements

• Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1For every DPIA in the register, verify the linked RoPA entry exists and is active.
2. 2For every RoPA entry marked "DPIA required = Yes," verify a DPIA reference exists and the DPIA status is not "Expired" or "Rejected."
3. 3For every RoPA entry with a lawful basis reference, verify the assessment is current (reviewed within 24 months or upon change).
4. 4Flag any orphaned DPIAs (no linked RoPA entry) or orphaned RoPA entries (marked high-risk with no DPIA).

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 Dpia Linkage loads about 3k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 1,081 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~89

When it runs · the whole SKILL.md, loaded when a task matches

~3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~5.4k

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

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,081 words, ~3,040 tokens.

name

ropa-dpia-linkage

description

Links RoPA entries to Data Protection Impact Assessments and lawful basis assessments. Covers cross-reference systems, dependency tracking, and update cascade triggers between RoPA, DPIA register, and lawful basis documentation. Activate for RoPA-DPIA link, cross-reference, dependency tracking, impact assessment linkage, cascade updates.

license

Apache-2.0

metadata.author

mukul975

metadata.version

1.0

metadata.domain

privacy

metadata.subdomain

records-of-processing

metadata.tags

gdpr, ropa, dpia, article-35, lawful-basis, cross-reference, dependency, cascade

┌──────────────────────┐       ┌──────────────────────┐
│     RoPA Register    │◄─────►│    DPIA Register      │
│                      │       │                       │
│  RPA-001: Payroll    │       │  DPIA-2024-PAY-001   │
│  RPA-002: Clinical   │◄─────►│  DPIA-2024-ONC-04   │
│  RPA-003: Analytics  │       │  (No DPIA required)  │
│  ...                 │       │  ...                  │
└──────────┬───────────┘       └───────────┬───────────┘
           │                               │
           │       ┌───────────────────┐   │
           └──────►│  Lawful Basis     │◄──┘
                   │  Register         │
                   │                   │
                   │  LIA-2025-GA4-001│
                   │  CON-2024-CT-04  │
                   │  ...             │
                   └───────────────────┘

RoPA Change Detected
    │
    ├── Is this entry linked to a DPIA?
    │   ├── Yes → Flag DPIA for review (Art. 35(11))
    │   └── No → Does the change make the processing high-risk?
    │       ├── Yes → Trigger DPIA necessity assessment
    │       └── No → No DPIA action required
    │
    └── Does this change affect the lawful basis?
        ├── Yes → Flag lawful basis assessment for review
        └── No → No lawful basis action required

DPIA Change Detected
    │
    ├── Does the DPIA outcome change risk mitigation measures?
    │   └── Yes → Update RoPA security measures field
    │
    ├── Does the DPIA outcome change processing scope?
    │   └── Yes → Update RoPA purpose, data categories, or recipients
    │
    └── Does the DPIA outcome affect lawful basis assessment?
        └── Yes → Flag lawful basis for review

Lawful Basis Change Detected
    │
    ├── Update RoPA lawful basis field
    └── Review DPIA assumptions about lawful basis

{
    "record_id": "RPA-002",
    "processing_activity": "Clinical trial participant data management",
    "dpia_required": true,
    "dpia_reference": "DPIA-2024-ONC-04",
    "dpia_status": "Approved",
    "dpia_approval_date": "2024-02-28",
    "dpia_next_review_date": "2025-02-28",
    "lawful_basis_reference": "CON-2024-CT-04",
    "lawful_basis_type": "Art. 6(1)(a) consent + Art. 9(2)(a) explicit consent",
    "lawful_basis_assessment_date": "2024-01-15",
    "art9_condition": "Art. 9(2)(a) — explicit consent per ICH E6(R2) informed consent process",
    "linked_lia": null,
    "prior_consultation_required": false,
    "prior_consultation_reference": null
}

© 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-dpia-linkage 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