cookie-policy-malik-taiar
Guide for drafting cookie policies compliant with GDPR and the ePrivacy Directive. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a cookie policy for a website or application.
Best use case
cookie-policy-malik-taiar is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guide for drafting cookie policies compliant with GDPR and the ePrivacy Directive. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a cookie policy for a website or application.
Teams using cookie-policy-malik-taiar should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/politique-cookies-malik-taiar/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cookie-policy-malik-taiar Compares
| Feature / Agent | cookie-policy-malik-taiar | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guide for drafting cookie policies compliant with GDPR and the ePrivacy Directive. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a cookie policy for a website or application.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cookie Policy Guide ## Overview A cookie policy informs users about cookies and trackers placed on their device. It is distinct from the privacy policy but can be integrated into it. It must comply with CNIL 2020 guidelines. ### Cookie Policy Objectives | Objective | Requirement | |-----------|-------------| | **Transparency** | Inform about cookies used and their purposes | | **Consent** | Obtain free, informed, and prior consent | | **Control** | Allow users to manage their preferences | | **Compliance** | Comply with GDPR + ePrivacy + CNIL recommendations | --- ## Reference Resources ### Template | Template | Description | |----------|-------------| | `assets/sample_template_politique_cookies.docx` | Default template to use if no private template is provided | | Internal template provided by lawyer | Use if the lawyer has a more suitable private template | ### CNIL Documentation | PDF File to READ (Read tool) | URL to CONSULT (WebFetch tool) | Topic | |------------------------------|--------------------------------|-------| | `assets/CNIL_lignes_directrices_cookies_et_traceurs.pdf` | - | Cookie guidelines | | `assets/CNIL_recommandation_cookies_et_traceurs.pdf` | https://www.cnil.fr/fr/cookies-et-autres-traceurs/regles/cookies | Cookie recommendations | | `assets/CNIL_faq_cookies_et_traceurs.pdf` | https://www.cnil.fr/fr/cookies-et-autres-traceurs/regles/cookies/FAQ | Cookie FAQ | | `assets/CNIL_evolution_regles_utilisation_cookies.pdf` | https://www.cnil.fr/fr/evolution-des-regles-dutilisation-des-cookies-quels-changements-pour-les-internautes | Rules evolution | | `assets/CNIL_transparence.pdf` | - | Guide on information and transparency | | `assets/CNIL_principes_rgpd.pdf` | - | Fundamental GDPR principles | | `assets/RGPD_texte_officiel.pdf` | - | Full text of EU Regulation 2016/679 | > **REQUIREMENT**: For ANY information regarding cookies, consent, retention periods, exemptions, or best practices: > 1. **READ the PDF files** with the Read tool BEFORE responding on a regulatory point > 2. **CONSULT the online URLs** with WebFetch to verify the most current information > 3. **CITE the CNIL URL** in your response when mentioning a rule or duration > 4. **NEVER invent** a duration or rule without verifying it in the sources ### Knowledge Base | Document | Content | |----------|---------| | **[COOKIES.md](references/COOKIES.md)** | Cookie categories, banners, CNIL sanctions, retention periods | | **[BASES_LEGALES_COOKIES.md](references/BASES_LEGALES_COOKIES.md)** | Cookie-specific legal bases (consent, exemptions) | | **[DROITS_PERSONNES.md](references/DROITS_PERSONNES.md)** | Data subject rights | | **[DUREES_CONSERVATION.md](references/DUREES_CONSERVATION.md)** | Retention periods (6 months recommended by CNIL for consent, 13 months max) | --- ## Information to Collect from Client > **IMPORTANT**: Before drafting the policy, collect the information below. ### 1. Website Publisher Information - [ ] Full company name - [ ] Legal form (SAS, SARL, Ltd, etc.) - [ ] Registered office address - [ ] Contact email - [ ] Website URL ### 2. Cookies Used STRICTLY NECESSARY COOKIES (exempt from consent) - [ ] Session cookie - [ ] Authentication cookie - [ ] Shopping cart cookie - [ ] Security cookie (CSRF) - [ ] Language preference cookie - [ ] Cookie choice remembrance cookie ANALYTICS COOKIES - [ ] Google Analytics - [ ] Matomo - [ ] AT Internet - [ ] Other: ___________ ADVERTISING / MARKETING COOKIES - [ ] Google Ads - [ ] Facebook Pixel - [ ] LinkedIn Insight Tag - [ ] Criteo - [ ] Other: ___________ SOCIAL MEDIA COOKIES - [ ] Facebook share buttons - [ ] Twitter/X share buttons - [ ] LinkedIn share buttons - [ ] Embedded YouTube videos - [ ] Other: ___________ FUNCTIONALITY COOKIES - [ ] Live chat (e.g., Intercom, Crisp) - [ ] Video player - [ ] Interface personalization - [ ] Other: ___________ ### 3. Consent Management Platform (CMP) - [ ] None - [ ] Axeptio - [ ] Didomi - [ ] Cookiebot - [ ] OneTrust - [ ] Other: ___________ ### 4. Retention Periods > **READ CNIL SOURCE**: `assets/CNIL_recommandation_cookies_et_traceurs.pdf` + https://www.cnil.fr/fr/cookies-et-autres-traceurs/regles/cookies > **IMPORTANT**: CNIL recommends **6 months** for the consent cookie. Use 6 months as default. | Cookie | CNIL Recommended Duration | Maximum Duration | |--------|---------------------------|------------------| | Consent cookie | 6 months | 13 months | | Analytics cookies | Depending on purpose | 13 months | | Advertising cookies | Depending on purpose | 13 months | --- ## Drafting Workflow ### Step 1: Template Selection (MANDATORY) > **NEVER DRAFT A POLICY FROM SCRATCH.** > Always start from a given template for drafting, either: > - the default template in `assets/sample_template_politique_cookies.docx`; > - another internal template provided by the user. > > This template is your base reference. You must: > - **Faithfully reproduce the template's structure and wording** > - **Keep the exact template phrasing** (they are validated) > - **Only replace placeholders** with client information > - **Do NOT rewrite sentences** even if you think you can phrase them better > - **Do NOT add sections** that are not in the template > > The collected information (cookies used, CMP, etc.) is used to **fill in** the template, **not to rewrite it**. **1. FIRST ACTION: Confirm the template to use BEFORE any drafting. Ask the user:** ``` "I will draft the cookie policy starting from the provided default template. Do you have an internal template that would be more suitable as a starting point?" ``` | Option | Action | |--------|--------| | Default template | Use `assets/sample_template_politique_cookies.docx` | | Internal template | Use the document provided by the lawyer | **2. Consider the user's choice and select the starting template.** --- ### Step 2: Understand the Site and Cookies Used > **MAIN OBJECTIVE**: Precisely identify all cookies placed by the site. **1. Ask the lawyer for available information:** ``` "To draft a perfectly tailored cookie policy, please provide: - The website URL - The list of cookies used (if known) - The consent management platform (CMP) used - Third-party tools integrated (analytics, advertising, social media...) - Any existing documentation about the site's cookies You may anonymize this information if necessary for confidentiality reasons. The more information you provide, the better adapted the policy will be. Otherwise, we will conduct our own research but it will be limited to publicly accessible information." ``` **2. Research on the site (if accessible):** - Visit the site and observe the cookie banner - Identify the CMP used - List visible cookies (via browser tools) - Note third-party integrations (YouTube, social media, analytics...) - Read the existing cookie policy (if present) **3. Summary before drafting:** ``` SITE: [URL] CMP USED: [Solution name] STRICTLY NECESSARY COOKIES: [List] ANALYTICS COOKIES: [List + providers] ADVERTISING COOKIES: [List + providers] SOCIAL MEDIA COOKIES: [List + providers] FUNCTIONALITY COOKIES: [List] RETENTION PERIODS: [Compliant with 13 months max?] KEY LAWYER POINTS: [What must absolutely be included] ``` > Once the summary is ready → Proceed to Draft 1. --- ### Step 3: Draft 1 > **ABSOLUTE RULE**: The reference template is your validated base. > > - **START from the template**: structure, wording, tone → this is your reference > - **ADAPT to the client case**: integrate the specific cookies identified > - **DO NOT rewrite everything**: keep the template wording, only adapt what needs to be > > In summary: Template + client cookies = Draft 1. Not a complete rewrite. Complete the template section by section: 1. **What is a cookie?** (definition) 2. **Who places cookies?** (publisher + third parties) 3. **Strictly necessary cookies** (detailed table) 4. **Analytics cookies** (table + purposes) 5. **Advertising cookies** (table + purposes) 6. **Social media cookies** (table + purposes) 7. **How to manage your preferences?** (banner + browser) 8. **Retention period** 9. **Policy updates** 10. **Contact** > **Immediate compliance check:** Before presenting Draft 1, verify the cookie compliance checklist (CNIL 2020): > - [ ] Exhaustive list of cookies with name, provider, duration, purpose > - [ ] Distinction between necessary cookies vs cookies requiring consent > - [ ] Information that refusing is as easy as accepting > - [ ] Retention periods ≤ 13 months > - [ ] Clear explanation of how the banner works > - [ ] Instructions for managing cookies via browser > - [ ] Link to CMP to modify preferences > - [ ] Document update date > - [ ] Contact for questions > > If Draft 1 is compliant → Proceed to Step 3. --- ### Step 4: Deliver Draft 1 + Benchmark + Improvement Suggestions **1. Deliver Draft 1 with explanation:** ``` "Here is Draft 1 of the cookie policy. **What I took into account:** - [List of identified cookies] - [CMP used] - [Retention periods] **Compliance:** The document complies with CNIL 2020 guidelines." ``` **2. Present the benchmark (systematic):** Research 3-5 cookie policies from companies in the same sector, then present: ``` "**Benchmark conducted:** I analyzed the cookie policies of: - [Company 1] - [what we noted] - [Company 2] - [what we noted] - [Company 3] - [what we noted] **Identified possible improvements:** - [Improvement 1]: [explanation] - [Improvement 2]: [explanation] Would you like to incorporate these elements into the provided Draft?" ``` **3. If the lawyer approves improvements → Produce Draft 2** --- ### Step 5: Final Verification Final review before definitive delivery: - [ ] All site cookies are listed - [ ] Distinction between necessary / consent-required respected - [ ] Retention periods ≤ 13 months - [ ] Clear management instructions (banner + browser) - [ ] No internal references in final document - [ ] Update date present --- ## CNIL Reference Sanctions | Company | Amount | Reason | |---------|--------|--------| | Google | €150M | Refusing cookies more difficult than accepting | | Facebook | €60M | No visible "reject all" button | | Amazon | €35M | Cookies placed without prior consent | | Microsoft | €60M | Cookies placed without consent | > These sanctions illustrate the importance of a compliant cookie policy and a banner respecting the principle that refusing must be as easy as accepting. --- ## Common Mistakes to Avoid | Mistake | Potential Sanction | Solution | |---------|-------------------|----------| | Cookies placed before consent | Fine | Wait for "Accept" click | | No visible "Reject" button | Fine | Button at same level as "Accept" | | Strict cookie wall | Fine | Offer an alternative | | Duration > 13 months | Formal notice | Respect maximum duration | | No cookie list | Non-compliance | Detailed table required | | Dark patterns | Fine | Neutral and clear design | | Incomplete cookie list | Non-compliance | Complete site audit | --- ## Using This Guide 1. **Step 1 - Choose the template**: Default reference template, or lawyer's internal template 2. **Step 2 - Identify cookies**: Collect lawyer info + site analysis 3. **Step 3 - Draft Draft 1**: Complete template + compliance check 4. **Step 4 - Deliver + Benchmark**: Present Draft 1 + systematic benchmark + improvement suggestions 5. **Step 5 - Finalize**: Integrate approved improvements + final verification > **TEMPLATE REMINDER**: Never draft from scratch. Always start from the reference template and adapt it. > **DURATION REMINDER**: CNIL recommends **6 months** for the consent cookie (13 months max). Always verify in CNIL sources before mentioning a duration.
Related Skills
whistleblower-policy-malik-taiar
Guide for (a) auditing an existing whistleblower system or (b) drafting a compliant reporting policy from a provided template. Covers EU Directive 2019/1937, the amended Sapin II law (Waserman 2022), Decree 2022-1284, CNIL guidelines, public sector requirements, and duty of vigilance.
privacy-policy-malik-taiar
Guide for drafting privacy policies compliant with GDPR. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a privacy policy for a website or application.
xlsx-processing-openai
Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.
xlsx-processing-manus
Professional Excel spreadsheet creation with a focus on aesthetics and data analysis. Use when creating spreadsheets for organizing, analyzing, and presenting structured data in a clear and professional format.
xlsx-processing-anthropic
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
vscode-extension-builder-lawvable
Build VS Code extensions from scratch or convert existing JS/React/Vue apps. Supports commands, webviews (React/Vue), custom editors, tree views, and AI agent integration via file-bridge IPC. Use when user wants to create a VS Code extension, convert a web app to an extension, add webviews or custom UIs to VS Code, implement tree views, build custom file editors, integrate with AI agents, or package/publish extensions (.vsix).
vendor-due-diligence-patrick-munro
Framework for assessing IT service providers, technology vendors, and third-party partners. Creates structured risk assessments across financial, operational, compliance, security, and reputational dimensions with regulatory checklists (GDPR, DORA, NIS2, SOX). Use when: (1) Evaluating new vendors or technology providers, (2) Conducting third-party risk assessments for procurement, (3) Performing critical vendor due diligence for regulatory compliance, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring processes, (6) Assessing vendor concentration risk, or (7) Generating executive-level vendor risk reports.
tech-contract-negotiation-patrick-munro
Guide to negotiating technology services agreements, professional services contracts, and commercial B2B transactions. Provides three-position frameworks (provider-favorable, balanced, client-favorable), deal-size tactics, objection handling templates, and concession roadmaps. Use when: (1) Developing negotiation strategies for SaaS, cloud, or managed services agreements, (2) Preparing position papers and fallback positions, (3) Responding to counterparty objections and demands, (4) Creating concession roadmaps that protect critical interests, (5) Assessing tactics based on deal value and leverage, or (6) Structuring balanced outcomes for liability, IP, payment, SLA, or warranty provisions.
tabular-review-lawvable
Guide to analyze multiple documents (PDF, DOCX) against user-defined columns and produce a structured Excel output with citations. Use when the user wants to: (1) Extract specific information from multiple documents into a table, (2) Compare clauses or provisions across contracts, (3) Create a document review matrix with source citations. Triggers on: 'tabular review', 'document matrix', 'extract from documents', 'compare across documents', 'review multiple contracts'.
statute-analysis-rafal-fryc
Guide for reading, interpreting, and applying statutes, regulations, and rules in legal and compliance contexts. Use when the user asks about (1) how to read and interpret statutes, regulations, or rules, (2) statutory interpretation methods and canons of construction, (3) understanding legislative intent, (4) applying statutes to specific legal situations, (5) extracting requirements from legal text, (6) distinguishing between different types of legal requirements, or (7) cross-jurisdictional compliance analysis.
skill-optimizer-lawvable
Guide to analyze a current work session and propose improvements to skills. Use (1) automatically after working with a skill to capture learnings, (2) when the user suggests improvements, corrections, or additions during a skill-related session, or (3) when the user manually invokes `self-improve`.
skill-creator-openai
Guide for creating effective skills. Use when users want to create a new skill (or update an existing skill) that extends the model's capabilities with specialized knowledge, workflows, or tool integrations.