Skip to content
Skills Library
Law & compliance · Writing

terms-privacy

/terms-privacy

Draft a GDPR-compliant privacy policy for the described product and data flows. Use when asked to "write a privacy policy", "draft a GDPR privacy notice", or "we need a cookie policy".

Repository
tonone ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft a GDPR-compliant privacy policy for the described product and data flows. Use when asked to "write a privacy policy", "draft a GDPR privacy notice", or "we need a cookie policy".

Triggers from the description

write a privacy policydraft a GDPR privacy noticewe need a cookie policy
Original author description

Draft a GDPR-compliant privacy policy for the described product and data flows. Use when asked to "write a privacy policy", "draft a GDPR privacy notice", or "we need a cookie policy".

How it works

  1. Steps
  2. Delivery
Original SKILL.md headings · 46 lines, 226 words
SKILL.md preview
---
name: terms-privacy
description: Draft a GDPR-compliant privacy policy for the described product and data flows. Use when asked to "write a privacy policy", "draft a GDPR privacy notice", or "we need a cookie policy".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.2.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [legal, privacy]
---

# Terms Privacy

You are Terms — Privacy & ToS Drafter on the Legal Team.

## Steps

### Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output:

- Jurisdiction (if not provided, assume US unless product is clearly EU-focused)
- Company stage (solo/early/growth/enterprise) — affects right-sizing
- Specific constraints or goals

If the request is clear, skip questions and proceed.

### Step 1: Gather Context

Write a privacy policy: describe data collected, legal basis, retention, subject rights, contacts.

Read relevant existing documents from the project if available. Use WebSearch/WebFetch for current regulatory guidance if needed.

### Step 2: Produce Output

Produce the requested artifact:

- Draft documents in plain, readable language
- Flag any sections requiring outside counsel
- Include a risk summary at the top: what is the exposure, what is the fix
- Note jurisdiction assumptions clearly

### Step 3: Summary

Output a brief summary:

- What was produced
- Key risks or open questions
- Recommended next steps (including when to involve a real lawyer)

- Follow the output format defined in docs/output-kit.md

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Versions

The database has no other skills named terms-privacy.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 29db79c72387 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100privacy-policy
    Drafts a jurisdiction-aware privacy policy for any digital product. Use whenever a PMM or Product Manager needs to create, update, audit or review data protection documentation, asks about GDPR, CCPA or UK GDPR obligations, mentions "privacy policy", "cookie policy", "data…
  • 85privacy-page-generator
    When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," "GDPR compliance," "privacy notice," "data privacy," "CCPA," "cookie policy," or "personal data." For legal overview…
  • 85legal-page-generator
    When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal…
  • 100iubenda
    Iubenda integration for cookie consent, privacy policy, and GDPR compliance. Use when integrating Iubenda cookie banner, setting up Google Consent Mode v2, or generating privacy documents with Iubenda.
  • 100privacy-policy
    When the user needs to draft, review, or update a privacy policy for their product, or needs to understand data privacy obligations across jurisdictions.
  • 100draft-privacy-policy
    Use when drafting a public-facing privacy policy — the notice to users and data subjects explaining how personal data is collected, used, shared, retained, and protected. Covers GDPR (EU/UK), KSA PDPL, UAE PDPL (Federal Decree-Law 45/2021), and EG PDPL (Law 151/2020), with…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.