C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a).
Install Consent For Transfers
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-for-transfers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-for-transfers --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/consent-for-transfers .claude/skills/consent-for-transfers && 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 "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .claude/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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/consent-for-transfersType 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 consent-for-transfers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-for-transfers --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/consent-for-transfers .agents/skills/consent-for-transfers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .agents/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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 consent-for-transfers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-for-transfers --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/consent-for-transfers .cursor/skills/consent-for-transfers && 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 "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .cursor/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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/consent-for-transfers--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 consent-for-transfers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-for-transfers --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/consent-for-transfers .gemini/skills/consent-for-transfers && 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 "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .gemini/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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 consent-for-transfersInstalls 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 consent-for-transfers -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/consent-for-transfers .github/skills/consent-for-transfers && 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 "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .github/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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 consent-for-transfers -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 consent-for-transfers --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/consent-for-transfers .opencode/skills/consent-for-transfers && 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 "consent-for-transfers" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-for-transfers into .opencode/skills/consent-for-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-for-transfers", 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
consent-for-transfers- GitHub stars
- 301
- Token cost
- ~1.7k tokens
- SKILL.md length
- 877 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a).
- Works in 5 steps: Express statement: The data subject must… → Specific to the transfer: Consent must… → Informed of risks: The data subject must… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Explicit Consent Requirements…, CloudVault SaaS Inc. Transfer… and Limitations of Consent as…, plus 1 more section
- Runs Python scripts from its folder
What it does
Consent For Transfers is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a). Covers informed consent requirements including risks of transfers without adequacy decisions or appropriate safeguards, specific destination country disclosure, and the narrow scope of derogation-based transfers.
Its SKILL.md is about 1.7k 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
- “/consent-for-transfers”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Express statement: The data subject must make an express statement of consent specifically for the transfer. An unticked checkbox is…
- Specific to the transfer: Consent must specifically mention the international transfer, not be buried in general terms.
- Informed of risks: The data subject must be told about the specific risks of the transfer, not just generic warnings.
- Specific destination: The third country or countries must be named.
- Absence disclosed: The data subject must be told that there is no adequacy decision and no appropriate safeguards in place for the…
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
Consent For Transfers loads about 1.7k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 877 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). 877 words, ~1,675 tokens.
Download SKILL.mdSave it as
.claude/skills/consent-for-transfers/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- consent-for-transfers
- description
- Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a). Covers informed consent requirements including risks of transfers without adequacy decisions or appropriate safeguards, specific destination country disclosure, and the narrow scope of derogation-based transfers.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- consent-management
- metadata.tags
- transfer-consent, article-49, international-transfers, explicit-consent, data-transfers
Managing Consent for Transfers
Overview
GDPR Article 49(1)(a) provides that in the absence of an adequacy decision (Article 45) or appropriate safeguards (Article 46), a transfer of personal data to a third country may take place if "the data subject has explicitly consented to the proposed transfer, after having been informed of the possible risks of such transfers for the data subject due to the absence of an adequacy decision and appropriate safeguards."
This is a derogation — a last resort — not a primary transfer mechanism. The EDPB Guidelines 2/2018 on derogations under Article 49 emphasize that derogations must be interpreted restrictively and should not become the rule.
Explicit Consent Requirements for Transfers
What Makes Transfer Consent "Explicit"
Explicit consent under Article 49(1)(a) requires a higher standard than standard consent under Article 6(1)(a):
- Express statement: The data subject must make an express statement of consent specifically for the transfer. An unticked checkbox is sufficient for standard consent but may not be sufficient for explicit consent — a written or typed declaration is preferred.
- Specific to the transfer: Consent must specifically mention the international transfer, not be buried in general terms.
- Informed of risks: The data subject must be told about the specific risks of the transfer, not just generic warnings.
- Specific destination: The third country or countries must be named.
- Absence disclosed: The data subject must be told that there is no adequacy decision and no appropriate safeguards in place for the destination.
Information That Must Be Provided Before Consent
Per Article 49(1)(a) and EDPB Guidelines 2/2018:
| Information Element | Description | Example for CloudVault SaaS Inc. |
|---|---|---|
| Destination country | Specific country name | India |
| Recipient identity | Who will receive the data | CloudVault India Pvt. Ltd. (subsidiary) |
| Purpose of transfer | Why the data is being transferred | Customer support during EU night hours |
| Data categories | What personal data will be transferred | Name, email, account metadata, support ticket content |
| Absence of adequacy decision | India does not have an EU adequacy decision | "India has not been recognized by the European Commission as providing an adequate level of data protection" |
| Absence of safeguards | No SCCs or BCRs in place for this transfer | "This transfer is not covered by Standard Contractual Clauses or Binding Corporate Rules" |
| Specific risks | What could go wrong | "Indian data protection law (DPDP Act 2023) may not provide equivalent protections. Government access requests may not be subject to the same limitations as under EU law." |
| Withdrawal right | How to withdraw consent | "You can withdraw consent for this transfer at any time in Settings > Privacy" |
CloudVault SaaS Inc. Transfer Consent Implementation
Show full SKILL.md (449 more words)Show less
Scenario: Customer Support Data Transfer to India
CloudVault SaaS Inc. operates a customer support center in Bengaluru, India (CloudVault India Pvt. Ltd.). When EU users submit support tickets outside EU business hours, ticket data may be accessed from India.
Consent Statement (displayed to users):
"To provide you with 24/7 customer support, CloudVault SaaS Inc. may transfer your support ticket data (your name, email address, account details, and the content of your support request) to CloudVault India Pvt. Ltd. in Bengaluru, India.
India does not have an adequacy decision from the European Commission, and this specific transfer is not covered by Standard Contractual Clauses or Binding Corporate Rules.
This means your data may not receive the same level of protection as under EU law. In particular:
- The Indian Digital Personal Data Protection Act 2023 is still in early implementation and its enforcement mechanisms are not yet fully established
- Indian government authorities may have legal powers to access personal data that differ from those available to EU authorities
- Judicial remedies available to you in India may differ from those available under EU law
You are not required to consent to this transfer. If you do not consent, your support requests will be handled during EU business hours only (Monday-Friday, 08:00-18:00 CET) by our Dublin-based support team.
You can withdraw this consent at any time in Settings > Privacy > Data Transfers. Withdrawal will take effect within 24 hours."
Consent Mechanism
- Two-step process: (1) user reads the full risk disclosure, (2) user types "I consent to the transfer" in a text field
- This typed declaration satisfies the "explicit" requirement
- Consent is recorded with all standard consent record fields plus transfer-specific fields
Limitations of Consent as Transfer Basis
Per EDPB Guidelines 2/2018:
- Not for systematic/repetitive transfers: Consent under Article 49(1)(a) should not be used as the basis for systematic, large-scale, or repetitive transfers. For those, use SCCs (Article 46(2)(c)) or BCRs (Article 47).
- Not a blank check: Each transfer must be specifically consented to, or consent must cover a clearly defined and limited set of transfers.
- Power imbalance applies: The same freely-given requirement applies — consent for transfers in an employment context is generally not valid.
- Withdrawal must be feasible: If the controller cannot operationally stop transfers upon withdrawal, consent may not be the appropriate basis.
Key Regulatory References
- GDPR Article 44 — General principle for transfers
- GDPR Article 45 — Transfers based on adequacy decisions
- GDPR Article 46 — Transfers subject to appropriate safeguards
- GDPR Article 49(1)(a) — Derogation: explicit consent for transfers
- EDPB Guidelines 2/2018 on Derogations under Article 49 (adopted May 25, 2018)
- CJEU C-311/18 (Schrems II, July 16, 2020) — Invalidated Privacy Shield; heightened transfer scrutiny
- EDPB Recommendations 01/2020 — Supplementary measures for transfers
© 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/consent-for-transfers 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
Consent For Transfers 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 |
|---|---|---|---|---|---|---|
| Consent For Transfers this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.7k | 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 Consent For Transfers
What does Consent For Transfers do?
Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a). Consent For Transfers is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for obtaining explicit consent for international data transfers under GDPR Article 49(1)(a).
When should I use Consent For Transfers?
Consent For Transfers fits situations like: tasks that involve Privacy and GDPR.
How do I install Consent For Transfers in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-for-transfers -a claude-code`. Or copy the skill folder (skills/privacy/consent-for-transfers in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/consent-for-transfers in your project. Claude Code loads it when a task matches its description.
How do I install Consent For Transfers in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-for-transfers -a codex`. Or copy the skill folder (skills/privacy/consent-for-transfers in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/consent-for-transfers in your project. Codex loads it when a task matches its description.
Can I use Consent For Transfers 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 consent-for-transfers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/consent-for-transfers, .gemini/skills/consent-for-transfers, .github/skills/consent-for-transfers and .opencode/skills/consent-for-transfers in your project.
What does Consent For Transfers need to run?
Going by SKILL.md and its folder, Consent For Transfers needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Consent For Transfers 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 Consent For Transfers 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 Consent For Transfers use?
Consent For Transfers 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 Consent For Transfers use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Consent For Transfers?
Skills that share tags, products or a category with Consent For Transfers: 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 Consent For Transfers?
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.