ワンクリックでManusで任意のスキルを実行

create-privacy-policy-ch-en

スター3

フォーク1

更新日2026年3月15日 14:16

Creates a Swiss-law-compliant Datenschutzerklärung (Privacy Policy) for websites operated from Switzerland or targeting Swiss users. Guides the user through an interactive data-inventory phase covering all processing activities (hosting, fonts, analytics, contact forms, cookies, external embeds, etc.), then generates a ready-to-publish Privacy Policy in German and/or English. Covers obligations under nDSG (in force 01.09.2023), DSG Art. 19, and where relevant DSGVO (for EU visitors). Activate for phrases like: "create a privacy policy", "Datenschutzerklärung erstellen", "I need a privacy policy for my Swiss website", "nDSG privacy policy", "DSGVO Datenschutz", or "create privacy policy switzerland".

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

roebi

roebi/agent-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

弁護士法律職·SOC 23-1011

ファイルエクスプローラー

4 ファイル

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

session-git-lifecycle-en

roebi/agent-skills

Defines the git-based lifecycle for agent chat sessions: CREATE for new projects (git init with explicit main branch) and RESUME for continuing work from a delivered tar.gz containing a .git folder. Use this skill whenever an agent starts a new software project from scratch, or whenever a user provides a versioned tar.gz to continue work in a new or resumed session. Also covers the handover tag namespace convention (handover/vN) that keeps session delivery tags safely separated from software version tags (vX.Y.Z) used by GitHub Actions release workflows. Trigger phrases: "start new project", "new session", "resume project", "continue from tar", "here is myproject_vN.tar.gz", "untar and continue", "pick up where we left off", "add github actions release workflow".

2026-06-213

create-python-project-github-en

roebi/agent-skills

Scaffold a complete, modern Python project from scratch - from mkdir to first PyPI publish. Use this skill whenever the user wants to create a new Python package, library, CLI tool, or PyPI module, start a new Python open-source project, set up GitHub Actions CI/CD for Python, or asks how to structure a modern Python project with packaging, testing, and devcontainer. Also triggers for "new pypi module", "python project template", "python package from scratch", "hatch", "uv init", or any request to bootstrap a Python repo with best practices.

2026-06-023

create-file-tree-for-topic-en

roebi/agent-skills

Creates a topic-specific directory and file tree scaffold (Gerüst) as a starting point for a software solution or skill collection. Generates empty files, adds placeholder.txt in every empty directory so git tracks it, and writes a README.md in the root with metadata: topic, version, description, create timestamp (YYYYMMDD_HHMISS), creator, and license. Activate for phrases like: "create a file tree for", "scaffold a project for", "create directory structure for", "bootstrap a file scaffold", "Gerüst für", "starting point for", "create folder structure", or "new project skeleton".

2026-04-203

apply-tdd-loop-en

roebi/agent-skills

Applies the Test-Driven Development (TDD) cycle as an agentic loop of RED -> GREEN -> REFACTOR iterations until all requirements are covered or all existing code paths are tested. Use when a user or agent wants to write code strictly test-first, add missing tests to existing code, or drive a full TDD session for a module, class, or function. Activate for trigger phrases like: "apply TDD", "write this test-first", "do a TDD loop", "TDD cycle for", "drive TDD on", "red green refactor", or "add tests then implement".

2026-04-203

learn-topic-having-teacher-track-learning-progress

roebi/agent-skills

Acts as a knowledgeable Teacher that guides a learner through any topic using a structured 5-level learning plan, tracked in a living <topic>-learning-process.md file. Activate when the user says "teach me", "I want to learn", "explain step by step", "learning session", or asks to start a tutoring or teaching loop on any subject. The skill runs an interactive teach-ask-answer loop, evolving the progress file every iteration, until the learner types "learned".

2026-04-203

brainstorming-topic-dialog-creative-mentor-en

roebi/agent-skills

Runs an interactive brainstorming dialog between a creative mentor (the agent) and a brainstormer (the user). The mentor guides deep topic exploration through a growing idea-tree: the brainstormer defines 4 root perspectives (SWOT-style), then mentor and brainstormer alternately add creative branches each round until the brainstormer says "brainstormed". The session concludes with a downloadable <topic>-brainstorming-summary.md. Activate for phrases like: "brainstorm X", "help me brainstorm", "creative brainstorming session", "explore topic X with me", "brainstorming dialog", "mentor-led brainstorm", or "idea tree for X".

2026-03-173

name	create-privacy-policy-ch-en
license	CC BY-NC-SA 4.0
description	Creates a Swiss-law-compliant Datenschutzerklärung (Privacy Policy) for websites operated from Switzerland or targeting Swiss users. Guides the user through an interactive data-inventory phase covering all processing activities (hosting, fonts, analytics, contact forms, cookies, external embeds, etc.), then generates a ready-to-publish Privacy Policy in German and/or English. Covers obligations under nDSG (in force 01.09.2023), DSG Art. 19, and where relevant DSGVO (for EU visitors). Activate for phrases like: "create a privacy policy", "Datenschutzerklärung erstellen", "I need a privacy policy for my Swiss website", "nDSG privacy policy", "DSGVO Datenschutz", or "create privacy policy switzerland".
metadata	{"author":"roebi","spec":"https://agentskills.io/specification","skill-class":"one-step-process","crud-verb":"create","topic":"privacy-policy-ch","language":"en","jurisdiction":"CH","legal-basis":"nDSG Art. 19, DSG, DSGVO (where applicable)","related-skill":"create-impressum-ch-en"}

Create Privacy Policy CH

