C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
CPRA §1798.121 sensitive personal information restrictions and compliance.
Install Cpra Sensitive Pi
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-sensitive-pi -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-sensitive-pi --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/cpra-sensitive-pi .claude/skills/cpra-sensitive-pi && 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 "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .claude/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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/cpra-sensitive-piType 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 cpra-sensitive-pi -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-sensitive-pi --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/cpra-sensitive-pi .agents/skills/cpra-sensitive-pi && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .agents/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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 cpra-sensitive-pi -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-sensitive-pi --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/cpra-sensitive-pi .cursor/skills/cpra-sensitive-pi && 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 "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .cursor/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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/cpra-sensitive-pi--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 cpra-sensitive-pi -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-sensitive-pi --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/cpra-sensitive-pi .gemini/skills/cpra-sensitive-pi && 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 "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .gemini/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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 cpra-sensitive-piInstalls 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 cpra-sensitive-pi -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/cpra-sensitive-pi .github/skills/cpra-sensitive-pi && 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 "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .github/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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 cpra-sensitive-pi -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 cpra-sensitive-pi --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/cpra-sensitive-pi .opencode/skills/cpra-sensitive-pi && 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 "cpra-sensitive-pi" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-sensitive-pi into .opencode/skills/cpra-sensitive-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-sensitive-pi", 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
cpra-sensitive-pi- GitHub stars
- 297
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,543 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
CPRA §1798.121 sensitive personal information restrictions and compliance.
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Sensitive PI Categories…, Right to Limit Use and… and Privacy Notice Disclosure…, plus 3 more sections
- Runs Python scripts from its folder
What it does
Cpra Sensitive Pi is an agent skill from mukul975/Privacy-Data-Protection-Skills. CPRA §1798.121 sensitive personal information restrictions and compliance. Covers all 9 sensitive PI categories including SSN, precise geolocation, racial/ethnic origin, biometric, genetic, health, and sex life data. Right to limit use/disclosure, permitted purposes, and implementation.
Its SKILL.md is about 3.1k 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
- “/cpra-sensitive-pi”
Requirements
- Python 3
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
Cpra Sensitive Pi loads about 3.1k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 1,543 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,543 words, ~3,110 tokens.
Download SKILL.mdSave it as
.claude/skills/cpra-sensitive-pi/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cpra-sensitive-pi
- description
- CPRA §1798.121 sensitive personal information restrictions and compliance. Covers all 9 sensitive PI categories including SSN, precise geolocation, racial/ethnic origin, biometric, genetic, health, and sex life data. Right to limit use/disclosure, permitted purposes, and implementation.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- us-state-privacy-laws
- metadata.tags
- cpra-sensitive-pi, sensitive-data, limit-use, geolocation, biometric
CPRA Sensitive Personal Information
Overview
The California Privacy Rights Act (CPRA) introduced the concept of "sensitive personal information" (sensitive PI) as a distinct category under Cal. Civ. Code §1798.140(ae), effective January 1, 2023. This category parallels but is not identical to the GDPR's "special categories of data" under Article 9. The CPRA grants consumers the right to limit a business's use and disclosure of their sensitive PI to specific enumerated purposes under §1798.121.
Unlike the GDPR, which generally prohibits processing of special categories unless an exception applies, the CPRA permits businesses to collect and use sensitive PI but gives consumers the right to restrict that processing after collection through the "limit use" mechanism.
Sensitive PI Categories (§1798.140(ae))
Category 1: Government Identifiers
Social Security number, driver's license number, state identification card number, or passport number.
Liberty Commerce Inc. Processing: Liberty Commerce Inc. collects Social Security numbers for tax reporting (1099-K forms) from marketplace sellers exceeding $600 in annual sales per IRS reporting thresholds. Driver's license numbers are collected for age verification on restricted product purchases. These are stored in a segregated, encrypted database with access limited to the tax compliance and fraud prevention teams.
Category 2: Account Credentials
Account log-in, financial account, debit card, or credit card number in combination with any required security or access code, password, or credentials allowing access to an account.
Liberty Commerce Inc. Processing: Payment card data is processed via PCI DSS-compliant service provider PaySecure Corp. and is not stored in Liberty Commerce Inc.'s systems in cleartext. Account credentials (hashed passwords, MFA tokens) are stored in the identity management system with bcrypt hashing and per-account salt.
Category 3: Precise Geolocation
Any data that is derived from a device and that is used or intended to be used to locate a consumer within a geographic area that is equal to or less than the area of a circle with a radius of 1,850 feet (approximately 564 meters).
Liberty Commerce Inc. Processing: The mobile app collects precise geolocation for store finder, delivery tracking, and local inventory search. Geolocation data is processed in real time and retained for 30 days. Upon a consumer's limit request, geolocation processing is restricted to delivery tracking only (a permitted service fulfillment purpose).
Category 4: Racial or Ethnic Origin
Racial or ethnic origin of the consumer.
Liberty Commerce Inc. Processing: Liberty Commerce Inc. collects racial/ethnic origin data through an optional workforce diversity survey for employees and an optional customer demographic survey. Customer survey data is aggregated and anonymized within 90 days. Upon a limit request, survey data collection ceases for that consumer and existing data is deleted.
Category 5: Religious or Philosophical Beliefs
Religious or philosophical beliefs of the consumer.
Liberty Commerce Inc. Processing: Not actively collected. May be inferred from product purchase patterns (religious texts, dietary products). Liberty Commerce Inc. does not create inferences about religious beliefs for advertising purposes. Product recommendation algorithms are configured to exclude religion-indicative categories from profile building.
Category 6: Union Membership
Union membership of the consumer.
Liberty Commerce Inc. Processing: Collected only for employees where required for payroll processing (union dues deduction). Not collected from consumers. Stored in HR system with access restricted to payroll administrators.
Category 7: Private Communications Content
Contents of a consumer's mail, email, and text messages unless the business is the intended recipient of the communication.
Liberty Commerce Inc. Processing: Customer service email and chat communications are retained for quality assurance and dispute resolution. Liberty Commerce Inc. is the intended recipient of these communications, so they fall outside the sensitive PI definition for purposes of the limit right. Third-party message content is not collected.
Category 8: Genetic Data
A consumer's genetic data.
Liberty Commerce Inc. Processing: Not collected. Liberty Commerce Inc. does not process genetic data for any business purpose.
Category 9: Biometric Information
Processing of biometric information for the purpose of uniquely identifying a consumer.
Liberty Commerce Inc. Processing: Face ID and fingerprint authentication are processed locally on the consumer's device via platform APIs (Apple Face ID, Android BiometricPrompt). Liberty Commerce Inc. does not receive, store, or process raw biometric templates. Device-side biometric results are used only to unlock the app and authorize transactions.
Category 10: Health Information
A consumer's health information.
Liberty Commerce Inc. Processing: Health-related product purchases (vitamins, supplements, medical devices) are recorded as transaction data. Liberty Commerce Inc. does not infer health conditions from purchase patterns for advertising. Health product purchase data is excluded from behavioral advertising profiles.
Category 11: Sex Life or Sexual Orientation
Information concerning a consumer's sex life or sexual orientation.
Liberty Commerce Inc. Processing: Not actively collected. May be inferred from product purchases. Liberty Commerce Inc. does not create or use inferences about sex life or sexual orientation for any business purpose.
Right to Limit Use and Disclosure (§1798.121)
Consumer Exercise Mechanism
- Business must display a "Limit the Use of My Sensitive Personal Information" link on its homepage
- The link may be combined with the opt-out link as a single "Your Privacy Choices" link per CPPA Regulations §7026(b)
- The CPPA-approved opt-out icon may be used in conjunction with the link
- No identity verification is required — the consumer's direction itself is sufficient
Show full SKILL.md (688 more words)Show less
Permitted Purposes After Limitation (§1798.121(a))
After a consumer exercises the limit right, the business may only use or disclose sensitive PI for:
| # | Permitted Purpose | Statute | Liberty Commerce Inc. Application |
|---|---|---|---|
| 1 | Perform services or provide goods reasonably expected by average consumer | §1798.121(a)(1) | Process transactions, fulfill orders, deliver products |
| 2 | Prevent, detect, investigate security incidents | §1798.121(a)(2) | Fraud detection using account credentials and geolocation anomalies |
| 3 | Resist malicious, deceptive, fraudulent, or illegal actions | §1798.121(a)(3) | Chargeback investigation, account takeover prevention |
| 4 | Ensure physical safety of natural persons | §1798.121(a)(4) | Product recall notifications using health product purchase data |
| 5 | Short-term, transient use including non-personalized advertising | §1798.121(a)(5) | Contextual (non-targeted) advertising based on current page content |
| 6 | Perform services on behalf of the business | §1798.121(a)(6) | Customer service, account maintenance, warranty processing |
| 7 | Verify or maintain quality or safety of a service or device | §1798.121(a)(7) | App functionality testing, payment processing verification |
| 8 | Upgrade, enhance, or improve services | §1798.121(a)(8) | Aggregate analytics for service improvement (no individual targeting) |
Processing Restrictions After Limitation
After a limit request, Liberty Commerce Inc. implements the following restrictions:
| Sensitive PI Category | Prohibited Uses | Permitted Uses |
|---|---|---|
| Precise geolocation | Targeted advertising, location-based marketing, sale to data brokers | Delivery tracking, store finder (if actively requested) |
| Payment credentials | Cross-referencing for marketing profiles, sharing with ad networks | Transaction processing, fraud detection |
| Racial/ethnic origin | Any marketing or profiling | Aggregate diversity reporting (anonymized) |
| Government IDs | Any use beyond original collection purpose | Tax reporting (SSN), age verification (DL) |
Privacy Notice Disclosure Requirements
Notice at Collection (§1798.100(a))
When collecting sensitive PI, the business must disclose:
- The categories of sensitive PI to be collected
- The purposes for which each category will be used
- Whether each category is sold or shared
- The retention period or criteria for each category
Privacy Policy (§1798.130(a)(5))
The privacy policy must separately identify:
- Categories of sensitive PI collected in the preceding 12 months
- Categories of sensitive PI sold or shared
- Purposes for using each sensitive PI category
- Whether consumers can limit use via the "Limit" link
Liberty Commerce Inc. Privacy Notice Excerpt:
Sensitive Personal Information We Collect: We collect the following categories of sensitive personal information: (1) Social Security numbers from marketplace sellers for tax reporting; (2) payment card details for transaction processing; (3) precise geolocation through our mobile app for delivery and store finder services. We do not sell or share your sensitive personal information. You may limit our use of your sensitive personal information by clicking "Limit the Use of My Sensitive Personal Information" in the footer of any page or by contacting us at privacy@libertycommerce.com.
Comparison with GDPR Special Categories
| Aspect | CPRA Sensitive PI | GDPR Special Categories (Art. 9) |
|---|---|---|
| Default rule | Permitted, with consumer right to limit | Prohibited, unless exception applies |
| Legal basis | No separate legal basis needed for collection | Explicit consent or specific exceptions required |
| Government IDs | Included as sensitive PI | Not a special category (but may be restricted by Member State law) |
| Financial data | Account credentials included | Not a special category |
| Precise geolocation | Included as sensitive PI | Not a special category (but may be covered under ePrivacy) |
| Enforcement | CPPA administrative fines; $7,500 for violations involving minors | DPA fines up to 4% annual turnover or EUR 20M |
Implementation Checklist
| # | Item | Status | Owner |
|---|---|---|---|
| 1 | Inventory all sensitive PI categories collected | Complete | Privacy Team |
| 2 | Map purposes for each sensitive PI category | Complete | Privacy Team |
| 3 | Deploy "Limit the Use of My Sensitive Personal Information" link | Complete | Engineering |
| 4 | Implement limit-request processing workflow | Complete | Engineering |
| 5 | Configure purpose-based access controls for sensitive PI | Complete | Security Team |
| 6 | Update privacy notice with sensitive PI disclosures | Complete | Legal |
| 7 | Train customer service on limit requests | Complete | Operations |
| 8 | Configure data processing agreements with sensitive PI restrictions | Complete | Legal |
| 9 | Test GPC signal interaction with limit mechanism | Complete | QA |
| 10 | Quarterly audit of sensitive PI processing against permitted purposes | Ongoing | Privacy Team |
Key Regulatory References
- Cal. Civ. Code §1798.121 — Right to limit use and disclosure of sensitive PI
- Cal. Civ. Code §1798.140(ae) — Definition of sensitive personal information
- Cal. Civ. Code §1798.135(a)(2) — "Limit" link requirement
- CPPA Regulations §7026 — Requests to limit sensitive PI
- CPPA Regulations §7027 — Combined opt-out/limit link option
- GDPR Article 9 — Processing of special categories of personal data (comparative reference)
© 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/cpra-sensitive-pi 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
Cpra Sensitive Pi 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 |
|---|---|---|---|---|---|---|
| Cpra Sensitive Pi this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~3.1k | 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 | 943 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 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 Cpra Sensitive Pi
What does Cpra Sensitive Pi do?
CPRA §1798.121 sensitive personal information restrictions and compliance. Cpra Sensitive Pi is an agent skill from mukul975/Privacy-Data-Protection-Skills.121 sensitive personal information restrictions and compliance.
When should I use Cpra Sensitive Pi?
Cpra Sensitive Pi fits situations like: tasks that involve Privacy and GDPR.
How do I install Cpra Sensitive Pi in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-sensitive-pi -a claude-code`. Or copy the skill folder (skills/privacy/cpra-sensitive-pi in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cpra-sensitive-pi in your project. Claude Code loads it when a task matches its description.
How do I install Cpra Sensitive Pi in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-sensitive-pi -a codex`. Or copy the skill folder (skills/privacy/cpra-sensitive-pi in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cpra-sensitive-pi in your project. Codex loads it when a task matches its description.
Can I use Cpra Sensitive Pi 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 cpra-sensitive-pi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cpra-sensitive-pi, .gemini/skills/cpra-sensitive-pi, .github/skills/cpra-sensitive-pi and .opencode/skills/cpra-sensitive-pi in your project.
What does Cpra Sensitive Pi need to run?
Going by SKILL.md and its folder, Cpra Sensitive Pi needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Cpra Sensitive Pi 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 Cpra Sensitive Pi 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 Cpra Sensitive Pi use?
Cpra Sensitive Pi 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 Cpra Sensitive Pi use?
About 3.1k tokens (SKILL.md is roughly 12k 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 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Cpra Sensitive Pi?
Skills that share tags, products or a category with Cpra Sensitive Pi: 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, 943 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cpra Sensitive Pi?
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.