C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Multi-state harmonized privacy compliance program. An agent skill from mukul975/Privacy-Data-Protection-Skills.
Install Multi State Compliance
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill multi-state-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills multi-state-compliance --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/multi-state-compliance .claude/skills/multi-state-compliance && 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 "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .claude/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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/multi-state-complianceType 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 multi-state-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills multi-state-compliance --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/multi-state-compliance .agents/skills/multi-state-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .agents/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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 multi-state-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills multi-state-compliance --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/multi-state-compliance .cursor/skills/multi-state-compliance && 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 "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .cursor/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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/multi-state-compliance--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 multi-state-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills multi-state-compliance --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/multi-state-compliance .gemini/skills/multi-state-compliance && 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 "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .gemini/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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 multi-state-complianceInstalls 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 multi-state-compliance -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/multi-state-compliance .github/skills/multi-state-compliance && 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 "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .github/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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 multi-state-compliance -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 multi-state-compliance --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/multi-state-compliance .opencode/skills/multi-state-compliance && 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 "multi-state-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/multi-state-compliance into .opencode/skills/multi-state-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-state-compliance", 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
multi-state-compliance- GitHub stars
- 297
- Token cost
- ~2.3k tokens
- SKILL.md length
- 986 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Multi-state harmonized privacy compliance program. An agent skill from mukul975/Privacy-Data-Protection-Skills.
- Works in 6 steps: Privacy notice with categories of PI,… → Consumer rights portal supporting… → 45-day response SLA with tracking and… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Common Requirements Matrix, State-Specific Deltas and Unified Privacy Program…, plus 2 more sections
- Runs Python scripts from its folder
What it does
Multi State Compliance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Multi-state harmonized privacy compliance program. Common requirements matrix across all US state privacy laws, state-specific deltas, unified privacy program architecture, and implementation strategy for operating across California, Virginia, Colorado, Connecticut, Texas, Oregon, Montana, and Kentucky.
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
- “/multi-state-compliance”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Privacy notice with categories of PI, purposes, rights, third parties, contact info
- Consumer rights portal supporting access, correct, delete, portability, opt-out
- 45-day response SLA with tracking and metrics
- Data minimization and purpose limitation controls
- Reasonable data security measures
- Non-discrimination protections
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
Multi State Compliance loads about 2.3k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 986 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). 986 words, ~2,297 tokens.
Download SKILL.mdSave it as
.claude/skills/multi-state-compliance/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- multi-state-compliance
- description
- Multi-state harmonized privacy compliance program. Common requirements matrix across all US state privacy laws, state-specific deltas, unified privacy program architecture, and implementation strategy for operating across California, Virginia, Colorado, Connecticut, Texas, Oregon, Montana, and Kentucky.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- us-state-privacy-laws
- metadata.tags
- multi-state, harmonized-compliance, common-requirements, state-deltas, unified-program
Multi-State Harmonized Compliance Program
Overview
As of 2026, over 20 US states have enacted comprehensive consumer privacy legislation. Organizations operating nationwide face a complex patchwork of requirements with significant overlap but important state-specific variations. A harmonized multi-state compliance program identifies the common baseline, maps state-specific deltas, and implements a unified privacy architecture that satisfies all applicable laws.
This skill covers the eight major enacted and effective state privacy laws: CCPA/CPRA (California), VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), TDPSA (Texas), OCPA (Oregon), MTDPA (Montana), and KPPA (Kentucky).
Common Requirements Matrix
Consumer Rights — Universal Baseline
All eight laws provide these core rights:
| Right | CA | VA | CO | CT | TX | OR | MT | KY |
|---|---|---|---|---|---|---|---|---|
| Access/Know | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Correct | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Delete | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Portability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Opt-out: targeted ads | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Opt-out: sale | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Opt-out: profiling | No* | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Limit sensitive PI | Yes | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| Third-party list | No | No | No | No | No | Yes | No | No |
| Appeal | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
*California provides opt-out of automated decision-making under pending CPPA regulations.
Controller Obligations — Universal Baseline
| Obligation | All States |
|---|---|
| Privacy notice/policy | Required |
| Data minimization | Required |
| Purpose limitation | Required |
| Data security | Required |
| Non-discrimination | Required |
| Response timeline | 45 days (all states) |
State-Specific Deltas
California (CCPA/CPRA) — Unique Requirements
- Revenue threshold: $25M alternative threshold (no other state has this)
- Sensitive PI limit right: Post-collection limit mechanism (other states require pre-collection consent)
- CPPA enforcement: Dedicated privacy agency (only state with one)
- Private right of action: For data breach claims (only state with any private right of action)
- Annual metrics: Required for businesses processing 10M+ consumers
- Data processing agreements: Explicit statutory requirement
- No cure period: Eliminated by CPRA
Virginia (VCDPA) — Unique Requirements
- 50% revenue threshold: Higher revenue percentage requirement than most states
Colorado (CPA) — Unique Requirements
- AG rulemaking: Most detailed implementing regulations (4 CCR 904-3)
- Universal opt-out: First mandated (effective July 2024)
- Profiling opt-out scope: Broadest definition covering 7+ decision categories
- $20,000 penalties: Higher per-violation penalties under Consumer Protection Act
Connecticut (CTDPA) — Unique Requirements
- Dark pattern prohibition: Explicit statutory definition and prohibition
- Loyalty program exemption: Bona fide loyalty programs exempt from sale opt-out
- 25% revenue threshold: Lower than Virginia's 50%
Texas (TDPSA) — Unique Requirements
- No revenue/consumer threshold: Applies to all non-SBA-small businesses
- Data broker registration: Secretary of State registration requirement
- CUBI interaction: Separate biometric data law (up to $25,000/violation)
- Broadest applicability: Largest state population, lowest effective threshold
Oregon (OCPA) — Unique Requirements
- Nonprofit coverage: Applies to nonprofit organizations
- Third-party list right: Specific entity names, not just categories
- De-identified data: Most detailed compliance requirements
- Employee data partial exemption: Unique treatment of employee data
- Transgender/nonbinary status: Explicit sensitive data category
- 14-day cure period: Shortest cure period among states
Montana (MTDPA) — Unique Requirements
- 50,000 consumer threshold: Lowest consumer count threshold
- 15-day extension only: Shorter extension than most states' 45 days
- Air carrier exemption: Unique industry exemption
Kentucky (KPPA) — Unique Requirements
- January 2026 effective date: Most recently effective among this group
- 50% revenue threshold: Matches Virginia
Unified Privacy Program Architecture
Tier 1: Common Baseline (Apply Everywhere)
These requirements are common across all states and form the foundation:
- Privacy notice with categories of PI, purposes, rights, third parties, contact info
- Consumer rights portal supporting access, correct, delete, portability, opt-out
- 45-day response SLA with tracking and metrics
- Data minimization and purpose limitation controls
- Reasonable data security measures
- Non-discrimination protections
Show full SKILL.md (390 more words)Show less
Tier 2: High-Water Mark (Apply to Satisfy Strictest Requirement)
Where state requirements differ, apply the strictest standard universally:
| Area | Strictest Standard | Source State |
|---|---|---|
| Sensitive data consent | Opt-in consent before collection | VA, CO, CT, TX, OR, MT, KY |
| Dark pattern prohibition | Consent via dark patterns invalid | CT (explicit), all (implicit) |
| Response extension | 15-day extension only | MT (strictest) or accept state-by-state |
| Universal opt-out | Honor GPC signals | CA, CO, CT, MT |
| Profiling opt-out | Include 7+ decision categories | CO (broadest scope) |
| De-identified data | Full compliance program | OR (most detailed) |
| Privacy notice retention periods | Include per-category retention | CA (CPRA requirement) |
Tier 3: State-Specific (Apply Only Where Required)
| Requirement | State(s) | Implementation |
|---|---|---|
| "Do Not Sell or Share" link | CA | Homepage footer |
| "Limit Sensitive PI" link | CA | Adjacent to opt-out link |
| Specific third-party list | OR | Additional disclosure in Oregon responses |
| Data broker registration | TX | Secretary of State registration (if applicable) |
| Annual metrics disclosure | CA (10M+) | Privacy notice metrics section |
| Loyalty program exemption | CT | Program-specific terms |
| Nonprofit compliance | OR | Full program for Oregon nonprofit operations |
Implementation Strategy for Liberty Commerce Inc.
Approach: High-Water Mark with State-Specific Overlays
Liberty Commerce Inc. implements a unified privacy program at the highest common standard, with state-specific modules activated based on the consumer's state of residence.
Consumer Request Received
│
├─► Determine Consumer's State
│
├─► Apply Tier 1 Common Baseline
│ (Same for all states)
│
├─► Apply Tier 2 High-Water Mark
│ (Strictest standard, applied universally)
│
└─► Apply Tier 3 State-Specific Module
├─ California module: CPRA-specific disclosures, sensitive PI limit
├─ Oregon module: Third-party specific list
├─ Texas module: Data broker check
└─ Connecticut module: Loyalty program exemption assessmentHarmonized Privacy Notice Template
A multi-state privacy notice should include these sections to satisfy all eight laws:
- Categories of PI/personal data collected (all states)
- Categories of sensitive PI/sensitive data collected (all states)
- Purposes for each category (all states)
- Retention period or criteria per category (CA required; best practice all)
- Sources of PI (CA required; best practice all)
- Categories of third parties receiving PI (all states)
- Whether PI is sold or shared (all states)
- Whether targeted advertising is conducted (all non-CA states)
- Whether profiling is conducted (all non-CA states)
- Consumer rights and how to exercise (all states)
- Appeal process (VA, CO, CT, TX, OR, MT, KY)
- Contact information (all states)
- "Do Not Sell or Share" link (CA)
- "Limit Sensitive PI" link (CA)
- Universal opt-out disclosure (CA, CO, CT, MT)
- Last updated date (CA required; best practice all)
- Annual metrics (CA, if 10M+ consumers)
Key Regulatory References
- IAPP US State Comprehensive Privacy Law Comparison Chart (updated quarterly)
- CPPA Regulations 11 CCR §7001-7102
- Colorado AG Regulations 4 CCR 904-3
- Global Privacy Control Specification v1.0
© 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/multi-state-compliance 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
Multi State Compliance 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 |
|---|---|---|---|---|---|---|
| Multi State Compliance this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~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 | 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 Multi State Compliance
What does Multi State Compliance do?
Multi-state harmonized privacy compliance program. An agent skill from mukul975/Privacy-Data-Protection-Skills. Multi State Compliance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Multi-state harmonized privacy compliance program.
When should I use Multi State Compliance?
Multi State Compliance fits situations like: tasks that involve Privacy and GDPR.
How do I install Multi State Compliance in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill multi-state-compliance -a claude-code`. Or copy the skill folder (skills/privacy/multi-state-compliance in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/multi-state-compliance in your project. Claude Code loads it when a task matches its description.
How do I install Multi State Compliance in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill multi-state-compliance -a codex`. Or copy the skill folder (skills/privacy/multi-state-compliance in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/multi-state-compliance in your project. Codex loads it when a task matches its description.
Can I use Multi State Compliance 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 multi-state-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-state-compliance, .gemini/skills/multi-state-compliance, .github/skills/multi-state-compliance and .opencode/skills/multi-state-compliance in your project.
What does Multi State Compliance need to run?
Going by SKILL.md and its folder, Multi State Compliance needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Multi State Compliance 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 Multi State Compliance 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 Multi State Compliance use?
Multi State Compliance 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 Multi State Compliance 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 1.6k tokens, read only when the agent opens those files.
What are the alternatives to Multi State Compliance?
Skills that share tags, products or a category with Multi State Compliance: 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 Multi State Compliance?
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.