Generates a Swiss-law-compliant Datenschutzerklärung for a website, following the revised nDSG (in force since 01.09.2023) and, where the site targets EU visitors, the DSGVO (GDPR).

Disclaimer: This skill produces a best-effort legal text based on your inputs. It is not a substitute for advice from a Swiss lawyer. For commercial operations or sites processing sensitive data, review with a legal professional.

Swiss legal basis (quick reference)

Law	Relevance
nDSG Art. 19	Duty to inform data subjects at time of collection
nDSG Art. 5 lit. j	Definition of data controller (Verantwortlicher)
DSGVO Art. 13/14	Applies if site targets EU residents — stricter than nDSG
DSG Art. 12	Prohibition of unlawful data processing

Phase 1 — Operator identity

Ask the user:

"Do you already have an Impressum for this website created with create-impressum-ch-en? If yes, I can reuse the identity data directly."

If yes → import: name-full / company-name, address, email, website-url If no → collect same fields as Group B of create-impressum-ch-en

Phase 2 — Data processing inventory

Ask each group separately. Wait for answers before proceeding.

Group A — Hosting & infrastructure

"Where is your website hosted?" Examples: GitHub Pages, Netlify, Vercel, Hostpoint, AWS, own server

Store as hosting-provider and hosting-location (country/region if known).

GitHub Pages note: hosted on GitHub (Microsoft) servers, primarily USA. Netlify note: USA. Vercel note: USA. Swiss hosters: Hostpoint, Cyon = CH.

Group B — Web fonts

"Does your website load fonts from an external CDN?" Examples: Google Fonts, Adobe Fonts, Bunny Fonts, or self-hosted

Google Fonts loaded via <link> tag (standard):

Transfers visitor IP address to Google servers (USA) on every page load
Google privacy policy: https://policies.google.com/privacy
Basis: legitimate interest (Art. 6 DSGVO) / nDSG Art. 19
Mitigation option: self-host fonts (no external request)

Store as fonts-provider: google-fonts | adobe-fonts | bunny-fonts | self-hosted | none

Group C — Analytics & tracking

"Does your website use any analytics or tracking tools?" Examples: Google Analytics, Plausible, Fathom, Matomo, none

Tool	Data sent to	Cookies	Privacy-friendly
Google Analytics	Google (USA)	yes	no
Plausible	EU servers	no	yes
Fathom	EU/CA	no	yes
Matomo (self-hosted)	own server	optional	yes
None	—	—	✓

Store as analytics-tool and analytics-cookies: yes | no | none

Group D — Contact & forms

"How can visitors contact you? Does the site have any forms?" Examples: email link only, contact form, newsletter signup

Type	Data collected	Storage
Email link (mailto:)	none by the site	n/a
Contact form	name, email, message	server/email
Newsletter	email address	mailing list provider

Store as contact-method: email-only | contact-form | newsletter | none If form/newsletter: store form-provider (e.g. Formspree, Netlify Forms, Mailchimp)

Group E — External embeds & third-party services

"Does your website embed or link to any external services that load resources from third-party servers?" Examples: YouTube videos, Vimeo, Google Maps, Claude / AI links, social media buttons, GitHub badges, CDN scripts

Each embed that loads external resources must be disclosed. Claude.ai links (claude.ai/new?q=...) are regular hyperlinks — no data transfer from your server, user clicks voluntarily → no disclosure needed. cdnjs.cloudflare.com scripts → disclose Cloudflare CDN.

Store as embeds[]: list of services

Group F — Cookies

"Does your website set any cookies?"

Purely informational static sites with no analytics and no forms typically set zero cookies. Confirm:

No analytics → no tracking cookies
No login → no session cookies
No consent tool → no consent cookies

Store as uses-cookies: yes | no If yes: list name, purpose, duration, provider for each cookie.

Group G — EU visitors

"Does your website intentionally target visitors in the EU (e.g. German, French, Italian, Austrian audience)?"

If yes → DSGVO Art. 13 disclosure obligations apply in addition to nDSG. The generated policy will include DSGVO-compatible language.

Store as targets-eu: yes | no | unsure (treat as yes if unsure)

Group H — Language preference

"Should the Privacy Policy be in German only, English only, or both languages?"

Store as output-language: de | en | both

Phase 3 — Generate Privacy Policy

Using collected data, generate the policy using the templates in references/template-de.md and/or references/template-en.md.

Generation rules

Include only sections relevant to the actual processing activities found.
Do not include boilerplate sections for tools/services the site does not use.
Mark any missing data with [bitte ergänzen] / [please add].
For Google Fonts: always mention IP transfer to Google USA and link to Google Privacy Policy.
For GitHub Pages hosting: mention Microsoft/GitHub as processor, USA transfer.
If uses-cookies = no: include a short "No cookies" statement — users appreciate explicit confirmation.
If targets-eu = yes: add DSGVO Art. 13 rights block (access, erasure, portability, objection, supervisory authority).

Phase 4 — Deliver and advise

Present the generated Privacy Policy.
List any [bitte ergänzen] fields as a checklist.
Remind the user:

"Place this at /datenschutz or /privacy reachable within one click from every page. Link it from your footer next to the Impressum."
Mitigation tip for Google Fonts:

"To avoid disclosing Google Fonts IP transfers entirely, self-host your fonts. Download from https://google-webfonts-helper.herokuapp.com and serve from your own domain. Then remove the Google Fonts <link> tag."

Reference files

references/template-de.md — German Datenschutzerklärung template
references/template-en.md — English Privacy Policy template
references/processing-activities.md — Standard descriptions for common processing activities (hosting, fonts, analytics, forms)
references/rights-blocks.md — nDSG and DSGVO data subject rights blocks