C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Draft GDPR-compliant privacy notices for EU/EEA jurisdictions.
Install Privacy Notice Generator
$ npx skills add borghei/Claude-Skills --skill privacy-notice-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills privacy-notice-generator --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/legal/privacy-notice-generator .claude/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .claude/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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/borghei/Claude-Skills/tree/main/legal/privacy-notice-generatorType 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 borghei/Claude-Skills --skill privacy-notice-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills privacy-notice-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/legal/privacy-notice-generator .agents/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .agents/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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 borghei/Claude-Skills --skill privacy-notice-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills privacy-notice-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/legal/privacy-notice-generator .cursor/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .cursor/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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/borghei/Claude-Skills.git --path legal/privacy-notice-generator--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 borghei/Claude-Skills --skill privacy-notice-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills privacy-notice-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/legal/privacy-notice-generator .gemini/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .gemini/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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 borghei/Claude-Skills privacy-notice-generatorInstalls 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 borghei/Claude-Skills --skill privacy-notice-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/legal/privacy-notice-generator .github/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .github/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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 borghei/Claude-Skills --skill privacy-notice-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills privacy-notice-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/legal/privacy-notice-generator .opencode/skills/privacy-notice-generator && 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-notice-generator" agent skill from https://github.com/borghei/Claude-Skills/tree/main/legal/privacy-notice-generator into .opencode/skills/privacy-notice-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-notice-generator", 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-notice-generator- GitHub stars
- 891
- Token cost
- ~3.8k tokens
- SKILL.md length
- 1,190 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft GDPR-compliant privacy notices for EU/EEA jurisdictions.
- Works in 12 steps: Controller identity and contact → DPO contact details → Data categories collected → …
- Privacy notice drafting
- SKILL.md covers Table of Contents, Clarify First, Tools and Reference Guides, plus 6 more sections
- Runs Python scripts from its folder; calls python
What it does
Privacy Notice Generator is an agent skill from borghei/Claude-Skills. Draft GDPR-compliant privacy notices for EU/EEA jurisdictions. Supports 6 notice types, 9 jurisdictions, multi-layer compliance verification. Use for privacy notice drafting, compliance checking, and jurisdiction mapping.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/compliance_verification.md`, `references/jurisdiction_requirements.md` and `references/notice_types_guide.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Privacy notice drafting
- Compliance checking
- Jurisdiction mapping
Example prompts
- “/privacy-notice-generator”
Requirements
- Python 3
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Controller identity and contact
- DPO contact details
- Data categories collected
- Purposes and legal bases
- Recipients and categories
- International transfers
- Retention periods
- Data subject rights
- Right to withdraw consent
- Right to complain to SA
- Automated decision-making
- Cookies and tracking (if applicable)
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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 Notice Generator loads about 3.8k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 1,190 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 borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,190 words, ~3,783 tokens.
Download SKILL.mdSave it as
.claude/skills/privacy-notice-generator/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- privacy-notice-generator
- description
- Draft GDPR-compliant privacy notices for EU/EEA jurisdictions. Supports 6 notice types, 9 jurisdictions, multi-layer compliance verification. Use for privacy notice drafting, compliance checking, and jurisdiction mapping.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- The Glass Room
- metadata.category
- legal
- metadata.domain
- privacy-notice
- metadata.updated
- 2026-04-10
- metadata.tags
- privacy-notice, gdpr, data-protection, compliance, eu-privacy
⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.
Privacy Notice Generator
Tools and guidance for drafting GDPR-compliant privacy notices across EU/EEA jurisdictions and audience types, with multi-layer compliance verification.
Table of Contents
- Tools
- Reference Guides
- Workflows
- Troubleshooting
- Success Criteria
- Scope & Limitations
- Anti-Patterns
- Tool Reference
Clarify First
Before generating the notice, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Notice type — website, applicant, employee, b2b, b2c, or combined — selects which sections and audience-specific content appear (e.g. works council/monitoring for employee, Art. 14 source disclosure for b2b)
- Jurisdiction — DE/FR/AT/IT/ES/NL/BE/IE/UK — adds local requirements (DE Widerspruchsrecht/TDDDG, FR CNIL, UK ICO) that the compliance checker scores
- Legal basis per processing purpose — Art. 13(1)(c) requires a specific basis per purpose; a generic "applicable law" statement fails the check
- Special features: cookies / AI / international transfers — toggle sections 6, 12, and 13 and the AI Act Art. 50 transparency disclosures
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the notice.
Tools
Privacy Notice Scaffolder
Generates a privacy notice skeleton with all required sections pre-populated with jurisdiction-specific placeholders and legal references.
# Website privacy notice for German jurisdiction
python scripts/privacy_notice_scaffolder.py \
--notice-type website \
--jurisdiction DE \
--data-categories personal,contact,usage,cookies \
--legal-bases consent,contract,legitimate_interests \
--has-cookies \
--has-international-transfers
# Employee notice for French jurisdiction with AI processing
python scripts/privacy_notice_scaffolder.py \
--notice-type employee \
--jurisdiction FR \
--data-categories personal,employment,financial,health \
--legal-bases contract,legal_obligation,consent \
--has-ai
# B2C customer notice for UK with all features
python scripts/privacy_notice_scaffolder.py \
--notice-type b2c \
--jurisdiction UK \
--data-categories personal,contact,financial,usage,marketing \
--legal-bases consent,contract,legitimate_interests \
--has-cookies --has-ai --has-international-transfers \
--jsonSupported Notice Types:
| Type | Audience | Key Sections |
|---|---|---|
| website | Website/app visitors | Cookies, analytics, tracking technologies |
| applicant | Job applicants | Recruitment data, talent pool, retention periods |
| employee | Employees | Works council, IT monitoring, BYOD, HR data |
| b2b | Business partners | Art. 14 requirements, source disclosure |
| b2c | B2C customers | Soft opt-in, payment processing, loyalty |
| combined | Multiple audiences | Merged sections with audience-specific callouts |
Supported Jurisdictions: DE, FR, AT, IT, ES, NL, BE, IE, UK
13-Section Notice Structure:
- Controller identity and contact
- DPO contact details
- Data categories collected
- Purposes and legal bases
- Recipients and categories
- International transfers
- Retention periods
- Data subject rights
- Right to withdraw consent
- Right to complain to SA
- Automated decision-making
- Cookies and tracking (if applicable)
- AI processing (if applicable)
Notice Compliance Checker
Validates a privacy notice text against Art. 13/14 GDPR requirements and generates a compliance score with missing/incomplete elements.
# Check a privacy notice file
python scripts/notice_compliance_checker.py privacy_notice.md
# Check with jurisdiction-specific requirements
python scripts/notice_compliance_checker.py privacy_notice.md --jurisdiction DE
# Check with notice type for type-specific validation
python scripts/notice_compliance_checker.py privacy_notice.md \
--jurisdiction DE --notice-type employee
# JSON output
python scripts/notice_compliance_checker.py privacy_notice.md \
--jurisdiction FR --notice-type website --jsonChecks For:
| Category | Elements Checked |
|---|---|
| Art. 13 Mandatory | Controller identity, DPO contact, purposes, legal bases, recipients, transfers, retention, all 8 rights, automated decisions, consent withdrawal, SA complaint |
| Art. 14 Additional | Source of data, categories obtained (for indirect collection) |
| General | Art. 21 right to object prominence, plain language, no placeholders, consistent formatting |
| Jurisdiction-specific | DE: Widerspruchsrecht prominence, TDDDG; FR: CNIL recommendations; UK: ICO guidance |
Output:
- Compliance score (0-100)
- Missing elements (must-fix)
- Incomplete elements (should-improve)
- Jurisdiction-specific findings
- Type-specific findings
Reference Guides
Notice Types Guide
references/notice_types_guide.md
Detailed guidance for 6 notice types:
- Platform sub-types for website/app notices
- Applicant-specific data categories and retention
- Employee notice with works council and monitoring requirements
- B2B Art. 14 requirements and source disclosure
- B2C soft opt-in and payment processing
- Combined notice merge strategies
Jurisdiction Requirements
references/jurisdiction_requirements.md
Jurisdiction-specific requirements for 9 jurisdictions:
- SA details and registration requirements
- Requirements beyond GDPR baseline
- Standard wording recommendations
- Retention guidance per jurisdiction
Compliance Verification
references/compliance_verification.md
5-layer verification system:
- Jurisdiction-specific checks
- Art. 13/14 mandatory disclosures
- General compliance checks
- Type-specific checks
- AI Act compliance
- Post-generation checklist
- Writing style guide
Workflows
Workflow 1: SCOPE → INTAKE → DRAFT → VERIFY → DELIVER
Step 1: SCOPE — Determine notice parameters
→ Notice type (website/applicant/employee/b2b/b2c/combined)
→ Jurisdiction (DE/FR/AT/IT/ES/NL/BE/IE/UK)
→ Special features (cookies, AI, international transfers)
Step 2: INTAKE — Gather information
→ Controller identity and DPO
→ Data inventory (categories, sources)
→ Purposes and legal bases per category
→ Recipients and processors
→ Transfer destinations and mechanisms
→ Retention periods per category
→ Cookie/tracking inventory (if website)
→ AI processing details (if applicable)
Step 3: DRAFT — Generate notice skeleton
→ python scripts/privacy_notice_scaffolder.py [params]
→ Fill in placeholders with actual information from intake
→ Add jurisdiction-specific clauses
→ Apply writing style guide (you/your, short sentences, tables)
Step 4: VERIFY — Run compliance checker
→ python scripts/notice_compliance_checker.py notice.md --jurisdiction [J] --notice-type [T]
→ Address all missing elements
→ Address incomplete elements
→ Review jurisdiction-specific findings
Step 5: DELIVER — Finalize and publish
→ Legal review sign-off
→ Technical review (links, formatting, accessibility)
→ Translation QA (if multilingual)
→ Publication with version control
→ Set review trigger calendarWorkflow 2: Notice Update
Step 1: Identify trigger (new processing, regulation change, annual review)
Step 2: Run compliance checker on current notice
Step 3: Identify gaps and required updates
Step 4: Draft updated sections
Step 5: Re-verify with compliance checker
Step 6: Notify data subjects of material changes
Step 7: Update version date and change logWorkflow 3: Multi-Jurisdiction Notice
Step 1: Generate base notice for primary jurisdiction
→ python scripts/privacy_notice_scaffolder.py --jurisdiction [primary] ...
Step 2: Check jurisdiction requirements for additional territories
→ See references/jurisdiction_requirements.md
Step 3: Add jurisdiction-specific supplements
→ DE: TDDDG telecom disclosures, DSK guidance
→ FR: CNIL cookie requirements, LIL specifics
→ UK: ICO guidance, UK transfer mechanisms
Step 4: Verify each jurisdiction version
→ python scripts/notice_compliance_checker.py notice_de.md --jurisdiction DE
→ python scripts/notice_compliance_checker.py notice_fr.md --jurisdiction FR
Step 5: Publish with language/jurisdiction switcherTroubleshooting
| Problem | Possible Cause | Resolution |
|---|---|---|
| Low compliance score despite complete notice | Missing jurisdiction-specific requirements (e.g., DE Widerspruchsrecht prominence) | Run checker with --jurisdiction flag; review jurisdiction_requirements.md for local additions |
| Scaffolder generates too many sections | Combined notice type includes all audience sections | Use specific notice type instead of combined; or remove irrelevant sections post-generation |
| Art. 14 findings for direct collection | Checker flags Art. 14 requirements for B2B notice type | Correct — B2B often involves indirect collection; ensure source disclosure is included |
| Placeholder text in final notice | Template not fully populated | Search for [PLACEHOLDER] and {{variable}} markers; all must be replaced before publication |
| Cookie section missing from employee notice | Employee notice type does not include cookies by default | Add --has-cookies flag if employee-facing systems use cookies/tracking |
| AI section not generated | Missing --has-ai flag | Re-run scaffolder with --has-ai; review AI Act Art. 50 transparency requirements |
Show full SKILL.md (486 more words)Show less
Success Criteria
- 100% Art. 13/14 compliance score — all mandatory disclosure elements present; zero missing items
- Jurisdiction-specific requirements met — compliance checker confirms local SA requirements addressed
- Type-specific requirements met — notice covers all audience-specific data processing activities
- No placeholder text remaining — all template variables replaced with actual information
- Writing style guide followed — "you/your" voice; short sentences; tables for complex information; precise legal citations
- Legal review completed — qualified privacy counsel sign-off on final notice
- Publication requirements met — accessible, versioned, dated, with change notification mechanism
Scope & Limitations
In Scope:
- Privacy notice skeleton generation for 6 notice types across 9 jurisdictions
- Compliance checking against Art. 13/14 GDPR mandatory disclosures
- Jurisdiction-specific requirement validation (DE, FR, AT, IT, ES, NL, BE, IE, UK)
- Notice type-specific section generation and validation
- AI Act Art. 50 transparency disclosure sections
- Cookie and tracking technology disclosure sections
- Writing style and plain language guidance
Out of Scope:
- Legal advice on specific legal basis selection — consult qualified privacy counsel
- Translation services — tool generates English templates; professional translation required
- Cookie consent implementation or CMP configuration
- DPIA generation (see
dpia-assessmentskill) - Privacy notice hosting or publication infrastructure
- Non-GDPR privacy notice formats (CCPA notice at collection, LGPD notices)
- Sector-specific notices (healthcare, financial services, children's services)
Anti-Patterns
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Copy-paste from another company | Different processing activities, jurisdictions, and legal bases; exposes liability gaps | Generate skeleton from actual parameters; fill with organization-specific information |
| One notice for all jurisdictions | Misses jurisdiction-specific requirements (DE TDDDG, FR CNIL, UK ICO); SA enforcement | Generate jurisdiction-specific versions or supplements using scaffolder per jurisdiction |
| Generic legal bases ("we process your data based on applicable law") | Art. 13(1)(c) requires specific legal basis per purpose; generic statement is non-compliant | Map each processing purpose to specific Art. 6(1) basis; document in purpose-basis table |
| Set and forget | Processing activities change; regulations evolve; notices become inaccurate | Set review triggers (see compliance_verification.md); run compliance checker quarterly |
| Overly legalistic language | Recital 58 requires clear and plain language; complex legal jargon is non-compliant | Follow writing style guide: "you/your" voice, short sentences, tables, examples |
Tool Reference
privacy_notice_scaffolder.py
Generates a privacy notice skeleton based on notice type, jurisdiction, and processing parameters.
| Flag | Required | Description |
|---|---|---|
--notice-type <type> | Yes | Notice type: website, applicant, employee, b2b, b2c, combined |
--jurisdiction <code> | Yes | Jurisdiction: DE, FR, AT, IT, ES, NL, BE, IE, UK |
--data-categories <list> | Yes | Comma-separated: personal, contact, usage, cookies, financial, health, employment, marketing, biometric |
--legal-bases <list> | Yes | Comma-separated: consent, contract, legal_obligation, legitimate_interests, vital_interests, public_task |
--has-cookies | No | Include cookies and tracking section |
--has-ai | No | Include AI and automated processing section |
--has-international-transfers | No | Include international transfers section |
--json | No | Output in JSON format |
notice_compliance_checker.py
Validates a privacy notice against Art. 13/14 GDPR requirements.
| Flag | Required | Description |
|---|---|---|
<notice_file> | Yes | Path to privacy notice file (markdown or text) |
--jurisdiction <code> | No | Jurisdiction for local requirements: DE, FR, AT, IT, ES, NL, BE, IE, UK |
--notice-type <type> | No | Notice type for type-specific checks: website, applicant, employee, b2b, b2c, combined |
--json | No | Output in JSON format |
© borghei, 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 5 other files (scripts, references) in legal/privacy-notice-generator of borghei/Claude-Skills.
- SKILL.md
- references/compliance_verification.md
- references/jurisdiction_requirements.md
- references/notice_types_guide.md
- scripts/notice_compliance_checker.py
- scripts/privacy_notice_scaffolder.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Privacy Notice Generator 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 Notice Generator this skillborghei/Claude-Skills | 891 | — | ~3.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 borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Privacy Notice Generator
What does Privacy Notice Generator do?
Draft GDPR-compliant privacy notices for EU/EEA jurisdictions. Privacy Notice Generator is an agent skill from borghei/Claude-Skills. Draft GDPR-compliant privacy notices for EU/EEA jurisdictions.
When should I use Privacy Notice Generator?
Privacy Notice Generator fits situations like: privacy notice drafting; compliance checking; jurisdiction mapping.
How do I install Privacy Notice Generator in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill privacy-notice-generator -a claude-code`. Or copy the skill folder (legal/privacy-notice-generator in borghei/Claude-Skills) into .claude/skills/privacy-notice-generator in your project. Claude Code loads it when a task matches its description.
How do I install Privacy Notice Generator in Codex?
Run `npx skills add borghei/Claude-Skills --skill privacy-notice-generator -a codex`. Or copy the skill folder (legal/privacy-notice-generator in borghei/Claude-Skills) into .agents/skills/privacy-notice-generator in your project. Codex loads it when a task matches its description.
Can I use Privacy Notice Generator 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 borghei/Claude-Skills --skill privacy-notice-generator -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-notice-generator, .gemini/skills/privacy-notice-generator, .github/skills/privacy-notice-generator and .opencode/skills/privacy-notice-generator in your project.
What does Privacy Notice Generator need to run?
Going by SKILL.md and its folder, Privacy Notice Generator needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Privacy Notice Generator 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 Notice Generator 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 Privacy Notice Generator use?
Privacy Notice Generator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Privacy Notice Generator use?
About 3.8k tokens (SKILL.md is roughly 15k 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 13k tokens, read only when the agent opens those files.
What are the alternatives to Privacy Notice Generator?
Skills that share tags, products or a category with Privacy Notice Generator: 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 Notice Generator?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.