/cookie-policy
When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
$ npx -y skills add kostja94/marketing-skills --skill cookie-policy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/cookie-policy
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
SKILL.md
cookie-policy.SKILL.mdname: cookie-policy-page-generator
description: When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
metadata:
version: 1.1.0
Pages: Cookie Policy
Guides cookie policy page content for transparency and regulatory compliance. Often presented as a standalone page or as part of the Privacy Policy.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
Identify: 1. **Cookie inventory**: List every cookie the site actually sets — check `_ga`, `_ga_*`, session cookies, CSRF tokens, preference cookies, ad cookies 2. **Consent requirement**: Does the site need a notice or a consent banner? See §Notice vs Consent 3. **Jurisdiction**: GDPR/ePrivacy (EU), CCPA (California), other regions 4. **Product category**: Free anonymous, freemium, SaaS, e-commerce — affects which cookies exist
---
Cookie Inventory: Common Patterns
Google Analytics 4 (GA4)
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_ga` | Analytics | Distinguishes users; used for aggregate usage measurement | 2 years | [GA opt-out browser add-on](https://tools.google.com/dlpage/gaoptout), block third-party cookies, or enable Do Not Track | | `_ga_<container-id>` | Analytics | Persists session state; used with `_ga` for session-level metrics | 2 years | Same as `_ga` |
**Disclosure requirement**: If the site uses Google Analytics, the cookie policy MUST list these cookies. GA ToS §7 requires posted privacy/cookie notice.
Functional / Session Cookies
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | Session ID | Essential | Maintains user session across page loads | Session (deleted on browser close) | Required for service; cannot be disabled | | CSRF Token | Essential | Prevents cross-site request forgery attacks | Session | Required for security; cannot be disabled | | Fair-use quota | Functional | Counts daily usage for rate limiting | 24 hours | Clear browser data; resets on next visit | | Language preference | Functional | Remembers user's language choice | 30 days – 1 year | Clear browser data | | Dark mode / theme | Functional | Remembers display preference | 30 days – 1 year | Clear browser data |
Advertising / Tracking Cookies (If Applicable)
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_fbp` | Marketing | Meta/Facebook pixel — tracks ad conversions | 90 days | [Meta ad preferences](https://www.facebook.com/ads/preferences) or block third-party cookies | | `_gcl_au` | Marketing | Google Ads conversion linker | 90 days | Block third-party cookies | | `_rdt_uuid` | Marketing | Reddit Ads conversion tracking | 90 days | Block third-party cookies |
---
Notice vs Consent — Critical Distinction
This is the most common compliance confusion. Determining which mechanism is needed depends on cookie type:
Cookie Notice (Informational)
**When to use**: Site uses only **strictly necessary** and **analytics** cookies (no advertising, no tracking, no third-party marketing cookies).
**What it is**: A banner or page section stating "We use cookies for [analytics/functionality]. By continuing, you accept this." No accept/reject toggle needed.
**Sufficient for**: GA4 analytics only, session cookies, CSRF tokens, functional preference cookies.
Cookie Consent Banner (Interactive)
**When to use**: Site uses **any** of: advertising cookies, third-party tracking cookies, social media pixels, or cookies that share data with ad networks.
**What it is**: An interactive banner with accept/reject/customize options. Must allow granular consent by cookie category. Must be as easy to reject as to accept. Must not use dark patterns (pre-checked boxes, confusing language, "accept all" only).
**Required for**: Meta pixel, Google Ads conversion tracking, retargeting cookies, any cross-site tracking.
Do Not Track (DNT)
State whether the site responds to browser DNT signals. Most sites do not, which is acceptable as long as disclosed. Example: "[Product] does not currently respond to Do Not Track signals because no uniform standard exists."
---
Essential Elements
1. What Are Cookies
Brief, plain-language explanation: "Cookies are small text files stored on your device by websites you visit. They help sites remember your preferences and understand how you use them."
2. Cookie Types Used
Categorize by function:
- **Essential / Strictly Necessary**: Required for the site to work (session, CSRF)
- **Functional**: Remember preferences (language, theme, fair-use quota)
- **Analytics / Performance**: Measure usage in aggregate (GA4)
- **Marketing / Advertising**: Track ad effectiveness, retargeting (if applicable)
3. Full Cookie Table
Table format for every cookie:
| Cookie Name | Type | Purpose | Duration | How to Opt Out | |-------------|------|---------|----------|----------------| | [name] | [essential/functional/analytics/marketing] | [1-sentence purpose] | [duration] | [specific actionable instruction] |
The **"How to Opt Out" column** is critical — don't just list cookies, tell users how to control them. This builds trust and satisfies regulatory expectations.
4. Third-Party Cookies
- Which third parties set cookies through the site (GA4, Meta, Stripe, etc.)
- Link to each third party's own privacy/cookie policy
- Whether those third parties use cookies for their own purposes
5. How to Manage Cookies
- Browser settings: link to instructions for Chrome,
Read more
name: cookie-policy-page-generator description: When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator. metadata: version: 1.1.0
Pages: Cookie Policy
Guides cookie policy page content for transparency and regulatory compliance. Often presented as a standalone page or as part of the Privacy Policy.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
Identify: 1. **Cookie inventory**: List every cookie the site actually sets — check `_ga`, `_ga_*`, session cookies, CSRF tokens, preference cookies, ad cookies 2. **Consent requirement**: Does the site need a notice or a consent banner? See §Notice vs Consent 3. **Jurisdiction**: GDPR/ePrivacy (EU), CCPA (California), other regions 4. **Product category**: Free anonymous, freemium, SaaS, e-commerce — affects which cookies exist
---
Cookie Inventory: Common Patterns
Google Analytics 4 (GA4)
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_ga` | Analytics | Distinguishes users; used for aggregate usage measurement | 2 years | [GA opt-out browser add-on](https://tools.google.com/dlpage/gaoptout), block third-party cookies, or enable Do Not Track | | `_ga_<container-id>` | Analytics | Persists session state; used with `_ga` for session-level metrics | 2 years | Same as `_ga` |
**Disclosure requirement**: If the site uses Google Analytics, the cookie policy MUST list these cookies. GA ToS §7 requires posted privacy/cookie notice.
Functional / Session Cookies
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | Session ID | Essential | Maintains user session across page loads | Session (deleted on browser close) | Required for service; cannot be disabled | | CSRF Token | Essential | Prevents cross-site request forgery attacks | Session | Required for security; cannot be disabled | | Fair-use quota | Functional | Counts daily usage for rate limiting | 24 hours | Clear browser data; resets on next visit | | Language preference | Functional | Remembers user's language choice | 30 days – 1 year | Clear browser data | | Dark mode / theme | Functional | Remembers display preference | 30 days – 1 year | Clear browser data |
Advertising / Tracking Cookies (If Applicable)
| Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_fbp` | Marketing | Meta/Facebook pixel — tracks ad conversions | 90 days | [Meta ad preferences](https://www.facebook.com/ads/preferences) or block third-party cookies | | `_gcl_au` | Marketing | Google Ads conversion linker | 90 days | Block third-party cookies | | `_rdt_uuid` | Marketing | Reddit Ads conversion tracking | 90 days | Block third-party cookies |
---
Notice vs Consent — Critical Distinction
This is the most common compliance confusion. Determining which mechanism is needed depends on cookie type:
Cookie Notice (Informational)
**When to use**: Site uses only **strictly necessary** and **analytics** cookies (no advertising, no tracking, no third-party marketing cookies).
**What it is**: A banner or page section stating "We use cookies for [analytics/functionality]. By continuing, you accept this." No accept/reject toggle needed.
**Sufficient for**: GA4 analytics only, session cookies, CSRF tokens, functional preference cookies.
Cookie Consent Banner (Interactive)
**When to use**: Site uses **any** of: advertising cookies, third-party tracking cookies, social media pixels, or cookies that share data with ad networks.
**What it is**: An interactive banner with accept/reject/customize options. Must allow granular consent by cookie category. Must be as easy to reject as to accept. Must not use dark patterns (pre-checked boxes, confusing language, "accept all" only).
**Required for**: Meta pixel, Google Ads conversion tracking, retargeting cookies, any cross-site tracking.
Do Not Track (DNT)
State whether the site responds to browser DNT signals. Most sites do not, which is acceptable as long as disclosed. Example: "[Product] does not currently respond to Do Not Track signals because no uniform standard exists."
---
Essential Elements
1. What Are Cookies
Brief, plain-language explanation: "Cookies are small text files stored on your device by websites you visit. They help sites remember your preferences and understand how you use them."
2. Cookie Types Used
Categorize by function:
- **Essential / Strictly Necessary**: Required for the site to work (session, CSRF)
- **Functional**: Remember preferences (language, theme, fair-use quota)
- **Analytics / Performance**: Measure usage in aggregate (GA4)
- **Marketing / Advertising**: Track ad effectiveness, retargeting (if applicable)
3. Full Cookie Table
Table format for every cookie:
| Cookie Name | Type | Purpose | Duration | How to Opt Out | |-------------|------|---------|----------|----------------| | [name] | [essential/functional/analytics/marketing] | [1-sentence purpose] | [duration] | [specific actionable instruction] |
The **"How to Opt Out" column** is critical — don't just list cookies, tell users how to control them. This builds trust and satisfies regulatory expectations.
4. Third-Party Cookies
- Which third parties set cookies through the site (GA4, Meta, Stripe, etc.)
- Link to each third party's own privacy/cookie policy
- Whether those third parties use cookies for their own purposes
5. How to Manage Cookies
- Browser settings: link to instructions for Chrome,
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

