C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Agent skill
Implementing Data Protection By Default
Technical implementation of GDPR Article 25(2) data protection by default.
Install Implementing Data Protection By Default
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill implementing-data-protection-by-default -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills implementing-data-protection-by-default --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/implementing-data-protection-by-default .claude/skills/implementing-data-protection-by-default && 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 "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .claude/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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/implementing-data-protection-by-defaultType 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 implementing-data-protection-by-default -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills implementing-data-protection-by-default --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/implementing-data-protection-by-default .agents/skills/implementing-data-protection-by-default && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .agents/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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 implementing-data-protection-by-default -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills implementing-data-protection-by-default --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/implementing-data-protection-by-default .cursor/skills/implementing-data-protection-by-default && 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 "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .cursor/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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/implementing-data-protection-by-default--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 implementing-data-protection-by-default -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills implementing-data-protection-by-default --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/implementing-data-protection-by-default .gemini/skills/implementing-data-protection-by-default && 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 "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .gemini/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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 implementing-data-protection-by-defaultInstalls 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 implementing-data-protection-by-default -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/implementing-data-protection-by-default .github/skills/implementing-data-protection-by-default && 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 "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .github/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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 implementing-data-protection-by-default -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 implementing-data-protection-by-default --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/implementing-data-protection-by-default .opencode/skills/implementing-data-protection-by-default && 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 "implementing-data-protection-by-default" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/implementing-data-protection-by-default into .opencode/skills/implementing-data-protection-by-default/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-data-protection-by-default", 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
implementing-data-protection-by-default- GitHub stars
- 295
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,186 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Technical implementation of GDPR Article 25(2) data protection by default.
- Works in 4 steps: Amount of personal data collected → Extent of processing performed → Period of storage → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, The Four Dimensions of…, Technical Implementation… and By-Default Verification Process, plus 1 more section
- Runs Python scripts from its folder
What it does
Implementing Data Protection By Default is an agent skill from mukul975/Privacy-Data-Protection-Skills. Technical implementation of GDPR Article 25(2) data protection by default. Covers strictest privacy settings as default configuration, minimum data collection, limited storage duration, restricted accessibility, and opt-in rather than opt-out patterns. Includes implementation checklist and system design requirements.
Its SKILL.md is about 2.5k 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
- “/implementing-data-protection-by-default”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Amount of personal data collected
- Extent of processing performed
- Period of storage
- Accessibility of personal data
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
Implementing Data Protection By Default loads about 2.5k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 1,186 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,186 words, ~2,502 tokens.
Download SKILL.mdSave it as
.claude/skills/implementing-data-protection-by-default/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- implementing-data-protection-by-default
- description
- Technical implementation of GDPR Article 25(2) data protection by default. Covers strictest privacy settings as default configuration, minimum data collection, limited storage duration, restricted accessibility, and opt-in rather than opt-out patterns. Includes implementation checklist and system design requirements.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-by-design
- metadata.tags
- data-protection-by-default, article-25, privacy-defaults, opt-in, minimum-collection
Implementing Data Protection by Default
Overview
GDPR Article 25(2) requires that controllers implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. This obligation applies across four dimensions:
- Amount of personal data collected
- Extent of processing performed
- Period of storage
- Accessibility of personal data
The EDPB Guidelines 4/2019 on Article 25 clarify that "by default" means the strictest privacy settings apply automatically, without requiring any action from the data subject. The data subject should not need to take action to protect their privacy — the system does it for them.
The Four Dimensions of By-Default Protection
Dimension 1: Minimum Data Collection (Amount)
Principle: By default, collect only the data fields strictly necessary for the core service purpose. Additional data collection requires explicit opt-in.
| Default State | Opt-In State | Example |
|---|---|---|
| Core fields only | Extended profile | Account creation collects email + display_name only; phone, address, photo collected only if user activates billing or delivery features |
| No location data | Location-enabled features | Mobile app does not request location permission by default; only requests when user activates location-dependent feature |
| No behavioral tracking | Analytics opt-in | Website loads without analytics cookies; tracking begins only after user grants consent in cookie banner |
| Minimal form fields | Progressive disclosure | Registration form shows 3 required fields; optional fields appear only when user clicks "Add more information" |
Prism Data Systems AG Implementation:
The default customer registration at Prism Data Systems AG collects exactly three fields: email, display_name, and country_code. The country code is needed for regulatory compliance (determining applicable data protection law). All other fields (phone number, billing address, company name, job title) are collected only when the user activates a feature that requires them (billing module, enterprise integration, support escalation).
Dimension 2: Minimum Processing (Extent)
Principle: By default, process data only for the primary purpose. Secondary processing (analytics, profiling, marketing) requires explicit opt-in.
| Processing Activity | Default State | Opt-In Required |
|---|---|---|
| Core service delivery | Active (Art. 6(1)(b)) | No |
| Product analytics | Disabled | Yes — consent toggle in preference center |
| Marketing communications | Disabled | Yes — separate consent at registration |
| Profiling for recommendations | Disabled | Yes — explicit opt-in with explanation |
| Third-party data sharing | Disabled | Yes — named third party + purpose |
| Automated decision-making | Disabled | Yes — Art. 22 explicit consent |
Prism Data Systems AG Implementation: New customer accounts at Prism Data Systems AG have all optional processing activities disabled by default. The account dashboard shows five processing toggles, all set to OFF:
- Product analytics: OFF
- Marketing emails: OFF
- Feature recommendations: OFF
- Usage data for ML training: OFF
- Anonymous benchmarking contributions: OFF
Dimension 3: Minimum Storage (Period)
Principle: By default, apply the shortest defensible retention period. Longer retention requires justification tied to a specific legal obligation.
| Data Category | Default Retention | Extended Retention (Justified) |
|---|---|---|
| Session data | Deleted at session end | Not applicable |
| Server logs | 90 days | 12 months (security investigation) |
| Customer account data | Account duration + 30 days | + statutory period (tax: 10 years for billing) |
| Support tickets | 1 year after closure | 3 years (limitation period) |
| Marketing consent records | Consent duration + 3 years | + 5 years (accountability, Art. 7(1)) |
| Analytics data | 13 months | Not applicable (maximum) |
Prism Data Systems AG Implementation: The retention policy engine at Prism Data Systems AG applies the shortest retention period by default for each data category. Extended retention is applied only for data categories with documented statutory requirements (tax records: 10 years per Swiss CO Art. 958f). All other data follows the purpose-based minimum retention.
Dimension 4: Minimum Accessibility
Principle: By default, restrict access to personal data to the minimum set of roles necessary. Broader access requires explicit authorization.
| Role | Default Access | Elevated Access (Requires Justification) |
|---|---|---|
| Customer support (Tier 1) | Masked PII only (m***@domain.ch) | Unmasked PII (30-min timeout, ticket reference required) |
| Analytics team | Pseudonymized data only | No access to direct identifiers |
| Engineering team | No production PII access | Break-glass access (dual approval, logged, time-limited) |
| Marketing team | Aggregate statistics only | No individual-level data access |
| DPO | Full access for compliance investigations | Standing access with audit trail |
| External auditor | Anonymized samples | Purpose-limited access with NDA |
Prism Data Systems AG Implementation: All new employee accounts at Prism Data Systems AG are provisioned with zero personal data access by default. Access is granted per-purpose through an access request workflow requiring manager approval and DPO notification. Access grants expire after 90 days and must be renewed. The Tier 1 support dashboard displays dynamically masked data by default.
Show full SKILL.md (461 more words)Show less
Technical Implementation Checklist
User Interface Defaults
- All consent toggles default to OFF (unticked)
- Privacy settings page accessible from main navigation
- No pre-selected optional data collection
- No dark patterns (no misleading button labels, no visual emphasis on "Accept All")
- Cookie banner defaults to "Reject All" with equal visual prominence to "Accept All"
- Registration form shows only mandatory fields by default
- Notification preferences default to minimum (transactional only)
- Profile visibility defaults to private (not public)
- Data sharing toggles default to OFF for each third party
- Search engine indexing of profiles defaults to OFF
Backend Defaults
- API endpoints reject non-allowlisted fields (return 400 for unexpected fields)
- New database tables include TTL metadata columns by default
- Default retention period applied automatically unless longer period is explicitly configured
- Pseudonymization applied at analytics ingestion boundary by default
- Field-level encryption enabled for all PII columns by default
- Dynamic masking rules applied to all support and operations dashboards
- Audit logging enabled for all personal data access by default
- Minimum group size (11) enforced on all analytics outputs
- Cross-purpose data access blocked by default (requires compatibility assessment)
- New service deployments fail privacy gate if data minimization assessment is not completed
Access Control Defaults
- New employee accounts provisioned with zero personal data access
- Access grants expire after 90 days by default
- Elevated access requires documented justification and approval
- Break-glass access logged and reviewed within 24 hours
- Third-party access disabled by default until DPA is executed
- API keys scoped to minimum required data categories
Communication Defaults
- Marketing communications disabled for all new accounts
- Transactional emails only (account confirmations, security alerts)
- Push notifications limited to security alerts by default
- Newsletter subscription requires separate opt-in
- Partner communications disabled by default
By-Default Verification Process
New account audit — Create a test account through the standard registration flow. Verify that no optional processing is active, no marketing communications are scheduled, and the minimum data fields are collected.
Dashboard inspection — Log in as a Tier 1 support agent. Verify that all PII is masked by default and that unmasking requires explicit action with justification.
API testing — Send API requests with additional fields beyond the allowlist. Verify that extra fields are rejected (HTTP 400).
Retention verification — Check that newly created records have TTL metadata set according to the minimum retention period.
Analytics output — Run a standard analytics query. Verify that results are pseudonymized, minimum group size is enforced, and differential privacy noise is applied.
Key Regulatory References
- GDPR Article 25(2) — Data protection by default
- GDPR Article 25(1) — Data protection by design
- GDPR Recital 78 — Technical measures for data protection by default
- EDPB Guidelines 4/2019 on Article 25, Section 3: Data Protection by Default
- CJEU C-673/17 (Planet49) — Pre-ticked boxes do not constitute consent
- EDPB Guidelines 05/2020 on consent — Consent must be freely given, not default
© 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/implementing-data-protection-by-default 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
Implementing Data Protection By Default 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 |
|---|---|---|---|---|---|---|
| Implementing Data Protection By Default this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2.5k | 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 | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 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 278 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.
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.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Implementing Data Protection By Default
What does Implementing Data Protection By Default do?
Technical implementation of GDPR Article 25(2) data protection by default. Implementing Data Protection By Default is an agent skill from mukul975/Privacy-Data-Protection-Skills. Technical implementation of GDPR Article 25(2) data protection by default.
When should I use Implementing Data Protection By Default?
Implementing Data Protection By Default fits situations like: tasks that involve Privacy and GDPR.
How do I install Implementing Data Protection By Default in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill implementing-data-protection-by-default -a claude-code`. Or copy the skill folder (skills/privacy/implementing-data-protection-by-default in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/implementing-data-protection-by-default in your project. Claude Code loads it when a task matches its description.
How do I install Implementing Data Protection By Default in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill implementing-data-protection-by-default -a codex`. Or copy the skill folder (skills/privacy/implementing-data-protection-by-default in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/implementing-data-protection-by-default in your project. Codex loads it when a task matches its description.
Can I use Implementing Data Protection By Default 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 implementing-data-protection-by-default -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-data-protection-by-default, .gemini/skills/implementing-data-protection-by-default, .github/skills/implementing-data-protection-by-default and .opencode/skills/implementing-data-protection-by-default in your project.
What does Implementing Data Protection By Default need to run?
Going by SKILL.md and its folder, Implementing Data Protection By Default needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Implementing Data Protection By Default 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 Implementing Data Protection By Default 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 Implementing Data Protection By Default use?
Implementing Data Protection By Default 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 Implementing Data Protection By Default use?
About 2.5k tokens (SKILL.md is roughly 10k 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.9k tokens, read only when the agent opens those files.
What are the alternatives to Implementing Data Protection By Default?
Skills that share tags, products or a category with Implementing Data Protection By Default: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 942 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementing Data Protection By Default?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.