Token导航 LogoToken导航

Agent Skill · 研究检索

privacy-notice-generator(隐私声明生成器)

privacy-notice-generator 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

privacy-notice-generator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 56,238。

总安装 461周安装 19GitHub Stars 103下载 150核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:privacy-notice-generator(隐私声明生成器)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/privacy-notice-generator
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill privacy-notice-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill privacy-notice-generator

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

privacy-notice-generator 用于查找、检索和筛选相关信息。适合在需要根据关键词或任务场景快速定位候选结果时使用。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围、维护状态及是否会触发联网或命令执行。

适用于 Codex、Claude、Cursor、Gemini CLI 等宿主环境。

来源仓库内路径:skills/privacy-notice-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/borghei/claude-skills --skill privacy-notice-g…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

privacy-notice-generator 怎么安装?

在终端执行 npx skills add https://github.com/borghei/claude-skills --skill privacy-notice-generator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

privacy-notice-generator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

privacy-notice-generator 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

privacy-notice-generator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

privacy-notice-generator 用的人多吗?

公开数据是累计安装 461 次,近一周安装 19 次,下载 150 次,GitHub 103 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

privacy-notice-generator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
privacy-notice-generator

隐私声明生成器 · 本页

461103只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

⚠️ 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

- Privacy Notice Scaffolder - Notice Compliance Checker


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 \
  --json

Supported Notice Types:

TypeAudienceKey Sections
websiteWebsite/app visitorsCookies, analytics, tracking technologies
applicantJob applicantsRecruitment data, talent pool, retention periods
employeeEmployeesWorks council, IT monitoring, BYOD, HR data
b2bBusiness partnersArt. 14 requirements, source disclosure
b2cB2C customersSoft opt-in, payment processing, loyalty
combinedMultiple audiencesMerged sections with audience-specific callouts

Supported Jurisdictions: DE, FR, AT, IT, ES, NL, BE, IE, UK

13-Section Notice Structure:

  1. Controller identity and contact
  2. DPO contact details
  3. Data categories collected
  4. Purposes and legal bases
  5. Recipients and categories
  6. International transfers
  7. Retention periods
  8. Data subject rights
  9. Right to withdraw consent
  10. Right to complain to SA
  11. Automated decision-making
  12. Cookies and tracking (if applicable)
  13. 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 --json

Checks For:

CategoryElements Checked
Art. 13 MandatoryController identity, DPO contact, purposes, legal bases, recipients, transfers, retention, all 8 rights, automated decisions, consent withdrawal, SA complaint
Art. 14 AdditionalSource of data, categories obtained (for indirect collection)
GeneralArt. 21 right to object prominence, plain language, no placeholders, consistent formatting
Jurisdiction-specificDE: 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 calendar

Workflow 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 log

Workflow 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 switcher

Troubleshooting

ProblemPossible CauseResolution
Low compliance score despite complete noticeMissing jurisdiction-specific requirements (e.g., DE Widerspruchsrecht prominence)Run checker with --jurisdiction flag; review jurisdiction_requirements.md for local additions
Scaffolder generates too many sectionsCombined notice type includes all audience sectionsUse specific notice type instead of combined; or remove irrelevant sections post-generation
Art. 14 findings for direct collectionChecker flags Art. 14 requirements for B2B notice typeCorrect — B2B often involves indirect collection; ensure source disclosure is included
Placeholder text in final noticeTemplate not fully populatedSearch for [PLACEHOLDER] and {{variable}} markers; all must be replaced before publication
Cookie section missing from employee noticeEmployee notice type does not include cookies by defaultAdd --has-cookies flag if employee-facing systems use cookies/tracking
AI section not generatedMissing --has-ai flagRe-run scaffolder with --has-ai; review AI Act Art. 50 transparency requirements

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-assessment skill)
  • 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-PatternWhy It FailsBetter Approach
Copy-paste from another companyDifferent processing activities, jurisdictions, and legal bases; exposes liability gapsGenerate skeleton from actual parameters; fill with organization-specific information
One notice for all jurisdictionsMisses jurisdiction-specific requirements (DE TDDDG, FR CNIL, UK ICO); SA enforcementGenerate 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-compliantMap each processing purpose to specific Art. 6(1) basis; document in purpose-basis table
Set and forgetProcessing activities change; regulations evolve; notices become inaccurateSet review triggers (see compliance_verification.md); run compliance checker quarterly
Overly legalistic languageRecital 58 requires clear and plain language; complex legal jargon is non-compliantFollow 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.

FlagRequiredDescription
--notice-type <type>YesNotice type: website, applicant, employee, b2b, b2c, combined
--jurisdiction <code>YesJurisdiction: DE, FR, AT, IT, ES, NL, BE, IE, UK
--data-categories <list>YesComma-separated: personal, contact, usage, cookies, financial, health, employment, marketing, biometric
--legal-bases <list>YesComma-separated: consent, contract, legal_obligation, legitimate_interests, vital_interests, public_task
--has-cookiesNoInclude cookies and tracking section
--has-aiNoInclude AI and automated processing section
--has-international-transfersNoInclude international transfers section
--jsonNoOutput in JSON format

notice_compliance_checker.py

Validates a privacy notice against Art. 13/14 GDPR requirements.

FlagRequiredDescription
<notice_file>YesPath to privacy notice file (markdown or text)
--jurisdiction <code>NoJurisdiction for local requirements: DE, FR, AT, IT, ES, NL, BE, IE, UK
--notice-type <type>NoNotice type for type-specific checks: website, applicant, employee, b2b, b2c, combined
--jsonNoOutput in JSON format

平台分布

Codex

39.39%
按下载量换算59

Claude

29.47%
按下载量换算44

Cursor

19.35%
按下载量换算29

Gemini CLI

8.57%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills