C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Framework for evaluating and selecting Consent Management Platforms (CMPs).
Install Consent Platform Eval
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-platform-eval -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-platform-eval --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/consent-platform-eval .claude/skills/consent-platform-eval && 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 "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .claude/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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/consent-platform-evalType 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 consent-platform-eval -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-platform-eval --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/consent-platform-eval .agents/skills/consent-platform-eval && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .agents/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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 consent-platform-eval -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-platform-eval --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/consent-platform-eval .cursor/skills/consent-platform-eval && 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 "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .cursor/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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/consent-platform-eval--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 consent-platform-eval -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills consent-platform-eval --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/consent-platform-eval .gemini/skills/consent-platform-eval && 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 "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .gemini/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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 consent-platform-evalInstalls 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 consent-platform-eval -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/consent-platform-eval .github/skills/consent-platform-eval && 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 "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .github/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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 consent-platform-eval -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 consent-platform-eval --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/consent-platform-eval .opencode/skills/consent-platform-eval && 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 "consent-platform-eval" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/consent-platform-eval into .opencode/skills/consent-platform-eval/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "consent-platform-eval", 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
consent-platform-eval- GitHub stars
- 295
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,024 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Framework for evaluating and selecting Consent Management Platforms (CMPs).
- Works in 4 steps: Requirements Gathering → Shortlist (3-4 Vendors) → Proof of Concept (2 Weeks per Vendor) → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Evaluation Criteria, Vendor Comparison Matrix and Selection Process, plus 2 more sections
- Runs Python scripts from its folder
What it does
Consent Platform Eval is an agent skill from mukul975/Privacy-Data-Protection-Skills. Framework for evaluating and selecting Consent Management Platforms (CMPs). Covers TCF v2.2 certification requirements, Global Privacy Control support, multi-regulation compliance (GDPR, CCPA, LGPD), A/B testing capabilities, API integration options, reporting features, and a structured vendor comparison methodology.
Its SKILL.md is about 2.3k 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
- “/consent-platform-eval”
Requirements
- Python 3
Workflow steps
4 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
Consent Platform Eval loads about 2.3k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 1,024 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,024 words, ~2,309 tokens.
Download SKILL.mdSave it as
.claude/skills/consent-platform-eval/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- consent-platform-eval
- description
- Framework for evaluating and selecting Consent Management Platforms (CMPs). Covers TCF v2.2 certification requirements, Global Privacy Control support, multi-regulation compliance (GDPR, CCPA, LGPD), A/B testing capabilities, API integration options, reporting features, and a structured vendor comparison methodology.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- consent-management
- metadata.tags
- consent-management-platform, cmp-evaluation, tcf-certification, vendor-selection, cmp-comparison
Evaluating Consent Management Platforms
Overview
A Consent Management Platform (CMP) is the technology layer that handles cookie consent collection, preference management, consent record storage, and signal propagation to downstream systems. Selecting the right CMP is critical for compliance with GDPR, ePrivacy, CCPA/CPRA, LGPD, and other regulations. The IAB Transparency and Consent Framework (TCF) v2.2 certification is a key differentiator for CMPs operating in the EU advertising ecosystem.
Evaluation Criteria
Category 1: Regulatory Compliance (Weight: 30%)
| Criterion | Description | Scoring |
|---|---|---|
| TCF v2.2 Certification | CMP is registered with IAB Europe and passes compliance audits | Required for EU advertising |
| GDPR Compliance | Supports Art. 7 consent requirements, Art. 7(3) withdrawal, Art. 7(1) records | Mandatory for EU operations |
| CCPA/CPRA Support | Supports "Do Not Sell" opt-out, GPC signal detection, CPRA requirements | Required for US operations |
| LGPD Support | Brazilian data protection law consent requirements | Required for Brazil operations |
| GPC Support | Detects and honors Global Privacy Control (Sec-GPC: 1) signal | Required for CA, CO, CT, MT, TX, OR |
| CNIL Compliance | Equal prominence accept/reject, 6-month reconsent, no cookie walls | Required for French operations |
| Multi-Jurisdiction | Ability to apply different consent rules based on user location | Critical for global operations |
| Cookie Scanning | Automated scanning to detect and classify all cookies on the site | Important for completeness |
Category 2: Technical Capabilities (Weight: 25%)
| Criterion | Description | Scoring |
|---|---|---|
| API Integration | RESTful API for consent state queries from backend systems | Critical for server-side enforcement |
| Tag Manager Integration | Native integration with Google Tag Manager, Tealium, Segment | Reduces implementation effort |
| SDK Availability | Mobile SDKs (iOS, Android) and server-side SDKs | Required for mobile apps |
| Performance | Page load impact (target: <100ms additional latency) | Critical for UX |
| Customization | UI customization (colors, layout, language, button text) | Important for brand consistency |
| A/B Testing | Built-in consent banner experimentation (within compliance boundaries) | Important for optimization |
| Geolocation | Accurate user location detection for jurisdiction-specific rules | Critical for multi-region |
| TC String Generation | Generates IAB TC String for ad tech ecosystem integration | Required for advertising |
Category 3: Consent Record Management (Weight: 20%)
| Criterion | Description | Scoring |
|---|---|---|
| Consent Receipts | Generates audit-ready consent receipts per Art. 7(1) | Critical for compliance |
| Version Control | Tracks consent text versions with change history | Important for audit trail |
| Consent History | Full history per user (grants, withdrawals, re-consents) | Critical for DSAR support |
| Data Export | Export consent records in standard formats (JSON, CSV) | Important for portability |
| Retention Controls | Configurable consent record retention periods | Important for data minimization |
| Search and Query | Search consent records by user, purpose, date range | Important for DPA inquiries |
| Proof of Consent | Can generate evidence packages for regulatory inquiries | Critical for enforcement defense |
Category 4: Reporting and Analytics (Weight: 15%)
| Criterion | Description | Scoring |
|---|---|---|
| Consent Rate Dashboard | Real-time consent/opt-out rates by purpose and region | Important for monitoring |
| Trend Analysis | Historical consent rate trends over time | Important for strategy |
| Compliance Reporting | Pre-built reports aligned with GDPR, CCPA requirements | Important for DPO |
| Custom Reports | Ability to create custom reports and dashboards | Nice to have |
| Alerting | Alerts for anomalous consent patterns (sudden drops, spikes) | Important for incident detection |
| GPC Reporting | Reports on GPC signal detection rates and actions taken | Required for CPRA compliance |
Category 5: Vendor and Support (Weight: 10%)
| Criterion | Description | Scoring |
|---|---|---|
| Data Processing Agreement | GDPR-compliant DPA available | Mandatory |
| Data Residency | EU data hosting available (for consent records) | Required for EU operations |
| Sub-Processors | Transparent sub-processor list | Required per Art. 28 |
| SLA | Uptime SLA (target: 99.9%+) | Critical for availability |
| Support | Dedicated support, privacy expertise, implementation guidance | Important |
| Pricing Model | Transparent pricing (per pageview, per domain, flat rate) | Important for budgeting |
Show full SKILL.md (454 more words)Show less
Vendor Comparison Matrix
| Feature | OneTrust | Cookiebot | Usercentrics | Didomi | Quantcast Choice |
|---|---|---|---|---|---|
| TCF v2.2 Certified | Yes | Yes | Yes | Yes | Yes |
| GDPR Compliance | Full | Full | Full | Full | Full |
| CCPA/CPRA Support | Yes | Yes | Yes | Yes | Yes |
| GPC Detection | Yes | Yes | Yes | Yes | Yes |
| LGPD Support | Yes | Limited | Yes | Yes | Limited |
| CNIL Compliance | Yes | Yes | Yes | Yes | Yes |
| Multi-Jurisdiction | 100+ countries | 50+ countries | 50+ countries | 40+ countries | 30+ countries |
| Cookie Scanner | Automated | Automated | Automated | Automated | Automated |
| API | REST + GraphQL | REST | REST | REST + GraphQL | REST |
| Mobile SDKs | iOS + Android | Limited | iOS + Android | iOS + Android | Limited |
| GTM Integration | Native | Native | Native | Native | Native |
| A/B Testing | Built-in | Via API | Built-in | Built-in | Limited |
| Performance | ~80ms | ~60ms | ~70ms | ~75ms | ~50ms |
| Consent Receipts | Kantara-aligned | Basic | Detailed | Detailed | Basic |
| Version Control | Yes | Yes | Yes | Yes | Yes |
| Data Export | JSON, CSV, API | CSV | JSON, CSV, API | JSON, CSV | CSV |
| Consent Dashboard | Advanced | Basic | Advanced | Advanced | Basic |
| EU Data Hosting | Yes (Frankfurt) | Yes (Copenhagen) | Yes (Munich) | Yes (Paris) | Yes (Amsterdam) |
| DPA Available | Standard | Standard | Standard | Standard | Standard |
| SLA | 99.99% | 99.9% | 99.95% | 99.9% | 99.9% |
| Pricing Model | Per session | Per domain | Per session | Per pageview | Free (basic) |
| Starting Price | ~EUR 300/month | ~EUR 9/month | ~EUR 50/month | ~EUR 50/month | Free tier |
Selection Process
Step 1: Requirements Gathering
Identify must-have requirements based on:
- Jurisdictions where your organization operates
- Number of domains and mobile apps
- Advertising ecosystem participation (need TCF v2.2?)
- Backend integration needs (API requirements)
- Budget constraints
Step 2: Shortlist (3-4 Vendors)
Apply mandatory criteria as filters:
- TCF v2.2 certification (if operating in EU ad tech)
- GPC support (if serving US consumers)
- EU data hosting (if required by data residency policy)
Step 3: Proof of Concept (2 Weeks per Vendor)
For each shortlisted vendor:
- Implement on a staging environment
- Test all consent flows (accept, refuse, manage, withdraw)
- Measure page load impact
- Test API integration with backend systems
- Verify consent records meet Art. 7(1) requirements
- Test multi-jurisdiction logic (EU vs US vs Brazil)
Step 4: Scoring and Selection
Score each vendor against the weighted criteria. Calculate weighted total score. Select the vendor with the highest score that meets all mandatory requirements.
CloudVault SaaS Inc. Selection
After evaluating five vendors, CloudVault SaaS Inc. selected Usercentrics based on:
- Full TCF v2.2 certification
- Native iOS and Android SDKs (critical for CloudVault mobile app)
- Built-in A/B testing within CNIL compliance boundaries
- Strong API for server-side consent state queries
- EU data hosting in Munich (same jurisdiction as key customers)
- Competitive pricing for the pageview volume
Key Regulatory References
- IAB TCF v2.2 Specification — CMP certification and requirements
- GDPR Article 7 — Conditions for consent (CMP must support)
- GDPR Article 28 — Processor requirements (CMP as processor)
- CPRA Section 1798.135(e) — GPC signal recognition
- CNIL Deliberation 2020-091 — Cookie consent technical requirements
- LGPD (Lei 13.709/2018) — Brazilian consent requirements
- ePrivacy Directive Article 5(3) — Cookie consent basis
© 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/consent-platform-eval 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
Consent Platform Eval 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 |
|---|---|---|---|---|---|---|
| Consent Platform Eval this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2.3k | 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 | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 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 278 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.
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.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Consent Platform Eval
What does Consent Platform Eval do?
Framework for evaluating and selecting Consent Management Platforms (CMPs). Consent Platform Eval is an agent skill from mukul975/Privacy-Data-Protection-Skills. Framework for evaluating and selecting Consent Management Platforms (CMPs).
When should I use Consent Platform Eval?
Consent Platform Eval fits situations like: tasks that involve Privacy and GDPR.
How do I install Consent Platform Eval in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-platform-eval -a claude-code`. Or copy the skill folder (skills/privacy/consent-platform-eval in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/consent-platform-eval in your project. Claude Code loads it when a task matches its description.
How do I install Consent Platform Eval in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill consent-platform-eval -a codex`. Or copy the skill folder (skills/privacy/consent-platform-eval in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/consent-platform-eval in your project. Codex loads it when a task matches its description.
Can I use Consent Platform Eval 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 consent-platform-eval -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/consent-platform-eval, .gemini/skills/consent-platform-eval, .github/skills/consent-platform-eval and .opencode/skills/consent-platform-eval in your project.
What does Consent Platform Eval need to run?
Going by SKILL.md and its folder, Consent Platform Eval needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Consent Platform Eval 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 Consent Platform Eval 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 Consent Platform Eval use?
Consent Platform Eval 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 Consent Platform Eval use?
About 2.3k tokens (SKILL.md is roughly 9.2k 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 2k tokens, read only when the agent opens those files.
What are the alternatives to Consent Platform Eval?
Skills that share tags, products or a category with Consent Platform Eval: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 942 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Consent Platform Eval?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.