What it does
Inventories the cookies actually set by the site's active plugins and third-party scripts (analytics, ads, embeds), groups them into standard categories (necessary, functional, analytics, marketing), and writes the banner text plus per-category descriptions to paste into the consent plugin's admin screen.
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/cookie-consent-writer/ (or ~/.claude/skills/cookie-consent-writer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/cookie-consent-writer/
OpenAI Codex
.codex/skills/cookie-consent-writer/
Cursor
.cursor/skills/cookie-consent-writer/ (or ~/.cursor/skills/cookie-consent-writer/ globally)
Compatibility
Any WordPress site with a cookie consent plugin installed; a scan of the live site's actual set cookies gives the most accurate inventory.
The complete SKILL.md for this skill:
---
name: cookie-consent-writer
description: Use when a user needs the actual text for a cookie consent banner or preference center, not just a plugin installed with default placeholder copy.
---
# Cookie Consent Text Writer
## When to use
A cookie consent plugin is installed but still has generic placeholder text, and the user wants copy that accurately describes the cookies this specific site actually sets.
## Procedure
1. Inventory the cookies set by the site: check active plugins (analytics, ads, chat, embeds) and any third-party scripts loaded on the front end.
2. Categorize each cookie into the standard buckets: strictly necessary, functional, analytics/performance, marketing/advertising.
3. Write the top-level banner copy: a short, plain sentence explaining that cookies are used, with a link to the preference center, avoiding legal jargon.
4. Write a short description for each category that appears in the preference center, naming the actual purpose (e.g. "remembers items in your cart") rather than a vague generic line.
5. Note which categories can be toggled off by the visitor versus which are always-on (strictly necessary), matching what the consent tool actually enforces.
6. Flag any cookie whose purpose couldn't be confirmed from the plugin's documentation, and recommend the user verify it before publishing.
## Guardrails
- Never invent a cookie's purpose if it can't be confirmed, list it as "purpose unconfirmed, verify with plugin vendor" rather than guessing to fill out the category.
- Do not claim in the banner copy that consent is being properly enforced (blocking scripts until accepted) unless that behavior was actually verified on the live site.