
Cookie Policy Page Generator
- 835 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
cookie-policy-page-generator is an agent skill that drafts transparent cookie policy pages aligned with GDPR, CCPA, and ePrivacy requirements for developers who must publish compliant tracking disclosures without engagin
About
cookie-policy-page-generator is an agent skill that helps developers publish cookie policy pages covering GDPR, CCPA, and ePrivacy obligations when a site uses analytics, advertising, or other tracking cookies. The skill produces compliant, transparent policy copy tailored to declared cookie categories and data practices rather than generic templates that omit jurisdiction-specific clauses. Reach for cookie-policy-page-generator when you are shipping a SaaS site, marketing property, or ecommerce storefront and need a cookie disclosure page before production traffic arrives. The output is ready-to-publish legal documentation content, not cookie-banner JavaScript or consent-management platform configuration.
- Maps every cookie your site actually sets including GA4, session, CSRF and preference cookies
- Determines notice vs consent banner requirements by jurisdiction and product type
- Produces ready-to-publish cookie policy page content with clear opt-out instructions
- Distinguishes between standalone cookie policy and integration into privacy policy
- Includes jurisdiction-specific language for EU, California and other regions
Cookie Policy Page Generator by the numbers
- 835 all-time installs (skills.sh)
- +10 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #522 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill cookie-policy-page-generatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 835 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
How do you write a compliant cookie policy page?
Generate compliant, transparent cookie policy pages that meet GDPR, CCPA and ePrivacy rules without hiring a lawyer.
Who is it for?
Developers shipping websites or SaaS products who must document cookie usage across GDPR, CCPA, and ePrivacy before launch.
Skip if: Engineering teams that need consent-banner implementation, cookie scanning automation, or full privacy-program legal review instead of policy page copy.
When should I use this skill?
A developer asks to generate, draft, or update a cookie policy page or mentions GDPR, CCPA, or ePrivacy cookie compliance copy.
What you get
Publishable cookie policy page copy with jurisdiction-specific disclosures and tracking-category documentation.
- cookie policy page copy
By the numbers
- Covers GDPR, CCPA, and ePrivacy regulatory frameworks in generated cookie policy pages
Files
SEO: Local
Guides local SEO: Google Business Profile, NAP consistency, and citation building. Businesses with accurate NAP across 40+ authoritative sites see ~19% higher visibility in Google Maps. Use this skill when optimizing for local search, setting up GBP, or auditing citations.
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
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 4 (Audience), 5 (Website).
Identify: 1. Business type: Storefront vs service-area 2. Location: Single or multiple 3. Current listings: Existing GBP, directories
NAP Consistency
NAP = Name, Address, Phone. Critical for local rankings.
| Rule | Guideline |
|---|---|
| Exact match | "Street" vs "St." or "LLC" inconsistency = Google may treat as different entities |
| Fix first | Audit and fix inconsistencies before adding new citations |
| Tools | BrightLocal, Whitespark, Moz Local for audit |
Google Business Profile
| Element | Guideline |
|---|---|
| Address | Physical address; no P.O. boxes |
| Description | 750 chars; primary keywords in first 100 |
| Hours | Accurate; seasonal availability |
| Category | Primary category matches business type |
| Service-area | Hide address if no storefront; define service areas |
Citation Building
Targeted precision over submitting to every directory.
Priority order: 1. Google Business Profile 2. Apple Maps 3. Yelp, Bing Places, Facebook 4. Better Business Bureau, Foursquare, Nextdoor 5. Niche directories (Healthgrades, Angi, etc.)
Citation Audit
- Incorrect or outdated data
- Duplicate entries
- Missing listings on key directories
Fix before adding; compounding errors harm rankings.
Output Format
- NAP (exact format for consistency)
- GBP optimization checklist
- Citation priority list
- Audit findings (if applicable)
Related Skills
- geo: GEO for AI search; local + AI overlap
- localization-strategy: Multilingual; local + i18n
- directory-submission: Directory listings; different from local citations
Related skills
How it compares
Use cookie-policy-page-generator for policy page copy; pair with consent-management tools when you also need banner UI and cookie blocking logic.
FAQ
Which regulations does cookie-policy-page-generator address?
cookie-policy-page-generator drafts cookie policy pages aligned with GDPR, CCPA, and ePrivacy requirements so developers can document tracking technologies and user rights for EU, California, and ePrivacy-covered deployments.
Does cookie-policy-page-generator implement cookie banners?
cookie-policy-page-generator produces policy page copy and regulatory disclosures; developers still need separate consent-banner or CMP tooling to manage opt-in UI and cookie blocking behavior.
Is Cookie Policy Page Generator safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.