Token导航 LogoToken导航TokenDH.com
运维和基础设施只读github未标认证来源可访问许可证需确认审计通过

dpia-assessmentDPIA 评估

Agent Skill

dpia-assessment 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

470

周安装

19

GitHub Stars

103

下载量

147
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:dpia-assessment(DPIA 评估)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/dpia-assessment
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill dpia-assessment
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill dpia-assessment

简介

使用分发生成摘要(--register

  • 必需,--json
  • 可选)
  • art36-检查
  • 检查艺术。 36 咨询要求(--注册
  • 必填)
  • 每周安装量
  • 19
  • 存储库
  • 博尔盖/克劳德-技能
  • GitHub 之星
  • 103
  • 第一次看到
  • 1 天前
  • 安全审计
  • Gen Agent Trust Hub 通行证
  • 套接字通行证
  • 斯尼克通行证

SKILL.md

⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

DPIA Assessment

GDPR Article 35 Data Protection Impact Assessment tooling. Evaluates whether a DPIA is required, manages risk registers with mitigation tracking, and generates documentation meeting supervisory authority expectations.


Table of Contents

- DPIA Threshold Checker - DPIA Risk Register


Tools

DPIA Threshold Checker

Evaluates whether a DPIA is required based on processing activity description. Checks Art. 35(3) mandatory triggers and 9 EDPB criteria.

# Check a processing activity (interactive prompts)
python scripts/dpia_threshold_checker.py --activity "AI-based credit scoring using financial and behavioral data of retail banking customers across EU"

# Check from JSON description
python scripts/dpia_threshold_checker.py --input processing.json

# JSON output
python scripts/dpia_threshold_checker.py --activity "Employee monitoring via CCTV in workplace" --json

# Generate blank input template
python scripts/dpia_threshold_checker.py --template > processing.json

Checks performed:

  • Art. 35(3)(a): Automated decision-making with legal/significant effect
  • Art. 35(3)(b): Large-scale processing of special category data (Art. 9) or criminal data (Art. 10)
  • Art. 35(3)(c): Systematic monitoring of publicly accessible area on large scale
  • 9 EDPB criteria from WP 248 rev.01 with two-criterion presumption rule

Output:

  • Verdict: Required / Recommended / Not Required
  • Art. 35(3) trigger matches
  • EDPB criteria scores with reasoning
  • Two-criterion presumption analysis

DPIA Risk Register

Manages a DPIA risk register in JSON format. Add risks, apply mitigations, and calculate residual risk.

# Initialize a new risk register
python scripts/dpia_risk_register.py init --output dpia_risks.json

# Add a risk
python scripts/dpia_risk_register.py add --register dpia_risks.json \
  --description "Unauthorized access to profiling data" \
  --rights-category "right-to-privacy" \
  --likelihood 4 --severity 3

# Add mitigation to a risk
python scripts/dpia_risk_register.py mitigate --register dpia_risks.json \
  --risk-id 1 --measure "Implement role-based access control" \
  --likelihood-reduction 2 --severity-reduction 1

# View risk register table
python scripts/dpia_risk_register.py view --register dpia_risks.json

# Generate residual risk summary
python scripts/dpia_risk_register.py summary --register dpia_risks.json --json

# Check Art. 36 consultation threshold
python scripts/dpia_risk_register.py art36-check --register dpia_risks.json

Rights categories: right-to-privacy, non-discrimination, freedom-of-expression, right-to-information, right-to-not-be-subject-to-automated-decisions, right-to-physical-safety


Reference Guides

EDPB Criteria

references/edpb_criteria.md

Complete EDPB 9-criteria assessment framework:

  • Each criterion with description, indicators, and scoring guidance
  • Art. 35(3) mandatory triggers
  • Two-criterion presumption rule (WP 248 rev.01)
  • Multi-jurisdictional DPIA analysis
  • National blacklist/whitelist overview (DE, FR, IE, BE, NL, IT, PL)

Risk Scoring Methodology

references/risk_scoring_methodology.md

DPIA risk scoring from the data subject perspective:

  • Likelihood and severity scales (1-5)
  • Rights categories per Recital 75
  • Risk level thresholds (Low/Medium/High/Very High)
  • Mitigation effectiveness scoring
  • Residual risk calculation
  • Art. 36 consultation triggers
  • Risk catalog: 20+ common DPIA risks

Workflows

Workflow 1: Full DPIA Assessment

Step 1: Threshold check — determine if DPIA required
        → python scripts/dpia_threshold_checker.py --activity "description"

Step 2: If Required or Recommended, describe the processing
        → Document purpose, legal basis, data categories, recipients, retention

