What it does
Audits active plugins (forms, analytics, ecommerce, comments, membership) and theme features to build an actual list of what personal data is collected, how it is stored, and which third parties receive it, then drafts the policy section by section against that real list instead of starting from a generic template.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/privacy-policy-writer/ (or ~/.claude/skills/privacy-policy-writer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/privacy-policy-writer/
OpenAI Codex
.codex/skills/privacy-policy-writer/
Cursor
.cursor/skills/privacy-policy-writer/ (or ~/.cursor/skills/privacy-policy-writer/ globally)
Compatibility
Any WordPress site; benefits from a list of active plugins and any third-party services (analytics, payment processors, email marketing) in use.
The complete SKILL.md for this skill:
---
name: privacy-policy-writer
description: Use when a user needs a privacy policy page written or updated, especially after adding a new plugin or service that collects visitor or customer data.
---
# Privacy Policy Writer
## When to use
The site needs a privacy policy that actually matches what it does, either drafted from scratch or updated after a new data-collecting plugin or service (analytics, forms, ecommerce) was added.
## Procedure
1. Audit active plugins and integrations for anything that collects personal data: contact forms, analytics, ecommerce/checkout, comments, membership/login systems, chat widgets.
2. For each one, note what data is collected (name, email, IP, payment details, behavioral data), where it's stored, and whether it's shared with a third party (e.g. an analytics provider or payment processor).
3. Draft policy sections only for data types and practices that actually apply to the site, skip generic categories that don't exist here.
4. Include sections on data retention, user rights (access, deletion, correction) at a level appropriate to the site's actual audience and jurisdiction, if known.
5. Flag any section touching specific legal obligations (children's data, health data, cross-border transfers) as needing a lawyer's review before publishing.
6. Present the draft with a short list of the plugins/services it was based on, so the user can catch anything missed.
## Guardrails
- Never state a legal conclusion (that the site is "fully GDPR compliant" or similar) as fact, this is a draft for review, not a substitute for legal advice.
- If a data-collecting plugin's actual behavior can't be confirmed, note the assumption explicitly rather than silently guessing at what it does with the data.