C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences.
Install Cnil Cookie Banner
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-banner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .claude/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .claude/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-bannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-banner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .agents/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .agents/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-banner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .cursor/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .cursor/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/cnil-cookie-banner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-banner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .gemini/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .gemini/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-bannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .github/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .github/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cnil-cookie-banner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/cnil-cookie-banner .opencode/skills/cnil-cookie-banner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cnil-cookie-banner" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cnil-cookie-banner into .opencode/skills/cnil-cookie-banner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cnil-cookie-banner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cnil-cookie-banner- GitHub stars
- 301
- Token cost
- ~2.8k tokens
- SKILL.md length
- 887 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences.
- Works in 5 steps: Equal Prominence for Accept and Reject → No Cookie Walls → Granular Purpose-Level Consent → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, CNIL Cookie Banner Requirements, Technical Implementation and CNIL Enforcement Precedents, plus 1 more section
- Runs Python scripts from its folder
What it does
Cnil Cookie Banner is an agent skill from mukul975/Privacy-Data-Protection-Skills. Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences. References the EUR 100M Google LLC fine and EUR 150M Meta Platforms fine for non-compliant cookie practices. Covers equal prominence, reject-all buttons, cookie walls prohibition, and 6-month reconsent cycles.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “/cnil-cookie-banner”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cnil Cookie Banner loads about 2.8k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 887 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 887 words, ~2,754 tokens.
Download SKILL.mdSave it as
.claude/skills/cnil-cookie-banner/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cnil-cookie-banner
- description
- Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences. References the EUR 100M Google LLC fine and EUR 150M Meta Platforms fine for non-compliant cookie practices. Covers equal prominence, reject-all buttons, cookie walls prohibition, and 6-month reconsent cycles.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- cookie-consent-compliance
- metadata.tags
- cnil, cookie-banner, french-privacy, google-fine, meta-fine, cookie-wall
CNIL-Compliant Cookie Banner Implementation
Overview
The Commission Nationale de l'Informatique et des Libertés (CNIL) enforces some of the strictest cookie consent requirements in the EU. Following its updated guidelines (Deliberation No. 2020-091 of 17 September 2020) and landmark enforcement actions — including the EUR 100 million fine against Google LLC and EUR 50 million against Google Ireland Limited (31 December 2021), and the EUR 60 million fine against Meta Platforms Ireland Limited (31 December 2022, later increased in subsequent actions totaling EUR 150 million across multiple decisions) — organizations serving French users must implement cookie banners meeting specific design and functional requirements.
CNIL Cookie Banner Requirements
1. Equal Prominence for Accept and Reject
The CNIL requires that the mechanism to refuse cookies must be as easy to use as the mechanism to accept them. This was the central issue in the Google and Meta enforcement actions — both companies provided a prominent "Accept All" button but required multiple clicks to reject cookies.
Compliant Design for Pinnacle E-Commerce Ltd:
+------------------------------------------------------------------+
| Pinnacle E-Commerce uses cookies |
| |
| We use cookies to improve your shopping experience, analyse |
| site traffic, and personalise content. You can accept all |
| cookies, reject non-essential cookies, or customise your |
| choices. |
| |
| [Accept All] [Reject All] [Customise] |
| |
| Privacy Policy | Cookie Policy |
+------------------------------------------------------------------+Design Rules:
- "Accept All" and "Reject All" buttons must have identical visual weight: same size, same font, same color scheme, same position hierarchy
- Neither button may use dark patterns (e.g., bright color for accept, grey for reject)
- A "Customise" or "Manage Preferences" option must also be available at the same level
- The banner must not use manipulative language ("Accept for the best experience" vs. neutral "Reject All")
2. No Cookie Walls
Under CNIL guidelines, access to the website must not be conditioned on accepting cookies. Cookie walls — where content is blocked until the user accepts all cookies — are prohibited.
Prohibited Implementation:
+------------------------------------------------------------------+
| To access Pinnacle E-Commerce, please accept our cookies. |
| |
| [Accept All Cookies] |
+------------------------------------------------------------------+Compliant Alternative: The site must be fully functional (at minimum, browsable) when the user clicks "Reject All." Essential cookies for cart functionality, authentication, and security may still be set under the strictly necessary exemption.
3. Granular Purpose-Level Consent
The customisation layer must allow users to consent to each purpose individually:
Layer 2 — Customise Preferences:
+------------------------------------------------------------------+
| Manage your cookie preferences |
| |
| Strictly Necessary [Always Active] |
| Required for the site to function (cart, security, login). |
| These cannot be disabled. |
| |
| Analytics [Toggle OFF] |
| Help us understand how visitors use the site to improve our |
| services. Data is aggregated and anonymised. |
| Partners: Google Analytics |
| |
| Advertising [Toggle OFF] |
| Used to show you relevant advertisements on other websites. |
| Partners: Meta, Google Ads |
| |
| Functionality [Toggle OFF] |
| Remember your preferences such as language and currency. |
| |
| [Confirm My Choices] [Accept All] [Reject All] |
+------------------------------------------------------------------+Rules for Layer 2:
- All non-essential toggles default to OFF (no pre-ticked consent)
- Each category lists specific third-party partners by name
- "Confirm My Choices" saves the current toggle state
- "Accept All" and "Reject All" remain available at this level too
4. Consent Validity and Reconsent
CNIL recommends that consent be renewed at regular intervals:
| Parameter | CNIL Requirement |
|---|---|
| Maximum consent validity | 6 months (CNIL recommendation) |
| Refusal retention | 6 months before re-prompting |
| Consent proof retention | Duration of consent + applicable statute of limitations |
| Re-prompt after consent expiry | Banner must reappear automatically |
| Re-prompt after cookie policy change | Mandatory — new consent required |
Implementation for Pinnacle E-Commerce Ltd:
Store the consent timestamp in a first-party cookie:
cookie_consent_timestamp=2026-01-15T10:30:00Z
cookie_consent_version=v2.3
cookie_consent_state=accepted_analytics|rejected_advertising|accepted_functionalityOn each page load, check:
- Does
cookie_consent_timestampexist? - Is it less than 6 months old?
- Does
cookie_consent_versionmatch the current cookie policy version?
If any check fails, redisplay the banner.
5. No Deceptive Design Patterns
CNIL specifically prohibits the following dark patterns:
| Dark Pattern | Description | Why Prohibited |
|---|---|---|
| Asymmetric buttons | Accept is large/colorful, reject is small/grey | Unequal prominence violates equal ease requirement |
| Hidden reject | Reject option buried in settings layers | Must be at same level as accept |
| Confusing toggles | Toggle visually suggests ON when it is OFF | Undermines informed consent |
| Guilt-tripping | "By rejecting, you'll miss personalised offers" | Manipulative language |
| Pre-selected purposes | Analytics or functionality toggles pre-enabled | Violates active consent requirement (Planet49) |
| Repeated prompting | Re-showing banner on every page after rejection | Coercion; must respect refusal for 6 months |
Show full SKILL.md (328 more words)Show less
Technical Implementation
Banner Loading Behavior
- No cookies before consent: Non-essential cookies must not be set before the user interacts with the banner. Tags must be blocked at the container level.
- Synchronous banner load: The consent banner must load before any tag management scripts execute.
- Server-side enforcement: Consent state should be validated server-side for requests that trigger cookie setting.
Tag Blocking Architecture
Page Load
│
├── Load consent banner script (synchronous)
│
├── Check consent state cookie
│ ├── No consent recorded → Show banner, block all non-essential tags
│ ├── Consent expired (>6 months) → Show banner, block all non-essential tags
│ ├── Consent recorded → Parse consent state
│ ├── Analytics accepted → Fire GA4 tags
│ ├── Advertising accepted → Fire Meta Pixel, Google Ads tags
│ └── Functionality accepted → Fire preference cookies
│
└── User interacts with banner
├── Accept All → Set all tags, store consent
├── Reject All → Block all non-essential tags, store refusal
└── Customise → Show Layer 2, await per-purpose selectionConsent Storage
Store consent proof with the following minimum fields:
| Field | Value |
|---|---|
| Consent ID | UUID per consent event |
| User identifier | Pseudonymised user ID or cookie ID |
| Timestamp | ISO 8601 UTC |
| Banner version | Hash of banner text/design |
| Cookie policy version | Version identifier (e.g., v2.3) |
| Decisions | Per-purpose accept/reject |
| Collection mechanism | "cookie_banner_layer_1" or "cookie_banner_layer_2" |
| IP address | For geolocation verification (retained separately, access-restricted) |
Accessibility Requirements
The cookie banner must meet WCAG 2.1 Level AA:
- Keyboard navigable (Tab, Enter, Escape)
- Screen reader compatible (ARIA roles, labels)
- Sufficient color contrast (4.5:1 ratio minimum)
- Focus trap within banner until interaction (preventing interaction with page behind)
- Banner text at minimum 14px font size
CNIL Enforcement Precedents
| Date | Organization | Fine | Key Violation |
|---|---|---|---|
| 31 Dec 2021 | Google LLC | EUR 100,000,000 | No equivalent reject mechanism; cookies set before consent |
| 31 Dec 2021 | Google Ireland | EUR 50,000,000 | Same violations as Google LLC |
| 29 Dec 2022 | TikTok | EUR 5,000,000 | No equivalent reject mechanism |
| 31 Dec 2022 | Meta Platforms Ireland | EUR 60,000,000 | No equivalent reject mechanism |
| 15 Jun 2023 | Criteo | EUR 40,000,000 | Consent not freely given; insufficient information |
| 28 Dec 2023 | Amazon France | EUR 32,000,000 | Cookie deposits without consent |
Key Legal References
- CNIL Deliberation No. 2020-091 (17 September 2020) — Guidelines on cookies and other trackers
- CNIL Recommendation on cookies (1 October 2020) — Practical modalities for consent collection
- ePrivacy Directive 2002/58/EC, Article 5(3) — Consent for storing/accessing information on devices
- CJEU Case C-673/17 (Planet49) — Active consent, no pre-ticked boxes
- GDPR Article 7 — Conditions for consent, including withdrawal
- CNIL Decision SAN-2021-023 (Google) — EUR 150M total fine for cookie consent violations
- CNIL Decision SAN-2022-021 (Meta) — EUR 60M fine for cookie consent violations
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/cnil-cookie-banner of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Cnil Cookie Banner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cnil Cookie Banner this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about Cnil Cookie Banner
What does Cnil Cookie Banner do?
Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences. Cnil Cookie Banner is an agent skill from mukul975/Privacy-Data-Protection-Skills. Designing and implementing CNIL-compliant cookie consent banners for French and EU audiences.
When should I use Cnil Cookie Banner?
Cnil Cookie Banner fits situations like: tasks that involve Privacy and GDPR.
How do I install Cnil Cookie Banner in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a claude-code`. Or copy the skill folder (skills/privacy/cnil-cookie-banner in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cnil-cookie-banner in your project. Claude Code loads it when a task matches its description.
How do I install Cnil Cookie Banner in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a codex`. Or copy the skill folder (skills/privacy/cnil-cookie-banner in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cnil-cookie-banner in your project. Codex loads it when a task matches its description.
Can I use Cnil Cookie Banner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cnil-cookie-banner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cnil-cookie-banner, .gemini/skills/cnil-cookie-banner, .github/skills/cnil-cookie-banner and .opencode/skills/cnil-cookie-banner in your project.
What does Cnil Cookie Banner need to run?
Going by SKILL.md and its folder, Cnil Cookie Banner needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Cnil Cookie Banner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cnil Cookie Banner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Cnil Cookie Banner use?
Cnil Cookie Banner is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cnil Cookie Banner use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Cnil Cookie Banner?
Skills that share tags, products or a category with Cnil Cookie Banner: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cnil Cookie Banner?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.