Step 3: Assess necessity and proportionality
        → Confirm lawful basis (Art. 6, cumulative with Art. 9 if special categories)
        → Verify purpose limitation, data minimization, storage limitation

Step 4: Identify risks from data subject perspective
        → python scripts/dpia_risk_register.py init --output dpia_risks.json
        → Add risks using references/risk_scoring_methodology.md catalog

Step 5: Apply mitigations and calculate residual risk
        → python scripts/dpia_risk_register.py mitigate --register dpia_risks.json ...

Step 6: Check Art. 36 consultation requirement
        → python scripts/dpia_risk_register.py art36-check --register dpia_risks.json

Step 7: Document and review
        → python scripts/dpia_risk_register.py summary --register dpia_risks.json

Workflow 2: Quick Threshold Assessment

Step 1: Describe the processing activity
        → python scripts/dpia_threshold_checker.py --template > processing.json
        → Fill in processing details

Step 2: Run threshold check
        → python scripts/dpia_threshold_checker.py --input processing.json --json

Step 3: Review verdict and reasoning
        → Required: proceed to full DPIA (Workflow 1)
        → Recommended: proceed unless strong justification to skip (document)
        → Not Required: document the assessment and rationale

Workflow 3: AI System DPIA

Step 1: Classify AI system (EU AI Act risk level if applicable)
        → Map to DPIA triggers (automated decision-making, profiling, scoring)

Step 2: Run threshold check with AI-specific indicators
        → python scripts/dpia_threshold_checker.py --activity "AI system description"

Step 3: Dual-phase risk analysis (EDPB Opinion 28/2024)
        → Phase 1: Training data risks (collection, bias, consent)
        → Phase 2: Inference risks (decisions, profiling, transparency)

Step 4: Assess from data subject perspective
        → Add risks covering both training and inference phases
        → Include algorithmic bias, lack of transparency, unfair outcomes

Step 5: Apply mitigations specific to AI
        → Explainability measures, human oversight, bias testing
        → Document FRIA distinction per EU AI Act Art. 27 if applicable

Legal Precision Points

12 points of legal precision that distinguish expert-level DPIA work.

#PointDetail
1Art. 35(3) absolute triggersThree mandatory triggers require DPIA regardless of other analysis: (a) automated decisions with legal effect, (b) large-scale special category/criminal data, (c) systematic public area monitoring
2Two-criterion presumptionIf 2 or more of the 9 EDPB criteria are met, DPIA is presumptively required (WP 248 rev.01). Can rebut only with documented justification
3Art. 9 cumulative with Art. 6Special category data requires BOTH an Art. 6 lawful basis AND an Art. 9(2) exception. Neither alone is sufficient
4Large scale four-factor testAssess: (a) number of data subjects, (b) volume of data, (c) geographic extent, (d) duration/permanence. No fixed numeric threshold
5National blacklists additiveSA-published lists of processing operations requiring DPIA add to (not replace) Art. 35(3) and EDPB criteria
6Multi-jurisdictional checkingIf processing spans multiple member states, check each SA's blacklist. Most restrictive list applies
7Pre-processing obligationDPIA must be completed BEFORE processing begins (Art. 35(1)). Retroactive DPIAs do not satisfy the requirement
8AI dual-phase analysisEDPB Opinion 28/2024: AI systems require separate risk analysis for training phase and inference/deployment phase
9Art. 36 sequentialPrior consultation with SA (Art. 36) is triggered only AFTER DPIA is completed and residual risk remains high. Cannot skip the DPIA
10Pseudonymization nuanceEDPB Guidelines 01/2025: pseudonymization reduces risk but does not eliminate DPIA requirement. Still personal data
11Data subject perspectiveAll risks must be assessed from the data subject's perspective (Recital 75), not the controller's business perspective
12AI Act FRIA distinctionEU AI Act Art. 27 requires Fundamental Rights Impact Assessment (FRIA) for high-risk AI. FRIA is separate from GDPR DPIA — both may be required

Output Formats

Threshold Verdict

VERDICT: DPIA REQUIRED
Reason: Art. 35(3)(a) trigger matched (automated decision-making with legal effect)
        + 4 of 9 EDPB criteria met (two-criterion presumption applies)
Matched triggers: automated_decision_making, evaluation_scoring, sensitive_data, large_scale

Risk Register Table

IDDescriptionRights CategoryLSScoreLevelMitigationResidual LResidual SResidual ScoreResidual Level
1Unauthorized profilingRight to privacy4312HighRBAC + encryption224Low
2Discriminatory outcomesNon-discrimination3412HighBias testing + human review236Medium

Residual Risk Overview

