privacy-guardian — Claude Code skill: what it does, how to install
privacy-guardian is a Claude Code skill for privacy engineering, covering differential privacy, encryption, PII handling, and GDPR or CCPA audits.
Apache-2.0 1 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a claude-codeWhat privacy-guardian does
This skill instructs the agent to act as a privacy and security specialist. It approaches privacy as an engineering constraint rather than a legal checklist, enforcing data minimisation, multi-layered defense, and systematic auditing.
The skill structures its guidance around three reference files. It consults references/patterns.md during system creation, checks references/sharp_edges.md to diagnose risks, and uses references/validations.md for objective review constraints.
Generic solutions are rejected whenever a matching approach exists in references/patterns.md. The instructions explicitly leave memory storage, embeddings, causal inference, and workflow pipelines outside its scope, delegating those to separate tools.
What it helps with
- Design systems compliant with GDPR and CCPA requirements
- Audit access control logs and data retention policies
- Integrate differential privacy mechanisms for sensitive data
- Validate PII storage and encryption architectures against known failure modes
Example prompts for the agent
- Review our user data schema for CCPA compliance using privacy-guardian
- Check our encryption and audit trail setup against references/sharp_edges.md
- Draft a differential privacy approach for query logs based on references/patterns.md
How to install privacy-guardian
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a claude-code2Manually: put the files in place
~/.claude/skills/privacy-guardian/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/privacy-guardian/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a codex2Manually: put the files in place
.agents/skills/privacy-guardian/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a cursor2Manually: put the files in place
.cursor/skills/privacy-guardian/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/privacy-guardian2Manually: put the files in place
.github/skills/privacy-guardian/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/privacy-guardianManually: put the files in place
.devin/skills/privacy-guardian/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about privacy-guardian
How to install privacy-guardian in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill privacy-guardian -a claude-code in your terminal.
What does privacy-guardian do?
It guides the agent on encryption, differential privacy, access controls, and compliance for systems handling personal data.
What domains does privacy-guardian defer to other tools?
It excludes memory hierarchy, vector embeddings, workflow orchestration, and causal inference, directing those requests elsewhere.
Source text
SKILL.md · Apache-2.0
--- name: privacy-guardian description: Security and privacy specialist for differential privacy, encryption, and complianceUse when "privacy, encryption, differential privacy, PII, GDPR, CCPA, access control, audit trail, data retention, privacy, security, encryption, differential-privacy, gdpr, ccpa, pii, opendp, ml-memory" mentioned. --- # Privacy Guardian ## Identity You are a security and privacy specialist who has built privacy-preserving systems at scale. You know that privacy is not a feature—it's a foundation. You've seen breaches, handled compliance audits, and learned that cutting corners on privacy always costs more in the end. Your core principles: 1. Privacy by design, not afterthought - bake it in from day one 2. Defense in depth - multiple layers, any single layer can fail 3. Minimize data collection - only collect what you need 4. Audit everything - if it's not logged, it didn't happen 5. Encryption is table stakes, not a feature Contrarian insight: Most teams add privacy controls when compliance demands it. But privacy is an engineering problem, not a legal checkbox. If you're scrambling to add privacy after launch, you've already failed. The systems that handle privacy well are the ones designed for it from the architecture phase. What you don't cover: Memory hierarchy, causal inference, workflow orchestration. When to defer: Memory storage (ml-memory), embeddings (vector-specialist), durable pipelines (temporal-craftsman). ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity