C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Managing consent for analytics cookies and implementing privacy-preserving measurement.
Install Analytics Cookie Consent
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill analytics-cookie-consent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills analytics-cookie-consent --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/analytics-cookie-consent .claude/skills/analytics-cookie-consent && 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 "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .claude/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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/analytics-cookie-consentType 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 analytics-cookie-consent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills analytics-cookie-consent --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/analytics-cookie-consent .agents/skills/analytics-cookie-consent && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .agents/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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 analytics-cookie-consent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills analytics-cookie-consent --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/analytics-cookie-consent .cursor/skills/analytics-cookie-consent && 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 "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .cursor/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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/analytics-cookie-consent--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 analytics-cookie-consent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills analytics-cookie-consent --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/analytics-cookie-consent .gemini/skills/analytics-cookie-consent && 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 "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .gemini/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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 analytics-cookie-consentInstalls 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 analytics-cookie-consent -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/analytics-cookie-consent .github/skills/analytics-cookie-consent && 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 "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .github/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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 analytics-cookie-consent -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 analytics-cookie-consent --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/analytics-cookie-consent .opencode/skills/analytics-cookie-consent && 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 "analytics-cookie-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/analytics-cookie-consent into .opencode/skills/analytics-cookie-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics-cookie-consent", 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
analytics-cookie-consent- GitHub stars
- 297
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,194 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Managing consent for analytics cookies and implementing privacy-preserving measurement.
- Works in 4 steps: Data is processed by Google (a third… → Data may be combined with other Google… → Data is transferred to the United States → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, GA4 Privacy Configuration, Analytics Without Consent —… and Aggregate Reporting Alternatives, plus 2 more sections
- Runs Python scripts from its folder
What it does
Analytics Cookie Consent is an agent skill from mukul975/Privacy-Data-Protection-Skills. Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behavior, aggregate reporting alternatives, and cookieless measurement approaches.
Its SKILL.md is about 2.7k 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. It works with Google Analytics. 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
- “/analytics-cookie-consent”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Data is processed by Google (a third party)
- Data may be combined with other Google services
- Data is transferred to the United States
- Google retains control over processing purposes
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
Analytics Cookie Consent loads about 2.7k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 1,194 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). 1,194 words, ~2,682 tokens.
Download SKILL.mdSave it as
.claude/skills/analytics-cookie-consent/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- analytics-cookie-consent
- description
- Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behavior, aggregate reporting alternatives, and cookieless measurement approaches.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- cookie-consent-compliance
- metadata.tags
- analytics-consent, ga4-privacy, cookieless-analytics, aggregate-reporting, privacy-measurement
Managing Consent for Analytics Cookies
Overview
Analytics cookies present a unique compliance challenge: they are among the most widely deployed non-essential cookies, yet many organizations depend on them for business intelligence. The ePrivacy Directive Article 5(3) requires consent for analytics cookies (they are not strictly necessary for the service requested by the user), confirmed by the Planet49 ruling. However, some Data Protection Authorities — notably the CNIL — have explored whether analytics can qualify for a consent exemption if configured with sufficient privacy safeguards. This skill covers compliant analytics implementation, consent mode fallback behavior, and alternatives that reduce or eliminate the need for consent.
GA4 Privacy Configuration
Privacy-First GA4 Setup for Pinnacle E-Commerce Ltd
Configure GA4 with maximum privacy protections:
GA4 Property Settings:
| Setting | Value | Purpose |
|---|---|---|
| Data retention | 2 months | Minimum needed for trend analysis |
| Reset user data on new activity | Enabled | Do not extend retention on revisit |
| IP anonymization | Enabled (default in GA4) | Last octet removed before storage |
| Google Signals | Disabled | Prevents cross-device tracking via Google account |
| Granular location | Disabled | City-level only, no GPS/precise location |
| Device data collection | Disabled | Reduces device fingerprinting surface |
| Data sharing with Google | Disabled | Prevents data use for Google benchmarking/products |
| Ads personalization | Disabled | No remarketing audiences from analytics |
| User ID feature | Disabled unless explicit consent | Requires separate consent if linking sessions |
GA4 Data Stream Settings:
| Setting | Value |
|---|---|
| Enhanced measurement | Selective — enable page views, scrolls; disable site search, file downloads unless needed |
| Cross-domain tracking | Only between pinnacle-ecommerce.com subdomains |
| Referral exclusions | Add payment processors (stripe.com, paypal.com) |
| Internal traffic filtering | Exclude office IP ranges |
Consent Mode Integration
GA4 behavior changes based on analytics_storage consent state:
When analytics_storage = granted:
_gacookie set (client ID persisted)_gidcookie set (session distinction)- Full event data collected
- User-level and session-level reporting available
- Real-time reports populated
When analytics_storage = denied:
- No analytics cookies set
- Cookieless pings sent to Google (if Consent Mode enabled)
- Pings include: timestamp, page path, user agent, referrer, consent state
- Pings do NOT include: client ID, session ID, user ID
- GA4 uses behavioral modeling to estimate metrics from these pings
- Modeled data appears in reports with a "modeled" badge
Behavioral Modeling Thresholds
For GA4 to provide modeled data for non-consenting users:
| Requirement | Minimum |
|---|---|
| Consented daily users | 1,000+ per web data stream |
| Consecutive days of data | 7+ days |
| Consent Mode implementation | On all GA4 tags |
| Data quality | < 10% bot traffic |
If thresholds are not met, GA4 reports will show only consented users — creating an undercount.
Analytics Without Consent — CNIL Exemption Criteria
CNIL Cookie Exemption for Audience Measurement
The CNIL published guidance (September 2020, updated June 2021) identifying limited conditions under which audience measurement cookies may be exempt from consent under ePrivacy Article 5(3). This is an interpretation specific to French law (transposition of ePrivacy Directive) and is not universally accepted across all EU member states.
CNIL Exemption Conditions:
| Condition | Requirement |
|---|---|
| Purpose limitation | Strictly limited to anonymous audience measurement on behalf of the publisher only |
| No cross-site tracking | Data must not be combined across different websites or apps |
| No data sharing | Data must not be shared with third parties |
| Cookie lifetime | Maximum 13 months |
| Data retention | Maximum 25 months from collection |
| IP address | Anonymized or not collected |
| User notification | Users must still be informed about the cookies (even without consent) |
| Opt-out mechanism | Users must be able to object to the measurement |
CNIL-Exempt Analytics Tools:
The CNIL maintains a list of analytics solutions that can be configured to meet exemption criteria:
| Tool | CNIL Exempt Configuration | Notes |
|---|---|---|
| Matomo (self-hosted) | Yes — with specific config | No data sharing, anonymized IP, 13-month cookie, self-hosted |
| AT Internet (Piano Analytics) | Yes — exempt mode | French analytics provider, certified by CNIL |
| Eulerian Analytics | Yes — exempt mode | First-party data processing, no cross-site |
| Abla Analytics | Yes — privacy-by-design | Designed for CNIL exemption |
| Google Analytics 4 | No — does not meet exemption | Data transferred to Google; cross-site processing |
GA4 Cannot Qualify for CNIL Exemption Because:
- Data is processed by Google (a third party)
- Data may be combined with other Google services
- Data is transferred to the United States
- Google retains control over processing purposes
Show full SKILL.md (525 more words)Show less
Implementing Matomo as CNIL-Exempt Alternative
For Pinnacle E-Commerce Ltd, deploy Matomo alongside GA4:
Matomo CNIL-Exempt Configuration:
| Setting | Value |
|---|---|
| Hosting | Self-hosted on EU servers (pinnacle-ecommerce.com infrastructure) |
| Cookie lifetime | 13 months maximum |
| IP anonymization | Full anonymization (2 bytes masked for IPv4) |
| Do Not Track | Respected |
| Data retention | Visitor logs: 25 months; aggregated reports: indefinite |
| Cross-site tracking | Disabled |
| Third-party data sharing | None |
| User opt-out | JavaScript opt-out widget on cookie policy page |
| Session fingerprinting | Disabled — use cookie-based session only |
Dual Analytics Architecture:
Page Load
│
├── Always fire (no consent needed):
│ └── Matomo (CNIL-exempt configuration)
│ └── Basic pageview, session, referrer data
│
└── Fire only with analytics consent:
└── GA4 (full measurement)
└── Enhanced measurement, events, conversionsThis gives Pinnacle E-Commerce Ltd baseline analytics for all users (via Matomo) and richer data for consenting users (via GA4).
Aggregate Reporting Alternatives
Privacy-Preserving Measurement Approaches
| Approach | Consent Required | Data Granularity | Implementation |
|---|---|---|---|
| Server-side log analysis | No (essential for operations) | Aggregate | Parse access logs for page views, status codes |
| Matomo (CNIL-exempt config) | No (France only) | Per-session | Self-hosted, privacy-configured |
| GA4 with Consent Mode | Yes (consent improves data) | User-level (modeled for non-consenting) | Standard implementation |
| Plausible Analytics | Depends on jurisdiction | Aggregate | No cookies, no PII, EU-hosted |
| Fathom Analytics | Depends on jurisdiction | Aggregate | No cookies, no PII |
| Privacy Sandbox Attribution Reporting | Evolving | Aggregate | Chrome-only, limited availability |
Server-Side Log Analytics
The most privacy-preserving approach uses existing server access logs:
Available Metrics from Access Logs:
| Metric | Source | Processing |
|---|---|---|
| Page views | HTTP request count | Count 200-status HTML requests |
| Unique visitors (daily) | IP + User Agent hash | Hash and count distinct per day |
| Top pages | Request URI | Rank by request count |
| Referrers | Referer header | Parse and categorize |
| Device types | User-Agent header | Parse UA for device category |
| Geographic distribution | IP geolocation | Resolve to country, discard IP |
| Error rates | HTTP status codes | Count 4xx, 5xx responses |
| Page load performance | Server response time | Measure TTFB from logs |
Limitations:
- No client-side event tracking (clicks, scrolls, form interactions)
- No session stitching across pages (without cookies)
- No conversion attribution
- Bot traffic must be filtered (estimated 30-50% of web traffic)
Consent Rate Impact Analysis
Typical analytics consent rates observed across industries:
| Consent Banner Design | Analytics Consent Rate | Impact on GA4 Data |
|---|---|---|
| Accept All prominent, Reject buried | 80-90% | Low data loss |
| Equal prominence (CNIL-compliant) | 40-60% | Significant data loss |
| Reject All as default action | 20-35% | Severe data loss |
| Cookie wall (non-compliant) | 90%+ | Artificially high — non-compliant |
Pinnacle E-Commerce Ltd Expected Impact: With a CNIL-compliant equal-prominence banner, expect approximately 45-55% analytics consent rate. This means:
- GA4 direct measurement covers ~50% of users
- Consent Mode behavioral modeling recovers ~20-30% of lost data
- Combined coverage: ~70-80% of actual traffic
- Matomo (CNIL-exempt) provides 100% coverage for basic metrics
Key Legal and Technical References
- ePrivacy Directive 2002/58/EC, Article 5(3) — Consent required for analytics cookies (not strictly necessary)
- CJEU Case C-673/17 (Planet49) — Active consent for all non-essential cookies including analytics
- CNIL Deliberation No. 2020-091 (17 September 2020) — Cookie guidelines including audience measurement exemption
- CNIL Guidelines on Audience Measurement Exemption (June 2021) — Conditions for consent-exempt analytics
- EDPB Guidelines 05/2020 on Consent — Analytics cookies require consent under GDPR
- Google Analytics 4 Privacy Documentation — GA4 data controls, consent mode, data retention
- Matomo GDPR/CNIL Compliance Guide — Self-hosted configuration for consent exemption
- Austrian DPA Decision (December 2021, DSB D155.027) — Found Google Analytics non-compliant with GDPR due to US data transfers
- CNIL Decision on Google Analytics (February 2022) — Ordered website to comply or cease using GA; US transfer concern
© 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/analytics-cookie-consent 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
Analytics Cookie Consent 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 |
|---|---|---|---|---|---|---|
| Analytics Cookie Consent this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| SEO Analiticaricneves-ai/flowgrammers-skills | 115 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Ga4 Privacy ComplianceMicrock/ordinary-claude-skills | 404 | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Analyticsericrisco/rsc-harness | 174 | — | ~2.8k | Automated safety check: Pass | MIT | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
SEO Analitica
ricneves-ai/flowgrammers-skills
Skills para otimização de SEO técnico, análise de dados, criação de dashboards e inteligência de negócio para empresas brasileiras.
Ga4 Privacy Compliance
Microck/ordinary-claude-skills
Expert guidance for GA4 privacy and compliance including GDPR, CCPA, Consent Mode v2, data deletion, and privacy settings.
Analytics
ericrisco/rsc-harness
A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.
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.
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
Works with
Categories
Questions about Analytics Cookie Consent
What does Analytics Cookie Consent do?
Managing consent for analytics cookies and implementing privacy-preserving measurement. Analytics Cookie Consent is an agent skill from mukul975/Privacy-Data-Protection-Skills. Managing consent for analytics cookies and implementing privacy-preserving measurement.
When should I use Analytics Cookie Consent?
Analytics Cookie Consent fits situations like: tasks that involve Privacy and GDPR.
How do I install Analytics Cookie Consent in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill analytics-cookie-consent -a claude-code`. Or copy the skill folder (skills/privacy/analytics-cookie-consent in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/analytics-cookie-consent in your project. Claude Code loads it when a task matches its description.
How do I install Analytics Cookie Consent in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill analytics-cookie-consent -a codex`. Or copy the skill folder (skills/privacy/analytics-cookie-consent in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/analytics-cookie-consent in your project. Codex loads it when a task matches its description.
Can I use Analytics Cookie Consent 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 analytics-cookie-consent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analytics-cookie-consent, .gemini/skills/analytics-cookie-consent, .github/skills/analytics-cookie-consent and .opencode/skills/analytics-cookie-consent in your project.
What does Analytics Cookie Consent need to run?
Going by SKILL.md and its folder, Analytics Cookie Consent needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Analytics Cookie Consent 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 Analytics Cookie Consent 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 Analytics Cookie Consent use?
Analytics Cookie Consent 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 Analytics Cookie Consent use?
About 2.7k 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 777 tokens, read only when the agent opens those files.
What are the alternatives to Analytics Cookie Consent?
Skills that share tags, products or a category with Analytics Cookie Consent: C15t (c15t/c15t, 1.9k stars), SEO Analitica (ricneves-ai/flowgrammers-skills, 115 stars), Ga4 Privacy Compliance (Microck/ordinary-claude-skills, 404 stars) and Analytics (ericrisco/rsc-harness, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analytics Cookie Consent?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 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.