Guides the Privacy Threshold Analysis screening process to determine whether a full DPIA is required.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .claude/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .claude/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .agents/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .agents/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .cursor/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .cursor/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/privacy-threshold-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .gemini/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .gemini/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .github/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .github/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills privacy-threshold-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/privacy-threshold-analysis .opencode/skills/privacy-threshold-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "privacy-threshold-analysis" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/privacy-threshold-analysis into .opencode/skills/privacy-threshold-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-threshold-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
privacy-threshold-analysisGuides the Privacy Threshold Analysis screening process to determine whether a full DPIA is required.
Privacy Threshold Analysis is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the Privacy Threshold Analysis screening process to determine whether a full DPIA is required. Provides a quick-screen questionnaire, threshold criteria based on WP248rev.01, escalation triggers, and documentation requirements. Activate when evaluating new processing activities, system changes, or procurement decisions. Keywords: PTA, privacy threshold analysis, DPIA screening, quick-screen, threshold criteria, WP248, escalation triggers.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR and Vendor and procurement management. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Privacy Threshold Analysis loads about 1.9k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 887 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 887 words, ~1,885 tokens.
.claude/skills/privacy-threshold-analysis/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.A Privacy Threshold Analysis (PTA) is a lightweight screening tool used to determine whether a processing activity requires a full DPIA under Art. 35. The PTA functions as a triage mechanism: it applies the WP248rev.01 nine criteria, Art. 35(3) mandatory triggers, and national supervisory authority DPIA lists to quickly classify processing activities into three categories: DPIA required, DPIA recommended, or DPIA not required. Every new processing activity, system change, or procurement of data-processing services should pass through the PTA before implementation.
| Question | Yes/No | If Yes |
|---|---|---|
| A1. Does the processing involve systematic and extensive evaluation of personal aspects based on automated processing (including profiling) on which decisions are based that produce legal effects or similarly significantly affect individuals? | DPIA mandatory — Art. 35(3)(a) | |
| A2. Does the processing involve large-scale processing of special categories of data (Art. 9(1): health, biometric, genetic, racial/ethnic, political, religious, trade union, sexual orientation) or criminal conviction data (Art. 10)? | DPIA mandatory — Art. 35(3)(b) | |
| A3. Does the processing involve systematic monitoring of a publicly accessible area on a large scale (e.g., CCTV in public spaces, Wi-Fi tracking)? | DPIA mandatory — Art. 35(3)(c) | |
| A4. Does the processing appear on the national supervisory authority's DPIA required list (Art. 35(4))? | DPIA mandatory |
If any question in Section A is answered Yes: DPIA is mandatory. Stop. Proceed to full DPIA.
| Question | Criterion | Yes/No |
|---|---|---|
| B1. Does the processing involve evaluation or scoring of individuals (profiling, prediction, credit scoring, behavioural analysis)? | C1 | |
| B2. Does the processing involve automated decision-making that produces legal effects or similarly significant effects on individuals? | C2 | |
| B3. Does the processing involve systematic monitoring of individuals (observation, tracking, surveillance)? | C3 | |
| B4. Does the processing involve sensitive data (Art. 9 special categories) or highly personal data (financial, location, communications)? | C4 | |
| B5. Is the processing carried out on a large scale (number of subjects, volume, geographic scope, duration)? | C5 | |
| B6. Does the processing involve matching or combining datasets from different sources beyond data subject expectations? | C6 | |
| B7. Does the processing involve data concerning vulnerable individuals (children, employees, patients, elderly, disabled, asylum seekers)? | C7 | |
| B8. Does the processing involve innovative use of technology or application of existing technology in a new way? | C8 | |
| B9. Does the processing prevent individuals from exercising a right or using a service or contract? | C9 |
Scoring:
| Question | Yes/No | Impact |
|---|---|---|
| C1. Does the processing involve international transfers to countries without an adequacy decision? | Additional risk factor — TIA required alongside DPIA if applicable | |
| C2. Is this a new processing activity not previously assessed? | New processing should be assessed more conservatively | |
| C3. Has similar processing been subject to enforcement action by any supervisory authority? | Elevated scrutiny — DPIA recommended regardless of criteria count | |
| C4. Does the processing involve real-time data processing or urgent decision-making? | Reduced opportunity for human review — elevated risk |
| Section A Triggers | Section B Criteria | Section C Factors | Determination |
|---|---|---|---|
| Any trigger met | N/A | N/A | DPIA mandatory |
| No trigger met | 2+ criteria | Any | DPIA strongly recommended |
| No trigger met | 1 criterion | 1+ factors | DPIA recommended |
| No trigger met | 1 criterion | 0 factors | DPO consultation recommended |
| No trigger met | 0 criteria | 1+ factors | Document screening; monitor |
| No trigger met | 0 criteria | 0 factors | DPIA not required |
Regardless of the outcome, every PTA must be documented and retained. The documentation must include:
| Field | Content |
|---|---|
| PTA Reference | Unique identifier (PTA-[ORG]-[YEAR]-[SEQ]) |
| Processing Activity Name | Descriptive name of the processing activity |
| Processing Owner | Name and role of the person responsible |
| Date of PTA | Date the screening was completed |
| Section A Responses | Yes/No for each Art. 35(3) question |
| Section B Responses | Yes/No for each WP248 criterion with justification |
| Section C Responses | Yes/No for each additional factor |
| Determination | DPIA mandatory/recommended/not required |
| DPO Sign-Off | DPO name, date, and whether they agree with the determination |
| Next Steps | Full DPIA initiated / Processing approved without DPIA / Deferred pending further information |
When a PTA determines that a DPIA is required:
When a PTA determines that a DPIA is recommended but not mandatory:
© 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
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/privacy-threshold-analysis of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Privacy Threshold Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Privacy Threshold Analysis this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Regulatory Deal Card Generator Patrick Munrolawve-ai/awesome-legal-skills | 842 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Tech Contract Negotiation Patrick Munrolawve-ai/awesome-legal-skills | 842 | — | ~4.9k | Automated safety check: Pass | AGPL-3.0 | |
| AI Governance Reviewer Carl Ditzlerlawve-ai/awesome-legal-skills | 842 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Operational Designmagnus919/hermes-profiles | 282 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Operational Designmagnus919/agent-skills | 116 | — | ~1.4k | Automated safety check: Pass | MIT |
lawve-ai/awesome-legal-skills
Generates standalone interactive HTML "deal cards" that translate complex regulations into negotiation-ready reference tools, systematically distinguishing mandatory obligations from negotiable…
lawve-ai/awesome-legal-skills
Systematic contract negotiation strategies for technology services agreements with German/EU law specificity.
lawve-ai/awesome-legal-skills
A skill your agent uses when the user wants an AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk review of an internal AI use case, an AI product feature, an LLM workflow…
magnus919/hermes-profiles
COO methodology for process design, organizational scaling, operational metrics, compliance and audit, vendor management, and team topology.
magnus919/agent-skills
Design and improve operational processes, controls, metrics, vendors, and scaling models through bounded pilots and evidence.
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Categories
Guides the Privacy Threshold Analysis screening process to determine whether a full DPIA is required. Privacy Threshold Analysis is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the Privacy Threshold Analysis screening process to determine whether a full DPIA is required.
Privacy Threshold Analysis fits situations like: tasks that involve Privacy and GDPR; tasks that involve Vendor and procurement management.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a claude-code`. Or copy the skill folder (skills/privacy/privacy-threshold-analysis in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/privacy-threshold-analysis in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a codex`. Or copy the skill folder (skills/privacy/privacy-threshold-analysis in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/privacy-threshold-analysis in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill privacy-threshold-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/privacy-threshold-analysis, .gemini/skills/privacy-threshold-analysis, .github/skills/privacy-threshold-analysis and .opencode/skills/privacy-threshold-analysis in your project.
Going by SKILL.md and its folder, Privacy Threshold Analysis needs Python for the scripts in its folder. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Privacy Threshold Analysis is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 322 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Privacy Threshold Analysis: Regulatory Deal Card Generator Patrick Munro (lawve-ai/awesome-legal-skills, 842 stars), Tech Contract Negotiation Patrick Munro (lawve-ai/awesome-legal-skills, 842 stars), AI Governance Reviewer Carl Ditzler (lawve-ai/awesome-legal-skills, 842 stars) and Operational Design (magnus919/hermes-profiles, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
