C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guides the Art. An agent skill from mukul975/Privacy-Data-Protection-Skills.
Install Prior Consultation Dpa
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill prior-consultation-dpa -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills prior-consultation-dpa --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/prior-consultation-dpa .claude/skills/prior-consultation-dpa && 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 "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .claude/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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/prior-consultation-dpaType 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 prior-consultation-dpa -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills prior-consultation-dpa --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/prior-consultation-dpa .agents/skills/prior-consultation-dpa && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .agents/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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 prior-consultation-dpa -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills prior-consultation-dpa --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/prior-consultation-dpa .cursor/skills/prior-consultation-dpa && 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 "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .cursor/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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/prior-consultation-dpa--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 prior-consultation-dpa -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills prior-consultation-dpa --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/prior-consultation-dpa .gemini/skills/prior-consultation-dpa && 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 "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .gemini/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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 prior-consultation-dpaInstalls 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 prior-consultation-dpa -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/prior-consultation-dpa .github/skills/prior-consultation-dpa && 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 "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .github/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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 prior-consultation-dpa -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 prior-consultation-dpa --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/prior-consultation-dpa .opencode/skills/prior-consultation-dpa && 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 "prior-consultation-dpa" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/prior-consultation-dpa into .opencode/skills/prior-consultation-dpa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prior-consultation-dpa", 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.
Facts
- Skill name
prior-consultation-dpa- GitHub stars
- 301
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,143 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides the Art. An agent skill from mukul975/Privacy-Data-Protection-Skills.
- Works in 5 steps: Preparation (Weeks 1-2) → Submission (Week 3) → Supervisory Authority Review Period… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, When Prior Consultation Is…, Art. 36(3) Required… and Consultation Process, plus 3 more sections
- Runs Python scripts from its folder
What it does
Prior Consultation Dpa is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the Art. 36 prior consultation process when a DPIA indicates high residual risk that cannot be mitigated. Covers required documentation per Art. 36(3), the 8-week DPA response timeline, outcome management, and interaction protocols with supervisory authorities. Keywords: prior consultation, Art. 36, supervisory authority, DPA, high residual risk, DPIA escalation, consultation documentation.
Its SKILL.md is about 2.4k 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. 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.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the prior-consultation-dpa skill to guide the Art. An agent skill from mukul975/Privacy-Data-Protection-Skills”
- “/prior-consultation-dpa”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Prior Consultation Dpa loads about 2.4k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 1,143 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,143 words, ~2,391 tokens.
Download SKILL.mdSave it as
.claude/skills/prior-consultation-dpa/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- prior-consultation-dpa
- description
- Guides the Art. 36 prior consultation process when a DPIA indicates high residual risk that cannot be mitigated. Covers required documentation per Art. 36(3), the 8-week DPA response timeline, outcome management, and interaction protocols with supervisory authorities. Keywords: prior consultation, Art. 36, supervisory authority, DPA, high residual risk, DPIA escalation, consultation documentation.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-impact-assessment
- metadata.tags
- prior-consultation, art-36, supervisory-authority, dpa, dpia-escalation
Conducting Prior Consultation with Supervisory Authority
Overview
Article 36(1) requires the controller to consult the supervisory authority prior to processing where a DPIA under Art. 35 indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk. Prior consultation is the final safety net when a DPIA reveals risks that cannot be adequately mitigated through technical, organisational, or contractual measures. The supervisory authority has up to 8 weeks (extendable by 6 weeks) to provide written advice. Processing must not commence until the supervisory authority's response is received and addressed.
When Prior Consultation Is Required
Art. 36(1) Trigger
Prior consultation is mandatory when:
- A DPIA has been conducted under Art. 35
- The DPIA identifies that processing would result in high risk
- The controller cannot sufficiently mitigate the risk through available measures
- Residual risk remains High or Very High despite all reasonable mitigations
Residual Risk Assessment
| Residual Risk Level | Action |
|---|---|
| Low | No prior consultation needed. Processing may proceed. |
| Medium | No prior consultation required, but DPO should document the acceptance rationale. |
| High | Prior consultation recommended. Processing should not proceed without SA review. |
| Very High | Prior consultation mandatory under Art. 36(1). Processing must not proceed. |
Practical Examples Triggering Prior Consultation
- Large-scale biometric identification in publicly accessible areas where encryption with exporter-held key is not feasible
- AI system making automated decisions about access to essential services (credit, insurance, healthcare) where residual discrimination risk cannot be fully eliminated
- Processing of genetic data for a novel purpose where no existing Art. 9(2) exemption clearly applies
- Employee monitoring system where proportionality concerns remain despite all mitigations
- International transfer to a country with Very High government access risk where the processing requires clear-text data access
Art. 36(3) Required Documentation
The controller must provide the supervisory authority with the following information:
| Document | Content | Art. 36(3) Reference |
|---|---|---|
| DPIA report | Complete DPIA per Art. 35(7) including systematic description, necessity/proportionality, risk assessment, and mitigation measures | Art. 36(3)(a) — implicit |
| Controller and processor responsibilities | Clear documentation of which entity is responsible for which processing operations and security measures | Art. 36(3)(a) |
| Measures and safeguards | All technical, organisational, and contractual measures implemented to protect data subjects | Art. 36(3)(b) |
| DPO contact details | Contact details of the Data Protection Officer | Art. 36(3)(c) |
| Additional information requested | Any further information the supervisory authority requests during the consultation | Art. 36(3)(d) |
Supplementary Documentation (Best Practice)
| Document | Purpose |
|---|---|
| Executive summary | 1-2 page summary of the processing, identified risks, and reasons for prior consultation |
| Data flow diagram | Visual representation of personal data flows through the processing |
| Risk register | Detailed risk register with inherent and residual risk levels |
| Mitigation measures schedule | Implementation status and timeline for all mitigations |
| DPO advice letter | Written DPO advice per Art. 35(2) and whether it was followed |
| Legitimate interest assessment | If processing relies on Art. 6(1)(f), the documented LIA |
| Art. 35(9) consultation evidence | Documentation of data subject views sought |
Consultation Process
Step 1: Preparation (Weeks 1-2)
- DPO confirms that prior consultation is required based on DPIA residual risk assessment.
- Processing owner compiles the Art. 36(3) documentation package.
- DPO reviews the package for completeness and accuracy.
- Legal counsel reviews for legal accuracy and strategic considerations.
- Senior management is briefed on the prior consultation and its implications (processing pause).
Step 2: Submission (Week 3)
- Identify the competent supervisory authority:
- Lead SA under one-stop-shop mechanism (Art. 56) for cross-border processing
- Local SA for purely national processing
- Submit the consultation package through the SA's designated channel (online portal, registered mail, or both per SA requirements).
- Confirm receipt and obtain a case reference number.
- Document the submission date — this starts the 8-week clock.
Step 3: Supervisory Authority Review Period (Weeks 3-11)
Art. 36(2) timeline:
- Standard period: Up to 8 weeks from receipt of the complete consultation request
- Extension: The SA may extend the period by up to 6 weeks for complex cases, with notification to the controller within the first month
- Total maximum: 14 weeks (8 + 6)
During this period:
- The SA may request additional information under Art. 36(3)(d). The 8-week clock pauses until the information is provided.
- The DPO serves as the point of contact for SA communications.
- Processing must not commence during the consultation period.
- The controller should continue implementing mitigation measures in preparation.
Show full SKILL.md (424 more words)Show less
Step 4: Outcome Management
| SA Response | Controller Action |
|---|---|
| Written advice with no concerns | Document the SA's response. Proceed with processing. Update DPIA with SA clearance. |
| Written advice with recommendations | Implement the SA's recommendations. Update DPIA. Proceed with processing once recommendations are addressed. |
| Written advice indicating GDPR infringement | Do not proceed with processing as described. Review processing design to address SA concerns. Consider re-submission after modifications. |
| No response within the statutory period | SA silence does not constitute approval. The controller bears responsibility for demonstrating compliance. Proceed with caution, documenting the SA's non-response. |
| Request for more information | Provide the requested information promptly. The clock pauses. |
Step 5: Post-Consultation
- Document the entire consultation process and outcome in the DPIA register.
- Update the DPIA with any SA recommendations or requirements.
- If processing proceeds, implement all SA-recommended measures.
- Schedule an accelerated DPIA review (6 months post-processing commencement).
- Maintain the consultation documentation for supervisory authority inspection.
National Supervisory Authority Consultation Procedures
| SA | Submission Method | Specific Requirements |
|---|---|---|
| ICO (UK) | Online consultation request form | Include DPIA, data flow diagram, DPO contact, description of why risk cannot be mitigated |
| CNIL (France) | Online portal (teleservice.cnil.fr) | DPIA in CNIL format; French language required |
| BfDI (Germany) | Written submission to the competent state or federal DPA | German language; DPIA must reference BDSG provisions |
| Garante (Italy) | PEC (certified email) | Italian language; include DPIA, processor agreements, security measures documentation |
| AEPD (Spain) | Sede Electronica portal | Spanish language; include DPIA and all supporting documentation |
| DPC Ireland | Online submission through DPC website | English language; include DPIA and all Art. 36(3) documentation |
Common Prior Consultation Mistakes
- Consulting too early: Submitting before completing the DPIA and implementing all feasible mitigations. The SA expects to see that all reasonable measures have been taken.
- Consulting too late: Beginning processing before the SA responds. Processing must not start during the consultation period.
- Incomplete documentation: Submitting without all Art. 36(3) required documents, causing delays for information requests.
- No DPO involvement: Submitting without documented DPO advice per Art. 35(2).
- Treating SA silence as approval: SA non-response does not constitute approval or endorsement.
- Failing to implement SA recommendations: Proceeding with processing without addressing SA feedback.
Enforcement Context
- Art. 36(1) non-compliance (failure to consult when required) can result in administrative fines up to EUR 10 million or 2% of annual worldwide turnover under Art. 83(4)(a).
- Swedish DPA vs Karolinska (2019): Fine included failure to conduct DPIA and consequent failure to identify need for prior consultation.
- Norwegian DPA vs Municipality (2020): Enforcement action for proceeding with high-risk processing without prior consultation.
© 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
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/prior-consultation-dpa of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Prior Consultation Dpa 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 |
|---|---|---|---|---|---|---|
| Prior Consultation Dpa this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
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.
Pia Threshold Screening
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.
Related
Categories
Questions about Prior Consultation Dpa
What does Prior Consultation Dpa do?
Guides the Art. An agent skill from mukul975/Privacy-Data-Protection-Skills. Prior Consultation Dpa is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides the Art.
When should I use Prior Consultation Dpa?
Prior Consultation Dpa fits situations like: tasks that involve Privacy and GDPR.
How do I install Prior Consultation Dpa in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill prior-consultation-dpa -a claude-code`. Or copy the skill folder (skills/privacy/prior-consultation-dpa in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/prior-consultation-dpa in your project. Claude Code loads it when a task matches its description.
How do I install Prior Consultation Dpa in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill prior-consultation-dpa -a codex`. Or copy the skill folder (skills/privacy/prior-consultation-dpa in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/prior-consultation-dpa in your project. Codex loads it when a task matches its description.
Can I use Prior Consultation Dpa in Cursor, Gemini CLI or GitHub Copilot?
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 prior-consultation-dpa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prior-consultation-dpa, .gemini/skills/prior-consultation-dpa, .github/skills/prior-consultation-dpa and .opencode/skills/prior-consultation-dpa in your project.
What does Prior Consultation Dpa need to run?
Going by SKILL.md and its folder, Prior Consultation Dpa needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Prior Consultation Dpa access the network?
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.
Is Prior Consultation Dpa safe to install?
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.
What licence does Prior Consultation Dpa use?
Prior Consultation Dpa 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.
How many tokens does Prior Consultation Dpa use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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 483 tokens, read only when the agent opens those files.
What are the alternatives to Prior Consultation Dpa?
Skills that share tags, products or a category with Prior Consultation Dpa: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prior Consultation Dpa?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 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.