SKILLEMALL.ai

CD dpia-sentinel-oliver-schmidt-prietz

GDPR Data Protection Impact Assessment (DPIA) guidance under Article 35 GDPR, EDPB Guidelines WP 248 rev.01, EDPB Opinion 28/2024 (AI), and national SA blacklists/whitelists. Triggers: "DPIA", "DSFA", "Datenschutz-Folgenabschätzung", "impact assessment", "Art. 35", "do I need a DPIA", descriptions of new high-risk processing (profiling, AI, biometrics, large-scale monitoring, special category data), Art. 36 prior consultation questions, national blacklist/whitelist queries.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 21 files body ≈ 2 459 tokens Open the sourcegithub.com↗ analyzed 90 min ago

GDPR Data Protection Impact Assessment (DPIA) guidance under Article 35 GDPR, EDPB Guidelines WP 248 rev.01, EDPB Opinion 28/2024 (AI), and national SA…

As a process D 39/100 · Unfinished process — References files that are not bundled: references/edpb-2026-template-v1.docx, references/dpia-custom-template-v1.docx

AnalyzerWordLegaltype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
95
Quality 40%
72
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: references/edpb-2026-template-v1.docx, references/dpia-custom-template-v1.docx
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

✓ No critical or high findings

Medium and low: 5
  • low Risky intent intent-offensive-security references/edpb-2026-explainer.md:72
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | External attacks | Phishing, ransomware |
  • low Risky intent intent-offensive-security references/edpb-2026-template.md:671
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - External attacks (phishing, ransomware)
  • low Risky intent intent-offensive-security references/scoring.md:33
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Regular security testing, penetration testing, red teaming
  • low Risky intent intent-offensive-security references/scoring.md:141
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    3. **Data disappearance** — deletion, ransomware, system failure, retention expiry error
  • low Risky intent intent-offensive-security references/scoring.md:143
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Sources: software bugs, misconfigurations, wrong access rights, operational errors (wrong recipient, wrong dataset, forgotten de-provisioning), unpatched vulnerabilities, insider abuse, external attac

Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/edpb-2026-template-v1.docx
  • warning missing-ref reference to a missing file: references/dpia-custom-template-v1.docx

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: references/edpb-2026-template-v1.docx, references/dpia-custom-template-v1.docx
  • 0Tools and files. 2 referenced file(s) missing: references/edpb-2026-template-v1.docx, references/dpia-custom-template-v1.docx
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 28 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2459 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • medium 8 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +4No input/output examples
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 478: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 28 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (7 of 9)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.