Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lawve-ai/dpa-art-28-oliver-schmidt-prietz
Review, draft, or redline a Data Processing Agreement (DPA / Auftragsverarbeitungsvertrag / AVV) under Art. 28 GDPR, or prepare a Joint Controller Arrangement under Art. 26 GDPR. Supports bilingual output (DE/EN), both controller- and processor-side perspectives, and two review depths — quick (Art. 28(3)(a)–(h) coverage) and negotiation-grade (clause-by-clause risk scoring).
Passed 15 of 22 test cases with the skill, and 9 of 22 without it.
and 3 more in the full report
6 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We received a counterparty DPA draft and need to produce a marked-up redline. What exact formatting convention must be used for additions and deletions, and how must clause numbering be handled relative to the counterparty draft?
| Checked | Without skill | With skill |
|---|---|---|
| Formats additions in bold font and deletions in strikethrough font. | Missed | Passed |
| Retains the counterparty draft's exact clause numbering scheme for traceability. | Passed | Passed |
The instructions your model reads when the skill loads.
This skill governs all work on controller–processor contracts (Art. 28 GDPR) and joint-controller arrangements (Art. 26 GDPR). It produces:
Before doing anything else, classify the request into ONE of these modes:
| Mode | Trigger pattern | Workflow file |
|---|---|---|
REVIEW_QUICK | "Is this DPA compliant?", "Art. 28(3)(a)–(h) check", short turnaround, sign/no-sign decision needed | workflows/review-quick.md |
REVIEW_NEG | "Review this for negotiation", "give me redline points", "what should we push back on", deeper diligence | workflows/review-negotiation.md |
DRAFT | "Draft a DPA", "create an AVV", "we need a processor agreement for [X]", greenfield | workflows/draft.md |
REDLINE | Counterparty has sent a DPA, user wants tracked-changes / counter-proposals | workflows/redline.md |
JOINT_CONTROLLER | "Art. 26", "joint controller", "JCA", or roles screen reveals JC not processor relationship | workflows/joint-controller.md |
If unclear, ASK. Do not guess between REVIEW_QUICK and REVIEW_NEG — the depth difference is ~30 min vs ~2–3 h of analytical work, and the output structure is materially different.
Mode flips during the work are allowed and expected. If a REVIEW_QUICK reveals issues serious enough that the user needs negotiation guidance, surface this and offer to escalate to REVIEW_NEG. If a roles screen during DRAFT or REVIEW_* reveals the parties are actually joint controllers, stop and switch to JOINT_CONTROLLER.
Regardless of mode:
references/art26-joint-controller.md BEFORE proceeding.references/tier-selection.md and walk the decision tree if the user has not pre-selected. For REVIEW modes, the tier is whatever the source document is — identify it and continue.references/sccs-module-guide.md and flag SCC requirements early. Note: 2021/915 (Tiers 2/3) does not by itself cover transfers — pair with 2021/914 if needed.test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.