agentleFS
zsrrica-pixelzsrrica-pixel/gdpr-compliance-plugin/skills/dpa-review/SKILL.md

dpa-review

Skill1 starsChanged 42 days agoMITView on GitHub

Review a Data Processing Agreement or processor contract against GDPR Art. 28. Use when the user shares a DPA, vendor contract, or asks whether a processor agreement is adequate.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. anthropics/claude-for-legal★ 9.5ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If roles are not stated, state your assumption.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DPA / processor contract review

Establish roles first (controller, processor, or joint controllers; Art. 26 applies to the latter). Then mark each Art. 28(3) element Present / Weak / Missing, quoting the clause:

  1. Subject matter, duration, nature and purpose of processing
  2. Types of personal data and categories of data subjects
  3. Processing only on documented controller instructions (incl. transfers)
  4. Confidentiality commitments for personnel
  5. Security measures (Art. 32), ideally in an annex
  6. Sub-processors: prior authorisation (general or specific), flow-down of the same obligations, list and change notice with right to object
  7. Assistance with data subject requests
  8. Assistance with Arts. 32-36 (security, breach notice, DPIAs); breach notice to controller "without undue delay" with a concrete timeframe
  9. Deletion or return of data at end of services
  10. Audit and information rights

Also check: international transfer mechanism (SCCs module, adequacy, DPF) and transfer impact assessment, liability caps that undercut data protection duties, and consistency between the DPA and the main agreement (order of precedence).

Output a findings table, a risk rating, and proposed redline language for each gap. Working draft, not legal advice.

Rubric and format

  • Present: clause meets Art. 28 as written. Weak: clause exists but is vague or sets a non-compliant term (e.g. a 10-business-day breach notice). Missing: no clause.
  • Findings table columns: #, element, status, clause quote/evidence. Put the "also check" items in a second table.
  • Risk rating: High (any core Art. 28(3) element Missing, or no transfer mechanism), Medium (only Weak items), Low (all Present, minor wording).
  • If roles are not stated, state your assumption. If the main agreement is not supplied, say precedence could not be checked.
  • Redline benchmarks are suggestions: breach notice 24-72h from awareness, 30 days' sub-processor notice, deletion within 30 days. Mark them as negotiable positions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.