Total risks: 8
Mitigated: 6 (75%)
Residual risk distribution:
  Low:       3 (37.5%)
  Medium:    3 (37.5%)
  High:      2 (25.0%)
  Very High: 0 (0.0%)

Art. 36 consultation: NOT TRIGGERED (no Very High residual risks)

Troubleshooting

ProblemPossible CauseResolution
Threshold checker says "Not Required" but processing feels riskyActivity description too vague or missing key detailsProvide more specific description including data types, scale, automation level, and data subject categories
Two-criterion presumption triggered but controller disagreesController must document justification for rebutting presumptionDocument specific reasons why DPIA is not needed despite criteria match; SA may challenge this
Risk register shows High residual risk after mitigationsMitigations insufficient or not properly scoredReview mitigation effectiveness; consider additional controls; if residual risk remains high, Art. 36 consultation required
Multi-jurisdictional check produces conflicting resultsDifferent SAs have different blacklists and thresholdsApply the most restrictive requirement; document the analysis for each jurisdiction
AI system DPIA unclear on training vs. inference risksTraining and inference phases have different risk profilesSeparate the analysis per EDPB Opinion 28/2024; assess each phase independently then combine
Art. 36 check unclear on thresholdResidual risk near the boundary between High and Very HighDocument the borderline assessment; consider voluntary consultation as good practice

Success Criteria

  • All high-risk processing activities assessed -- threshold check completed before processing begins, with documented verdict and reasoning
  • Risk register complete with mitigations -- every identified risk has likelihood, severity, rights category, and at least one mitigation measure
  • Residual risk acceptable or Art. 36 consultation initiated -- no unaddressed Very High residual risks
  • Documentation meets SA expectations -- assessment follows Art. 35(7) requirements: systematic description, necessity/proportionality, risks, mitigations
  • EDPB criteria properly applied -- two-criterion presumption correctly evaluated with documented reasoning

Scope & Limitations

In Scope:

  • DPIA threshold assessment against Art. 35(3) triggers and EDPB criteria
  • Risk register management with mitigation tracking and residual risk calculation
  • Art. 36 prior consultation threshold assessment
  • Multi-jurisdictional blacklist awareness (DE, FR, IE, BE, NL, IT, PL)
  • AI system dual-phase DPIA analysis guidance
  • Data subject perspective risk assessment per Recital 75

Out of Scope:

  • Legal advice on lawful basis selection (Art. 6) or Art. 9(2) exception applicability
  • Supervisory authority submission or interaction
  • Technical implementation of mitigations (encryption, access control)
  • DPO appointment or consultation logistics
  • National blacklist exhaustive coverage beyond listed jurisdictions
  • EU AI Act conformity assessment (see eu-ai-act-specialist)

Anti-Patterns

  • Conducting DPIA after processing has started -- Art. 35(1) requires DPIA before processing begins; retroactive DPIAs do not satisfy the legal obligation and create enforcement exposure
  • Assessing risk from the controller's perspective -- DPIA risks must be evaluated from the data subject's perspective per Recital 75; business impact is irrelevant to this analysis; a breach that is minor for the company may be catastrophic for affected individuals
  • Treating pseudonymization as eliminating DPIA need -- pseudonymized data remains personal data under GDPR (Recital 26); pseudonymization is a mitigation that reduces risk scores, not a basis for skipping the DPIA entirely
  • Skipping Art. 36 consultation when residual risk is high -- if residual risk remains Very High after mitigations, prior consultation with the supervisory authority is mandatory, not optional
  • Conflating DPIA with FRIA -- the EU AI Act's Fundamental Rights Impact Assessment (Art. 27) is a separate obligation from GDPR DPIA; completing one does not satisfy the other; both may be required for AI systems processing personal data

Tool Reference

dpia_threshold_checker.py

Evaluates whether a DPIA is required based on Art. 35(3) triggers and EDPB criteria.

FlagRequiredDescription
--activity <text>Yes (unless --input or --template)Processing activity description
--input <file>Yes (unless --activity)Path to JSON processing description
--templateNoGenerate blank input template
--jsonNoOutput in JSON format

dpia_risk_register.py

Manages DPIA risk register with mitigation tracking and residual risk calculation.

SubcommandDescription
initCreate new empty risk register (--output required)
addAdd risk (--register, --description, --rights-category, --likelihood, --severity required)
mitigateAdd mitigation (--register, --risk-id, --measure, --likelihood-reduction, --severity-reduction required)
viewDisplay risk register table (--register required)
summaryGenerate summary with distribution (--register required, --json optional)
art36-checkCheck Art. 36 consultation requirement (--register required)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.53%
按下载量换算57

Claude

29.41%
按下载量换算43

Cursor

18.18%
按下载量换算27

Gemini CLI

9.09%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills