C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implementation guide for ePrivacy Directive compliant double opt-in email consent.
Install Double Opt In Email
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill double-opt-in-email -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills double-opt-in-email --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/double-opt-in-email .claude/skills/double-opt-in-email && 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 "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .claude/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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/double-opt-in-emailType 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 double-opt-in-email -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills double-opt-in-email --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/double-opt-in-email .agents/skills/double-opt-in-email && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .agents/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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 double-opt-in-email -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills double-opt-in-email --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/double-opt-in-email .cursor/skills/double-opt-in-email && 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 "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .cursor/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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/double-opt-in-email--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 double-opt-in-email -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills double-opt-in-email --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/double-opt-in-email .gemini/skills/double-opt-in-email && 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 "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .gemini/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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 double-opt-in-emailInstalls 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 double-opt-in-email -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/double-opt-in-email .github/skills/double-opt-in-email && 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 "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .github/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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 double-opt-in-email -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 double-opt-in-email --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/double-opt-in-email .opencode/skills/double-opt-in-email && 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 "double-opt-in-email" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/double-opt-in-email into .opencode/skills/double-opt-in-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "double-opt-in-email", 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
double-opt-in-email- GitHub stars
- 301
- Token cost
- ~1.6k tokens
- SKILL.md length
- 398 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implementation guide for ePrivacy Directive compliant double opt-in email consent.
- Works in 4 steps: When someone unsubscribes: Add their… → Suppression list is permanent: Never… → Check before sending: Always check the… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Double Opt-In Workflow, Token Expiration and Retry… and Suppression List Management, plus 2 more sections
- Runs Python scripts from its folder
What it does
Double Opt In Email is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implementation guide for ePrivacy Directive compliant double opt-in email consent. Covers confirmation email workflow design, token expiration handling, record-keeping requirements, suppression list management, and integration with CAN-SPAM Act and CASL requirements for multi-jurisdiction compliance.
Its SKILL.md is about 1.6k 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 Design tokens. 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
- Tasks that involve Design tokens
Example prompts
- “/double-opt-in-email”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- When someone unsubscribes: Add their email to the suppression list immediately
- Suppression list is permanent: Never remove an email from the suppression list automatically
- Check before sending: Always check the suppression list before sending any marketing email AND before sending a DOI confirmation email
- If a suppressed email re-subscribes: Allow re-subscription but require fresh DOI confirmation; remove from suppression list only after…
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
Double Opt In Email loads about 1.6k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 398 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). 398 words, ~1,582 tokens.
Download SKILL.mdSave it as
.claude/skills/double-opt-in-email/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- double-opt-in-email
- description
- Implementation guide for ePrivacy Directive compliant double opt-in email consent. Covers confirmation email workflow design, token expiration handling, record-keeping requirements, suppression list management, and integration with CAN-SPAM Act and CASL requirements for multi-jurisdiction compliance.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- consent-management
- metadata.tags
- double-opt-in, email-consent, eprivacy-directive, email-marketing, suppression-list
Implementing Double Opt-In Email
Overview
Double opt-in (DOI) is the gold standard for email marketing consent. It requires two steps: (1) the user submits their email address and indicates interest, and (2) the user clicks a confirmation link in a verification email. This creates a verifiable consent record that satisfies GDPR Article 7(1) (demonstrability), ePrivacy Directive Article 13 (prior consent for electronic marketing), and German Federal Court of Justice (BGH) rulings that have established DOI as the expected standard in Germany.
Double Opt-In Workflow
START: User enters email on CloudVault SaaS Inc. sign-up or newsletter form
│
├─► Step 1: Initial Opt-In Request
│ ├─ User enters email address
│ ├─ User ticks unticked checkbox: "Send me product updates and news"
│ ├─ Validate email format (RFC 5322)
│ ├─ Check suppression list — if email is suppressed, do NOT send confirmation
│ └─ Display: "Check your email to confirm your subscription."
│
├─► Step 2: Generate Confirmation Token
│ ├─ Create cryptographically random token (256-bit, URL-safe base64)
│ ├─ Associate token with: email address, purpose, timestamp, IP, user agent
│ ├─ Set expiration: 48 hours from generation
│ └─ Store pending subscription record (status: "pending_confirmation")
│
├─► Step 3: Send Confirmation Email
│ ├─ From: noreply@cloudvault-saas.eu
│ ├─ Subject: "Confirm your CloudVault newsletter subscription"
│ ├─ Body:
│ │ ├─ "You requested to receive product updates from CloudVault SaaS Inc."
│ │ ├─ "Click below to confirm:"
│ │ ├─ [Confirm Subscription] button → confirmation URL with token
│ │ ├─ "If you didn't request this, you can ignore this email."
│ │ ├─ "This link expires in 48 hours."
│ │ └─ Controller details: CloudVault SaaS Inc., 42 Innovation Drive, Dublin
│ ├─ Headers:
│ │ ├─ List-Unsubscribe: <mailto:unsubscribe@cloudvault-saas.eu>
│ │ └─ List-Unsubscribe-Post: List-Unsubscribe=One-Click
│ └─ Note: This confirmation email is NOT marketing — it is transactional
│
├─► Step 4: User Clicks Confirmation Link
│ ├─ Validate token: exists, not expired, not already used
│ ├─ If valid:
│ │ ├─ Update subscription status: "confirmed"
│ │ ├─ Record consent with full audit trail:
│ │ │ ├─ Initial request: timestamp, IP, user agent
│ │ │ ├─ Confirmation: timestamp, IP, user agent
│ │ │ └─ Consent text version hash
│ │ ├─ Add email to active marketing list
│ │ └─ Display: "Subscription confirmed! You'll receive updates from CloudVault."
│ │
│ ├─ If expired:
│ │ ├─ Display: "This link has expired. Please subscribe again."
│ │ └─ Delete pending record
│ │
│ └─ If already used:
│ └─ Display: "You're already subscribed."
│
└─► Step 5: Ongoing Management
├─ Every marketing email includes one-click unsubscribe (RFC 8058)
├─ Unsubscribe adds to suppression list (permanent)
├─ Consent records retained for demonstration per Art. 7(1)
└─ Re-consent requested after 24 months of inactivityToken Expiration and Retry Handling
| Scenario | Action | Reasoning |
|---|---|---|
| Token expires (48 hours) | Delete pending record, do not send reminders | Avoid spam risk; user can re-subscribe |
| User requests twice | Do not send second confirmation if one is pending | Prevent email flooding |
| Email bounces | Mark pending record as "bounced", do not retry | Invalid email address |
| Token used twice | Show "already subscribed" page | Prevent duplicate records |
Suppression List Management
The suppression list is critical for compliance with CAN-SPAM Act Section 7704(a)(3)(A) (10-day unsubscribe processing) and GDPR Article 17(3)(c) (retention for legal obligation compliance):
- When someone unsubscribes: Add their email to the suppression list immediately
- Suppression list is permanent: Never remove an email from the suppression list automatically
- Check before sending: Always check the suppression list before sending any marketing email AND before sending a DOI confirmation email
- If a suppressed email re-subscribes: Allow re-subscription but require fresh DOI confirmation; remove from suppression list only after confirmation click
Show full SKILL.md (156 more words)Show less
Multi-Jurisdiction Compliance
| Requirement | GDPR + ePrivacy | CAN-SPAM (US) | CASL (Canada) |
|---|---|---|---|
| Consent type | Prior opt-in (DOI recommended) | Opt-out (but DOI is best practice) | Express consent (implied consent limited) |
| Unsubscribe | Art. 7(3) — as easy as giving | 10 business days to process | 10 business days to process |
| Sender identification | Art. 13(1)(a) | Physical postal address required | Contact information required |
| Record-keeping | Art. 7(1) — demonstrate consent | Maintain opt-out requests 3 years | Maintain consent records |
| Penalties | Up to EUR 20M or 4% global turnover | Up to $51,744 per email | Up to CAD 10M per violation |
Key Regulatory References
- ePrivacy Directive Article 13 — Unsolicited communications
- GDPR Article 7(1) — Demonstrating consent
- GDPR Article 7(3) — Withdrawal of consent
- CAN-SPAM Act (15 U.S.C. 7701-7713) — US commercial email requirements
- CASL (S.C. 2010, c. 23) — Canadian Anti-Spam Legislation
- RFC 8058 — Signaling One-Click Functionality for List Email Headers
- German BGH VI ZR 269/12 (2004) — Double opt-in as standard for email marketing consent
- CNIL Deliberation on Commercial Prospecting (2022) — Email consent requirements
© 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/double-opt-in-email 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
Double Opt In Email 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 |
|---|---|---|---|---|---|---|
| Double Opt In Email this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.6k | 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 Double Opt In Email
What does Double Opt In Email do?
Implementation guide for ePrivacy Directive compliant double opt-in email consent. Double Opt In Email is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implementation guide for ePrivacy Directive compliant double opt-in email consent.
When should I use Double Opt In Email?
Double Opt In Email fits situations like: tasks that involve Privacy and GDPR; tasks that involve Design tokens.
How do I install Double Opt In Email in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill double-opt-in-email -a claude-code`. Or copy the skill folder (skills/privacy/double-opt-in-email in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/double-opt-in-email in your project. Claude Code loads it when a task matches its description.
How do I install Double Opt In Email in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill double-opt-in-email -a codex`. Or copy the skill folder (skills/privacy/double-opt-in-email in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/double-opt-in-email in your project. Codex loads it when a task matches its description.
Can I use Double Opt In Email 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 double-opt-in-email -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/double-opt-in-email, .gemini/skills/double-opt-in-email, .github/skills/double-opt-in-email and .opencode/skills/double-opt-in-email in your project.
What does Double Opt In Email need to run?
Going by SKILL.md and its folder, Double Opt In Email needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Double Opt In Email 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 Double Opt In Email 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 Double Opt In Email use?
Double Opt In Email 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 Double Opt In Email use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Double Opt In Email?
Skills that share tags, products or a category with Double Opt In Email: 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 Double Opt In Email?
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.