C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
A skill your agent uses when building apps that collect user data.
Install Privacy By Design
$ npx skills add sickn33/agentic-awesome-skills --skill privacy-by-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills privacy-by-design --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy-by-design .claude/skills/privacy-by-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .claude/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-designType 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 sickn33/agentic-awesome-skills --skill privacy-by-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills privacy-by-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy-by-design .agents/skills/privacy-by-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .agents/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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 sickn33/agentic-awesome-skills --skill privacy-by-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills privacy-by-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy-by-design .cursor/skills/privacy-by-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .cursor/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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/sickn33/agentic-awesome-skills.git --path skills/privacy-by-design--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 sickn33/agentic-awesome-skills --skill privacy-by-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills privacy-by-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy-by-design .gemini/skills/privacy-by-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .gemini/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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 sickn33/agentic-awesome-skills privacy-by-designInstalls 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 sickn33/agentic-awesome-skills --skill privacy-by-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy-by-design .github/skills/privacy-by-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .github/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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 sickn33/agentic-awesome-skills --skill privacy-by-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills privacy-by-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy-by-design .opencode/skills/privacy-by-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "privacy-by-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/privacy-by-design into .opencode/skills/privacy-by-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-by-design", 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
privacy-by-design- GitHub stars
- 47k
- Used in
- 2 other repos
- Token cost
- ~1.8k tokens
- SKILL.md length
- 757 words
- Files
- 2
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building apps that collect user data.
- Works in 6 steps: Data Minimization → Purpose Limitation → Storage Limitation → …
- Building apps that collect user data
- SKILL.md covers Overview, When to Use This Skill, Legal Frameworks and Core Principles, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Privacy By Design is an agent skill from sickn33/agentic-awesome-skills. Use when building apps that collect user data. Ensures privacy protections are built in from the start—data minimization, consent, encryption.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Building apps that collect user data
- Tasks that involve Privacy and GDPR
Example prompts
- “/privacy-by-design”
Requirements
- Python 3
Workflow steps
6 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 b84d35a. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, python and sql).
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
Privacy By Design loads about 1.8k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 757 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 757 words, ~1,849 tokens.
Download SKILL.mdSave it as
.claude/skills/privacy-by-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- privacy-by-design
- description
- Use when building apps that collect user data. Ensures privacy protections are built in from the start—data minimization, consent, encryption.
- risk
- safe
- source
- community
- date_added
- 2026-02-23
Privacy by Design
Overview
Integrate privacy protections into software architecture from the beginning, not as an afterthought. This skill applies Privacy by Design principles (GDPR Article 25, Cavoukian's framework) when designing databases, APIs, and user flows. Protects real users' data and builds trust.
When to Use This Skill
- Use when building apps that collect personal data (names, emails, locations, preferences)
- Use when designing database schemas, APIs, or authentication flows
- Use when the user mentions forms, user accounts, analytics, or third-party integrations
- Use when deploying to production—verify privacy controls before launch
Legal Frameworks
GDPR (EU) — Primary reference. Article 25 mandates "data protection by design and by default." Applies to EU users and often adopted globally.
CCPA (California) — Right to know, delete, opt-out of sale. Similar principles: minimize, disclose, allow control.
LGPD (Brazil) — Aligned with GDPR. Purpose limitation, necessity, transparency. Applies to Brazil users.
Design for the strictest framework you target; it often satisfies others.
Core Principles
1. Data Minimization
Collect only what is strictly necessary. Every field needs a documented justification. Avoid "we might need it later."
2. Purpose Limitation
Store the purpose of each data point. Do not reuse data for purposes the user did not consent to.
3. Storage Limitation
Define retention periods. Implement automated deletion or anonymization when retention expires. Never keep data "forever" by default.
4. Privacy as Default
Opt-in for optional collection, not opt-out. Sensitive settings (analytics, marketing) off by default. No pre-checked consent boxes.
5. End-to-End Security
Encrypt at rest and in transit. Use RBAC. Log access to sensitive data for audit.
6. Transparency
Document what is collected and why. Clear privacy policies. Easy access and deletion for users.
User Rights (GDPR)
Ensure these are implementable from day one:
| Right | What to build |
|---|---|
| Access | Endpoint or flow to return all user data |
| Rectification | Ability to update/correct data |
| Erasure | Account deletion + data purge (including backups) |
| Portability | Export data in machine-readable format (JSON, CSV) |
Deep Dive: Why It Matters
Data minimization — Less data = less breach impact, lower storage cost, simpler compliance. Each field is a liability.
Purpose limitation — Reusing data without consent is illegal under GDPR. Document purpose in schema or metadata.
Retention — Indefinite storage increases risk and violates GDPR. Define retention_days per data type; automate cleanup.
Logging — Logs often leak PII. Redact emails, IDs, tokens. Use structured logging with allowlists.
Third parties — Every SDK (analytics, crash reporting, ads) may send data elsewhere. Audit dependencies; require consent before loading.
Code Examples
JavaScript/Node — Minimal User Model
// BAD: Collecting everything "just in case"
const user = { email, name, phone, address, birthdate, ipAddress, userAgent, ... };
// GOOD: Minimal, documented purpose
const user = {
email, // purpose: authentication
displayName, // purpose: UI display
createdAt, // purpose: account age
};JavaScript — Consent Before Tracking
// BAD: Track first, ask later
analytics.track(userId, event);
// GOOD: Check consent first
if (userConsent.analytics) {
analytics.track(userId, event);
}Python — Safe Logging
# BAD: Logging PII in plain text
logger.info(f"User {user.email} logged in from {request.remote_addr}")
# GOOD: Redact or hash identifiers
logger.info(f"User {hash_user_id(user.id)} logged in")
# Or: logger.info("User login", extra={"user_id_hash": hash_id(user.id)})SQL — Schema with Purpose and Retention
-- GOOD: Document purpose and retention in schema
CREATE TABLE users (
id UUID PRIMARY KEY,
email VARCHAR(255) NOT NULL, -- purpose: auth, retention: account lifetime
display_name VARCHAR(100), -- purpose: UI, retention: account lifetime
created_at TIMESTAMPTZ, -- purpose: audit, retention: 7 years
last_login_at TIMESTAMPTZ -- purpose: security, retention: 90 days
);
-- Add retention policy (PostgreSQL example)
-- Schedule job to anonymize/delete last_login_at after 90 daysAPI — Return Only Needed Fields
# BAD: Returning full user object
return jsonify(user) # May include internal fields, hashed passwords
# GOOD: Explicit allowlist
return jsonify({
"id": user.id,
"email": user.email,
"displayName": user.display_name,
})Show full SKILL.md (331 more words)Show less
Common Pitfalls
| Pitfall | Solution |
|---|---|
| Logs contain emails, IPs, tokens | Redact PII; use hashed IDs or structured logs |
| Error messages expose data | Return generic errors to client; log details server-side |
| Third-party SDKs load before consent | Load analytics/ads only after consent; use consent management |
| No deletion flow | Design account deletion + data purge from day one |
| Backups keep data forever | Include backups in retention; encrypt backups |
| Cookies without consent | Use consent banner; respect Do Not Track where applicable |
Third-Party Audit
Before adding a dependency that touches user data:
- What data does it collect or receive?
- Where does it send data (servers, countries)?
- Is it loaded before or after user consent?
- Can we disable it if user opts out?
- Does their privacy policy align with ours?
Implementation Checklist
When building a feature that touches user data:
- Is this data necessary? Can we achieve the goal with less?
- Do we have explicit consent for this use?
- Is it encrypted (at rest and in transit)?
- Do we have a retention/deletion policy?
- Can the user export or delete their data?
- Are third-party services disclosed and consented?
- Are logs free of PII?
- Are backups included in retention policy?
Best Practices
- ✅ Ask "do we need this?" for every new data field
- ✅ Design deletion and export flows from day one
- ✅ Use hashing or tokenization for sensitive identifiers when possible
- ✅ Document purpose and retention in schema or metadata
- ❌ Don't log passwords, tokens, or PII in plain text
- ❌ Don't share data with third parties without explicit consent
- ❌ Don't assume "we'll add privacy later"—it rarely happens
- ❌ Don't expose stack traces or internal errors to clients
When to Use
This skill is applicable when building software that collects, stores, or processes personal data. Apply it proactively during design and implementation.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33, MIT. 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 1 other file in skills/privacy-by-design of sickn33/agentic-awesome-skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit b84d35a
Used in 2 other repositories
We found 13 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Privacy By Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Privacy By Design this skillsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| 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 sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Categories
Questions about Privacy By Design
What does Privacy By Design do?
A skill your agent uses when building apps that collect user data. Privacy By Design is an agent skill from sickn33/agentic-awesome-skills. Use when building apps that collect user data.
When should I use Privacy By Design?
Privacy By Design fits situations like: building apps that collect user data; tasks that involve Privacy and GDPR.
How do I install Privacy By Design in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill privacy-by-design -a claude-code`. Or copy the skill folder (skills/privacy-by-design in sickn33/agentic-awesome-skills) into .claude/skills/privacy-by-design in your project. Claude Code loads it when a task matches its description.
How do I install Privacy By Design in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill privacy-by-design -a codex`. Or copy the skill folder (skills/privacy-by-design in sickn33/agentic-awesome-skills) into .agents/skills/privacy-by-design in your project. Codex loads it when a task matches its description.
Can I use Privacy By Design 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 sickn33/agentic-awesome-skills --skill privacy-by-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/privacy-by-design, .gemini/skills/privacy-by-design, .github/skills/privacy-by-design and .opencode/skills/privacy-by-design in your project.
What does Privacy By Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Privacy By Design is instructions for the agent only. Our summary lists: Python 3.
Does Privacy By Design 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 Privacy By Design 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. Review the folder before installing.
What licence does Privacy By Design use?
Privacy By Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Privacy By Design use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Privacy By Design?
Skills that share tags, products or a category with Privacy By Design: 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 Privacy By Design?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.