[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EM622WNZZ48VSZMHT97FB9":3,"skill-same:01M7EM622WNZZ48VSZMHT97FB9":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7EM622WNZZ48VSZMHT97FB9","ccpa-cpra-privacy-rights",null,"Implements California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA)—Cal. Civ. Code §1798.100 et seq.—covering consumer rights to know, delete, correct, opt-out of sale\u002Fshare, and limit use of sensitive personal information, plus DSAR workflows, privacy notices, and service provider contracts for AI\u002Fagent data handling. Trigger when processing California residents' personal information, operating DSAR programs, reviewing agent\u002FLLM data flows for CPRA compliance, or auditing privacy notices and vendor agreements. Do not use for HIPAA-covered PHI workflows (use hipaa-privacy-minimum-necessary), PCI cardholder encryption (use pci-dss-encryption-key-management), or general vendor SOC reports without CPRA scope (use vendor-third-party-risk).","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fccpa-cpra-privacy-rights\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ccpa-cpra-privacy-rights\ndescription: Implements California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA)—Cal. Civ. Code §1798.100 et seq.—covering consumer rights to know, delete, correct, opt-out of sale\u002Fshare, and limit use of sensitive personal information, plus DSAR workflows, privacy notices, and service provider contracts for AI\u002Fagent data handling. Trigger when processing California residents' personal information, operating DSAR programs, reviewing agent\u002FLLM data flows for CPRA compliance, or auditing privacy notices and vendor agreements. Do not use for HIPAA-covered PHI workflows (use hipaa-privacy-minimum-necessary), PCI cardholder encryption (use pci-dss-encryption-key-management), or general vendor SOC reports without CPRA scope (use vendor-third-party-risk).\nsource: \"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills\"\nsource_repository: \"vaquarkhan\u002Fcompliance-agent-skills\"\nsource_path: \"skills\u002Fccpa-cpra-privacy-rights\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# CCPA \u002F CPRA Privacy Rights\n\n## Overview\n\nThis skill operationalizes **California privacy law** under **CCPA as amended by CPRA** (operationalized by the **California Privacy Protection Agency**, CPPA). Key statutes:\n\n| Topic | Primary citations |\n| --- | --- |\n| Consumer rights | Cal. Civ. Code **§1798.100–§1798.135** |\n| Sensitive PI limitations | **§1798.121** (limit use\u002Fdisclosure) |\n| Opt-out of sale\u002Fshare | **§1798.120**, **§1798.135** (Do Not Sell or Share) |\n| Right to correct | **§1798.106** (CPRA addition) |\n| Right to delete | **§1798.105**, **§1798.110(c)(7)** |\n| Right to know | **§1798.110**, **§1798.115** |\n| Service providers \u002F contractors | **§1798.140(ag)**, **§1798.140(j)**, **§1798.140(v)** |\n| Automated decision-making | **§1798.185(a)(16)** (regulations) |\n| Privacy policy requirements | **§1798.130(a)(5)**, **§1798.135(b)** |\n\n**Personal information (PI)** includes identifiers, commercial information, biometric data, geolocation, and inferences—**prompts and agent logs may contain PI** even when not HIPAA PHI.\n\n**Sensitive personal information (SPI)** includes SSN, precise geolocation, racial\u002Fethnic origin, mail\u002Femail\u002Fpassword in combination with credentials, and contents of mail\u002Femail (with exceptions).\n\nAI\u002Fagent systems must address: **what PI enters LLM prompts**, **retention by LLM vendors**, **subprocessor chains**, and **DSAR fulfillment** across agent databases and logs.\n\n## When to Use\n\nUse this skill when:\n\n- **Processing California residents' PI** in products, analytics, or agent workflows\n- Building or auditing **Data Subject Access Request (DSAR)** \u002F consumer rights request programs\n- Reviewing **privacy policies**, **notice at collection**, and **CPRA addendum** disclosures\n- Assessing **sale\u002Fshare** of PI (including cross-context behavioral advertising) and **opt-out** mechanisms\n- Drafting or reviewing **service provider agreements** for LLM, MCP, or analytics vendors\n- Evaluating **agent prompt\u002Flogging** practices for PI minimization and deletion capability\n- Responding to **CPPA enforcement trends** or customer CPRA questionnaires\n\nDo **not** use this skill when:\n\n- HIPAA Security Rule technical controls only (use `hipaa-technical-safeguards`)\n- PCI PAN encryption and key management (use `pci-dss-encryption-key-management`)\n- SOC 2 TSC-only audits without California PI (use `soc2-trust-services-criteria`)\n- Breach notification under HIPAA\u002Fstate breach laws without CPRA rights scope (use `breach-incident-response`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Scope and role determination\n\n1. Determine if organization is **business**, **service provider**, **contractor**, or **third party** per §1798.140 definitions.\n2. Map **data flows** for California consumers:\n   - Web\u002Fapp collection → agent prompts → LLM API → logs → MCP Postgres evidence store\n3. Identify **business purposes** vs **commercial purposes** (sale\u002Fshare) per §1798.140.\n4. Document **sensitive PI** categories collected—triggers §1798.121 **Limit the Use** rights.\n5. Artifact: `cpra-data-map-{id}.json`.\n\n### Step 2: Consumer rights inventory\n\nFor each right, document statutory basis, process owner, SLA, and systems affected:\n\n| Right | Citation | SLA (recommended) | Agent\u002FLLM considerations |\n| --- | --- | --- | --- |\n| Know (access) | §1798.110, §1798.115 | 45 days + extension | Export prompts\u002Flogs with redaction of other consumers' PI |\n| Delete | §1798.105 | 45 days | Delete from agent DB, vector stores, LLM vendor if contractually required |\n| Correct | §1798.106 | 45 days | Update source systems; re-index embeddings if used |\n| Opt-out of sale\u002Fshare | §1798.120 | 15 business days for opt-out processing | Stop sharing ad identifiers; review analytics SDKs |\n| Limit SPI use | §1798.121 | As soon as feasible | Restrict SPI in agent prompts to minimum necessary |\n| Non-discrimination | §1798.125 | Immediate | No denial of service for exercising rights |\n\n### Step 3: DSAR intake and verification\n\n1. Provide **two or more designated methods** for submission (§1798.130(a)(1))—web form, toll-free, email.\n2. **Verify consumer identity** to reasonable degree (§1798.140)—do not over-collect verification PI.\n3. For agent-related requests:\n   - Query internal stores: session logs, `redaction.py` token maps (may contain PI—handle as SPI)\n   - Issue **vendor requests** to LLM provider if they hold PI on your behalf (requires contract terms)\n4. Log DSAR in tracker: request ID, type, receipt date, verification status, due date, outcome.\n5. **Do not** send raw consumer PI to LLM for DSAR processing—use redaction or structured DB queries via **Postgres MCP** (read-only, audited).\n\n### Step 4: DSAR fulfillment workflow\n\n1. **Access (Know)**:\n   - Categories and specific pieces of PI collected (§1798.110)\n   - Sources, business\u002Fcommercial purposes, third parties disclosed to (§1798.115)\n   - Deliver in portable format; exclude other consumers' data and trade secrets\n2. **Delete**:\n   - Direct service providers\u002Fcontractors to delete (§1798.105(c))\n   - Delete agent session data, cached prompts, analytics events\n   - Document exceptions: legal retention, security incidents, complete transaction\n3. **Correct**:\n   - Correct inaccurate PI; instruct service providers per §1798.106\n4. **Opt-out \u002F Limit**:\n   - Honor **Global Privacy Control (GPC)** as valid opt-out signal where required (CPPA regulations)\n   - Implement **Limit SPI** link if collecting SPI for non-essential purposes (§1798.135(a)(2))\n\n### Step 5: Privacy notices and disclosures\n\n1. Review **privacy policy** for CPRA-required elements (§1798.130(a)(5)):\n   - Categories of PI collected, purposes, retention, sale\u002Fshare practices\n   - Consumer rights and how to exercise them\n   - SPI categories and Limit the Use link if applicable\n   - **Automated decision-making** disclosure if applicable (§1798.185)\n2. **Notice at collection** at each collection point—including agent chat interfaces.\n3. **Annual privacy metrics** (if business meets volume thresholds)—requests received and median response times.\n4. Artifact: `privacy-notice-gap-analysis-{id}.md`.\n\n### Step 6: Service provider and LLM vendor contracts\n\n1. Verify written contracts prohibit **selling\u002Fsharing** PI and restrict use to **business purposes** (§1798.140(ag)).\n2. For LLM\u002Fagent vendors, contract must address:\n   - **No training** on consumer PI unless disclosed and permitted\n   - **Deletion** support for DSAR\n   - **Subprocessor** notification\n   - **Security** requirements comparable to CPRA §1798.100(e)\n3. Cross-ref `vendor-third-party-risk` for assessment methodology and `hipaa-baa-vendor-assessment` only if PHI overlap exists.\n4. Distinguish **service provider** vs **third party**—third party relationships require consumer notice and opt-out where applicable.\n\n### Step 7: Agent and MCP data handling controls\n\n1. **Minimization**: Do not pass consumer PI to LLM beyond task necessity—align with `hipaa-phi-redaction-pipeline` patterns for tokenization.\n2. **Retention**: Define TTL for agent logs; automated deletion jobs.\n3. **Sale\u002Fshare analysis**: Review whether analytics, advertising integrations, or data licensing constitute **sale** or **sharing** under CPRA definitions.\n4. **MCP logging**: Ensure Slack\u002FPostgres MCP does not persist consumer PI in cleartext—see `mcp-compliance-integration`.\n5. **GPC\u002Fopt-out**: Technical honor signal before agent enriches profile with shared data.\n\n### Step 8: Findings and remediation\n\n1. Emit findings with CPRA citations:\n\n```yaml\nid: FIND-CPRA-001\nseverity: HIGH\ncontrol_id: CCPA-1798.105\nobservation: \"Agent session store lacks delete workflow for DSAR\"\nrecommendation: \"Implement deletion API covering Postgres evidence DB and 30-day LLM vendor purge SLA\"\nowner: \"\"\ndue_date: null\nstatus: open\n```\n\n2. Package evidence: data map, notice copies, DSAR samples (redacted), contract clauses, policy versions with hashes.\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We're B2B only, so CCPA doesn't apply.\" | CPRA applies when you process **California consumers'** PI—B2B contacts may still be consumers; assess actual data not business model label. |\n| \"LLM vendor is a service provider, so no disclosure needed.\" | **Service provider status requires a qualifying contract** and limited use—default API terms often fail; verify §1798.140(ag). |\n| \"Agent logs aren't 'personal information'.\" | Logs with identifiers, inferences, or linked account data **are PI** under §1798.140(v). |\n| \"We don't sell data—we just share with ad partners.\" | CPRA **\"share\"** for cross-context behavioral advertising triggers **opt-out** rights—distinct from colloquial \"sale.\" |\n| \"DSAR delete is impossible because LLM trained on it.\" | Training use should be **contractually prohibited**; if occurred, legal review required—do not claim impossibility without vendor confirmation. |\n| \"GPC doesn't apply to us yet.\" | CPPA regulations treat **GPC as opt-out signal** for applicable businesses—implement technical honor or document exemption basis with counsel. |\n\n## Red Flags\n\n- Consumer PI sent to LLM without service provider agreement restricting secondary use\n- No mechanism to delete agent session history per verified DSAR\n- Privacy policy missing SPI categories or Limit the Use link when SPI collected\n- Analytics\u002Fad SDKs active after consumer opt-out of sale\u002Fshare\n- Postgres MCP evidence database retains consumer PI indefinitely without retention policy\n- DSAR responses include other consumers' PI (over-disclosure)\n- Verification process collects more PI than necessary (SSN required for all requests)\n- GPC signal ignored on website where regulations apply\n\n## Verification\n\n- [ ] Data map complete for California consumer PI including agent\u002FLLM flows\n- [ ] Business vs service provider vs third party roles documented per vendor\n- [ ] All six consumer rights have documented processes, owners, and SLAs\n- [ ] DSAR intake, verification, and fulfillment tested with sample request (synthetic data)\n- [ ] Privacy policy and notice at collection reviewed against §1798.130\u002F§1798.135\n- [ ] LLM and MCP vendor contracts include CPRA service provider provisions\n- [ ] Sale\u002Fshare analysis complete with opt-out and GPC technical controls verified\n- [ ] SPI Limit the Use mechanism implemented where required\n- [ ] Agent log retention and deletion automation documented and tested\n- [ ] Evidence package hashed with engagement ID and audit timestamp\n","# CCPA \u002F CPRA Privacy Rights\n\n## Overview\n\nThis skill operationalizes **California privacy law** under **CCPA as amended by CPRA** (operationalized by the **California Privacy Protection Agency**, CPPA). Key statutes:\n\n| Topic | Primary citations |\n| --- | --- |\n| Consumer rights | Cal. Civ. Code **§1798.100–§1798.135** |\n| Sensitive PI limitations | **§1798.121** (limit use\u002Fdisclosure) |\n| Opt-out of sale\u002Fshare | **§1798.120**, **§1798.135** (Do Not Sell or Share) |\n| Right to correct | **§1798.106** (CPRA addition) |\n| Right to delete | **§1798.105**, **§1798.110(c)(7)** |\n| Right to know | **§1798.110**, **§1798.115** |\n| Service providers \u002F contractors | **§1798.140(ag)**, **§1798.140(j)**, **§1798.140(v)** |\n| Automated decision-making | **§1798.185(a)(16)** (regulations) |\n| Privacy policy requirements | **§1798.130(a)(5)**, **§1798.135(b)** |\n\n**Personal information (PI)** includes identifiers, commercial information, biometric data, geolocation, and inferences—**prompts and agent logs may contain PI** even when not HIPAA PHI.\n\n**Sensitive personal information (SPI)** includes SSN, precise geolocation, racial\u002Fethnic origin, mail\u002Femail\u002Fpassword in combination with credentials, and contents of mail\u002Femail (with exceptions).\n\nAI\u002Fagent systems must address: **what PI enters LLM prompts**, **retention by LLM vendors**, **subprocessor chains**, and **DSAR fulfillment** across agent databases and logs.\n\n## When to Use\n\nUse this skill when:\n\n- **Processing California residents' PI** in products, analytics, or agent workflows\n- Building or auditing **Data Subject Access Request (DSAR)** \u002F consumer rights request programs\n- Reviewing **privacy policies**, **notice at collection**, and **CPRA addendum** disclosures\n- Assessing **sale\u002Fshare** of PI (including cross-context behavioral advertising) and **opt-out** mechanisms\n- Drafting or reviewing **service provider agreements** for LLM, MCP, or analytics vendors\n- Evaluating **agent prompt\u002Flogging** practices for PI minimization and deletion capability\n- Responding to **CPPA enforcement trends** or customer CPRA questionnaires\n\nDo **not** use this skill when:\n\n- HIPAA Security Rule technical controls only (use `hipaa-technical-safeguards`)\n- PCI PAN encryption and key management (use `pci-dss-encryption-key-management`)\n- SOC 2 TSC-only audits without California PI (use `soc2-trust-services-criteria`)\n- Breach notification under HIPAA\u002Fstate breach laws without CPRA rights scope (use `breach-incident-response`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Scope and role determination\n\n1. Determine if organization is **business**, **service provider**, **contractor**, or **third party** per §1798.140 definitions.\n2. Map **data flows** for California consumers:\n   - Web\u002Fapp collection → agent prompts → LLM API → logs → MCP Postgres evidence store\n3. Identify **business purposes** vs **commercial purposes** (sale\u002Fshare) per §1798.140.\n4. Document **sensitive PI** categories collected—triggers §1798.121 **Limit the Use** rights.\n5. Artifact: `cpra-data-map-{id}.json`.\n\n### Step 2: Consumer rights inventory\n\nFor each right, document statutory basis, process owner, SLA, and systems affected:\n\n| Right | Citation | SLA (recommended) | Agent\u002FLLM considerations |\n| --- | --- | --- | --- |\n| Know (access) | §1798.110, §1798.115 | 45 days + extension | Export prompts\u002Flogs with redaction of other consumers' PI |\n| Delete | §1798.105 | 45 days | Delete from agent DB, vector stores, LLM vendor if contractually required |\n| Correct | §1798.106 | 45 days | Update source systems; re-index embeddings if used |\n| Opt-out of sale\u002Fshare | §1798.120 | 15 business days for opt-out processing | Stop sharing ad identifiers; review analytics SDKs |\n| Limit SPI use | §1798.121 | As soon as feasible | Restrict SPI in agent prompts to minimum necessary |\n| Non-discrimination | §1798.125 | Immediate | No denial of service for exercising rights |\n\n### Step 3: DSAR intake and verification\n\n1. Provide **two or more designated methods** for submission (§1798.130(a)(1))—web form, toll-free, email.\n2. **Verify consumer identity** to reasonable degree (§1798.140)—do not over-collect verification PI.\n3. For agent-related requests:\n   - Query internal stores: session logs, `redaction.py` token maps (may contain PI—handle as SPI)\n   - Issue **vendor requests** to LLM provider if they hold PI on your behalf (requires contract terms)\n4. Log DSAR in tracker: request ID, type, receipt date, verification status, due date, outcome.\n5. **Do not** send raw consumer PI to LLM for DSAR processing—use redaction or structured DB queries via **Postgres MCP** (read-only, audited).\n\n### Step 4: DSAR fulfillment workflow\n\n1. **Access (Know)**:\n   - Categories and specific pieces of PI collected (§1798.110)\n   - Sources, business\u002Fcommercial purposes, third parties disclosed to (§1798.115)\n   - Deliver in portable format; exclude other consumers' data and trade secrets\n2. **Delete**:\n   - Direct service providers\u002Fcontractors to delete (§1798.105(c))\n   - Delete agent session data, cached prompts, analytics events\n   - Document exceptions: legal retention, security incidents, complete transaction\n3. **Correct**:\n   - Correct inaccurate PI; instruct service providers per §1798.106\n4. **Opt-out \u002F Limit**:\n   - Honor **Global Privacy Control (GPC)** as valid opt-out signal where required (CPPA regulations)\n   - Implement **Limit SPI** link if collecting SPI for non-essential purposes (§1798.135(a)(2))\n\n### Step 5: Privacy notices and disclosures\n\n1. Review **privacy policy** for CPRA-required elements (§1798.130(a)(5)):\n   - Categories of PI collected, purposes, retention, sale\u002Fshare practices\n   - Consumer rights and how to exercise them\n   - SPI categories and Limit the Use link if applicable\n   - **Automated decision-making** disclosure if applicable (§1798.185)\n2. **Notice at collection** at each collection point—including agent chat interfaces.\n3. **Annual privacy metrics** (if business meets volume thresholds)—requests received and median response times.\n4. Artifact: `privacy-notice-gap-analysis-{id}.md`.\n\n### Step 6: Service provider and LLM vendor contracts\n\n1. Verify written contracts prohibit **selling\u002Fsharing** PI and restrict use to **business purposes** (§1798.140(ag)).\n2. For LLM\u002Fagent vendors, contract must address:\n   - **No training** on consumer PI unless disclosed and permitted\n   - **Deletion** support for DSAR\n   - **Subprocessor** notification\n   - **Security** requirements comparable to CPRA §1798.100(e)\n3. Cross-ref `vendor-third-party-risk` for assessment methodology and `hipaa-baa-vendor-assessment` only if PHI overlap exists.\n4. Distinguish **service provider** vs **third party**—third party relationships require consumer notice and opt-out where applicable.\n\n### Step 7: Agent and MCP data handling controls\n\n1. **Minimization**: Do not pass consumer PI to LLM beyond task necessity—align with `hipaa-phi-redaction-pipeline` patterns for tokenization.\n2. **Retention**: Define TTL for agent logs; automated deletion jobs.\n3. **Sale\u002Fshare analysis**: Review whether analytics, advertising integrations, or data licensing constitute **sale** or **sharing** under CPRA definitions.\n4. **MCP logging**: Ensure Slack\u002FPostgres MCP does not persist consumer PI in cleartext—see `mcp-compliance-integration`.\n5. **GPC\u002Fopt-out**: Technical honor signal before agent enriches profile with shared data.\n\n### Step 8: Findings and remediation\n\n1. Emit findings with CPRA citations:\n\n```yaml\nid: FIND-CPRA-001\nseverity: HIGH\ncontrol_id: CCPA-1798.105\nobservation: \"Agent session store lacks delete workflow for DSAR\"\nrecommendation: \"Implement deletion API covering Postgres evidence DB and 30-day LLM vendor purge SLA\"\nowner: \"\"\ndue_date: null\nstatus: open\n```\n\n2. Package evidence: data map, notice copies, DSAR samples (redacted), contract clauses, policy versions with hashes.\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We're B2B only, so CCPA doesn't apply.\" | CPRA applies when you process **California consumers'** PI—B2B contacts may still be consumers; assess actual data not business model label. |\n| \"LLM vendor is a service provider, so no disclosure needed.\" | **Service provider status requires a qualifying contract** and limited use—default API terms often fail; verify §1798.140(ag). |\n| \"Agent logs aren't 'personal information'.\" | Logs with identifiers, inferences, or linked account data **are PI** under §1798.140(v). |\n| \"We don't sell data—we just share with ad partners.\" | CPRA **\"share\"** for cross-context behavioral advertising triggers **opt-out** rights—distinct from colloquial \"sale.\" |\n| \"DSAR delete is impossible because LLM trained on it.\" | Training use should be **contractually prohibited**; if occurred, legal review required—do not claim impossibility without vendor confirmation. |\n| \"GPC doesn't apply to us yet.\" | CPPA regulations treat **GPC as opt-out signal** for applicable businesses—implement technical honor or document exemption basis with counsel. |\n\n## Red Flags\n\n- Consumer PI sent to LLM without service provider agreement restricting secondary use\n- No mechanism to delete agent session history per verified DSAR\n- Privacy policy missing SPI categories or Limit the Use link when SPI collected\n- Analytics\u002Fad SDKs active after consumer opt-out of sale\u002Fshare\n- Postgres MCP evidence database retains consumer PI indefinitely without retention policy\n- DSAR responses include other consumers' PI (over-disclosure)\n- Verification process collects more PI than necessary (SSN required for all requests)\n- GPC signal ignored on website where regulations apply\n\n## Verification\n\n- [ ] Data map complete for California consumer PI including agent\u002FLLM flows\n- [ ] Business vs service provider vs third party roles documented per vendor\n- [ ] All six consumer rights have documented processes, owners, and SLAs\n- [ ] DSAR intake, verification, and fulfillment tested with sample request (synthetic data)\n- [ ] Privacy policy and notice at collection reviewed against §1798.130\u002F§1798.135\n- [ ] LLM and MCP vendor contracts include CPRA service provider provisions\n- [ ] Sale\u002Fshare analysis complete with opt-out and GPC technical controls verified\n- [ ] SPI Limit the Use mechanism implemented where required\n- [ ] Agent log retention and deletion automation documented and tested\n- [ ] Evidence package hashed with engagement ID and audit timestamp\n",{"name":5,"source":24,"license":15,"description":7,"imported_at":25,"source_path":26,"source_repository":27},"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills","2026-09-20","skills\u002Fccpa-cpra-privacy-rights\u002FSKILL.md","vaquarkhan\u002Fcompliance-agent-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Fccpa-cpra-privacy-rights","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ccpa-cpra-privacy-rights",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ccpa-cpra-privacy-rights",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ccpa-cpra-privacy-rights","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fccpa-cpra-privacy-rights\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]