[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739AKSC7MYBF2KGSASVFH2V":3,"skill-same:01M739AKSC7MYBF2KGSASVFH2V":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M739AKSC7MYBF2KGSASVFH2V","gdpr-compliance",null,"Ensure GDPR compliance for marketing activities including consent management, data processing, privacy notices, and data subject rights","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fgdpr-compliance\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gdpr-compliance\ndescription: Ensure GDPR compliance for marketing activities including consent management, data processing, privacy notices, and data subject rights\nlicense: MIT\nmetadata:\n  author: ClawFu\n  version: 1.0.0\n  mcp-server: \"@clawfu\u002Fmcp-skills\"\n---\n\n# GDPR Compliance for Marketing\n\n> Ensure your marketing activities comply with GDPR requirements for consent, data processing, and privacy rights.\n\n## When to Use This Skill\n\n- Designing consent collection flows\n- Writing privacy notices\n- Auditing marketing data practices\n- Handling data subject requests\n- Documenting lawful basis\n\n## Methodology Foundation\n\nBased on **GDPR Articles 6, 7, 12-23** and **EDPB Guidelines**, covering:\n- Lawful basis determination\n- Consent requirements\n- Transparency obligations\n- Data subject rights\n- Documentation requirements\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Explains GDPR requirements | Business risk tolerance |\n| Drafts compliant language | Implementation priority |\n| Identifies gaps | Legal interpretation |\n| Creates documentation | DPO consultation needs |\n| Suggests controls | Resource allocation |\n\n## Instructions\n\n### Step 1: Lawful Basis Assessment\n\n**Six Lawful Bases (Article 6):**\n\n| Basis | Marketing Use | Documentation Needed |\n|-------|---------------|----------------------|\n| **Consent** | Email marketing, cookies, tracking | Consent records |\n| **Contract** | Customer communications | Contract terms |\n| **Legitimate Interest** | Soft opt-in, B2B marketing | LIA document |\n| **Legal Obligation** | Regulatory comms | Legal reference |\n| **Vital Interest** | Rarely applicable | - |\n| **Public Task** | Rarely applicable | - |\n\n**Marketing Activity Mapping:**\n\n| Activity | Typical Basis | Requirements |\n|----------|---------------|--------------|\n| Email newsletter | Consent | Double opt-in, easy unsubscribe |\n| Existing customer upsell | Legitimate Interest | LIA, opt-out available |\n| Cold B2B outreach | Legitimate Interest | LIA, clear identity |\n| Website cookies | Consent | Banner, granular choices |\n| Retargeting ads | Consent | Cookie consent |\n| Lead magnets | Consent | Clear purpose, separate consent |\n\n### Step 2: Consent Requirements\n\n**Valid Consent Criteria (Article 7):**\n| Requirement | What It Means | Example |\n|-------------|---------------|---------|\n| Freely given | No bundling, no penalty | Separate from T&Cs |\n| Specific | Clear purpose stated | \"Marketing emails about [X]\" |\n| Informed | Who, what, why explained | Privacy notice linked |\n| Unambiguous | Clear affirmative action | Unchecked checkbox |\n| Withdrawable | Easy to revoke | One-click unsubscribe |\n\n**Consent Record Requirements:**\n```\nRecord for each consent:\n- Who consented (identifier)\n- When (timestamp)\n- What they consented to (purpose)\n- How (mechanism)\n- What they were told (notice version)\n```\n\n### Step 3: Privacy Notice Requirements\n\n**Required Elements (Articles 13-14):**\n\n| Element | First-Party Data | Third-Party Data |\n|---------|------------------|------------------|\n| Controller identity | Required | Required |\n| DPO contact | If applicable | If applicable |\n| Purposes | Required | Required |\n| Lawful basis | Required | Required |\n| Recipients | Required | Required |\n| Transfers | If applicable | If applicable |\n| Retention | Required | Required |\n| Rights | Required | Required |\n| Withdrawal | If consent | If consent |\n| Complaint right | Required | Required |\n| Source | N\u002FA | Required |\n\n### Step 4: Data Subject Rights\n\n**Rights Framework:**\n\n| Right | Timeline | Marketing Impact |\n|-------|----------|------------------|\n| Access (Art. 15) | 1 month | Provide all marketing data |\n| Rectification (Art. 16) | 1 month | Update preferences |\n| Erasure (Art. 17) | 1 month | Remove from lists |\n| Restriction (Art. 18) | 1 month | Pause processing |\n| Portability (Art. 20) | 1 month | Export in machine format |\n| Objection (Art. 21) | Immediate for marketing | Stop direct marketing |\n\n### Step 5: Documentation & Records\n\n**Required Documentation:**\n1. Records of Processing Activities (ROPA)\n2. Legitimate Interest Assessments\n3. Consent records and mechanisms\n4. Privacy notices (versioned)\n5. Data Subject Request log\n6. Breach notification procedures\n\n## Examples\n\n### Example 1: Marketing Email Consent Flow\n\n**Input:**\n```\nDesign a GDPR-compliant consent flow for:\n- SaaS product newsletter\n- Product updates\n- Promotional offers\n- Third-party partner offers\n```\n\n**Output:**\n```\n## GDPR-Compliant Email Consent Flow\n\n### Consent Collection UI\n\n---\n\n**Signup Form Fields:**\n\n```\nEmail: [________________]\n\n[ ] I agree to receive the monthly newsletter with industry insights\n[ ] I agree to receive product updates and feature announcements\n[ ] I agree to receive promotional offers and discounts\n[ ] I agree to receive relevant offers from our trusted partners\n\n[Sign Up]\n\nBy signing up, you confirm you've read our [Privacy Notice].\nYou can withdraw consent anytime via unsubscribe link or contacting us.\n```\n\n**Design Requirements:**\n- All checkboxes unchecked by default\n- No \"select all\" option\n- Each purpose separate\n- Privacy notice linked, not buried\n- No dark patterns\n\n---\n\n### Consent Record Structure\n\n```json\n{\n  \"email\": \"user@example.com\",\n  \"consents\": [\n    {\n      \"purpose\": \"newsletter\",\n      \"granted\": true,\n      \"timestamp\": \"2026-01-31T10:30:00Z\",\n      \"source\": \"signup_form_v3\",\n      \"notice_version\": \"privacy_v2.1\"\n    },\n    {\n      \"purpose\": \"product_updates\",\n      \"granted\": true,\n      \"timestamp\": \"2026-01-31T10:30:00Z\",\n      \"source\": \"signup_form_v3\",\n      \"notice_version\": \"privacy_v2.1\"\n    },\n    {\n      \"purpose\": \"promotional\",\n      \"granted\": false,\n      \"timestamp\": null,\n      \"source\": null,\n      \"notice_version\": null\n    },\n    {\n      \"purpose\": \"third_party\",\n      \"granted\": false,\n      \"timestamp\": null,\n      \"source\": null,\n      \"notice_version\": null\n    }\n  ],\n  \"ip_address\": \"192.168.1.1\",\n  \"user_agent\": \"Mozilla\u002F5.0...\"\n}\n```\n\n---\n\n### Email Footer (Required)\n\n```\n---\nYou're receiving this because you subscribed to our [newsletter\u002Fupdates].\n\nManage preferences: [link]\nUnsubscribe from this list: [link]\nUnsubscribe from all: [link]\n\n[Company Name]\n[Address]\n[Contact Email]\n```\n\n---\n\n### Preference Center\n\n| Subscription | Status | Action |\n|--------------|--------|--------|\n| Monthly Newsletter | [ON\u002FOFF] | Industry insights and tips |\n| Product Updates | [ON\u002FOFF] | New features and improvements |\n| Promotional Offers | [ON\u002FOFF] | Discounts and special deals |\n| Partner Offers | [ON\u002FOFF] | Relevant third-party offers |\n\n[Update Preferences] [Unsubscribe from All]\n\n---\n\n### Compliance Checklist\n\n- [ ] All consents granular (separate checkboxes)\n- [ ] Checkboxes unchecked by default\n- [ ] Clear description of each purpose\n- [ ] Privacy notice accessible\n- [ ] Withdrawal mechanism clear\n- [ ] Consent records stored\n- [ ] Double opt-in implemented\n- [ ] Unsubscribe in every email\n- [ ] Preference center available\n```\n\n### Example 2: Legitimate Interest Assessment\n\n**Input:**\n```\nWe want to email our existing customers about related products.\nDo we need consent or can we use legitimate interest?\n```\n\n**Output:**\n```\n## Legitimate Interest Assessment: Customer Cross-Sell\n\n### Summary\n\nYou can likely rely on legitimate interest (not consent) for\nemailing existing customers about **similar** products, but must\ncomplete this assessment and offer easy opt-out.\n\n---\n\n### Three-Part LIA Test\n\n#### 1. Purpose Test: Is There a Legitimate Interest?\n\n**Interest:** Promote related products to existing customers\n**Legitimacy:** Yes - recognized business interest in customer development\n**Benefit:** Revenue growth, customer relationship deepening\n\n✅ **PASS**\n\n---\n\n#### 2. Necessity Test: Is Processing Necessary?\n\n| Question | Answer |\n|----------|--------|\n| Is email necessary to achieve the interest? | Yes - direct communication channel |\n| Is there a less intrusive way? | In-app notifications possible but less effective |\n| Is the processing proportionate? | Yes - limited frequency, relevant content |\n\n✅ **PASS** (with conditions)\n\n**Conditions:**\n- Limit to genuinely related products\n- Reasonable frequency (not daily)\n- Honor opt-outs immediately\n\n---\n\n#### 3. Balancing Test: Individual Rights vs. Your Interest\n\n| Factor | Assessment |\n|--------|------------|\n| Nature of data | Basic contact info - low sensitivity |\n| Reasonable expectations | Customers expect marketing from sellers |\n| Relationship | Existing customer relationship |\n| Impact on individual | Minor inconvenience, easy to opt out |\n| Safeguards | Opt-out in every email |\n\n✅ **PASS**\n\n---\n\n### Conclusion\n\n**Lawful Basis:** Legitimate Interest (Article 6(1)(f))\n\n**Requirements for Compliance:**\n\n1. **Document this LIA** and keep on file\n2. **Include in privacy notice:**\n   \"We may contact existing customers about similar products\n   based on legitimate interest. You can opt out at any time.\"\n3. **Easy opt-out:** Every email must have unsubscribe\n4. **Honor preferences:** Immediate suppression on opt-out\n5. **Similar products only:** Don't expand to unrelated offerings\n6. **Reasonable frequency:** No more than weekly\n\n---\n\n### Template Email Footer\n\n```\nYou're receiving this as a valued [Company] customer.\n\nNot interested in product updates?\n[Opt out of marketing] | [Manage preferences]\n\nThis email was sent based on our legitimate interest in keeping\ncustomers informed about relevant products. See our Privacy Notice\nfor details and your rights.\n```\n\n---\n\n### When This Doesn't Apply\n\nUse **consent** instead if:\n- Products are significantly different\n- Customer bought once 2+ years ago\n- You acquired data from third party\n- Customer previously opted out\n- Emails are primarily promotional (not informational)\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Explaining GDPR requirements\n- Drafting compliant language\n- Creating documentation templates\n- Identifying compliance gaps\n\n### What This Skill Cannot Do\n- Provide legal advice\n- Know your specific jurisdiction nuances\n- Guarantee regulatory acceptance\n- Replace DPO consultation\n\n### When to Escalate to Human\n- Complex cross-border transfers\n- Regulatory investigation\n- Data breach response\n- Novel processing activities\n\n## Iteration Guide\n\n**Follow-up Prompts:**\n- \"Draft the privacy notice section for [activity]\"\n- \"How do we handle a right to erasure request?\"\n- \"What documentation do we need for [processing]?\"\n- \"Is this cookie banner compliant?\"\n\n## References\n\n- GDPR Text (Regulation 2016\u002F679)\n- EDPB Guidelines on Consent\n- ICO Direct Marketing Guidance\n- CNIL Cookie Guidelines\n\n## Related Skills\n\n- `terms-analyzer` - Terms of service review\n- `contract-review` - DPA analysis\n- `nda-generator` - Confidentiality\n\n## Skill Metadata\n\n- **Domain**: Legal \u002F Marketing\n- **Complexity**: Intermediate\n- **Mode**: centaur\n- **Time to Value**: 1-2 hours per assessment\n- **Prerequisites**: Basic GDPR familiarity\n","# GDPR Compliance for Marketing\n\n> Ensure your marketing activities comply with GDPR requirements for consent, data processing, and privacy rights.\n\n## When to Use This Skill\n\n- Designing consent collection flows\n- Writing privacy notices\n- Auditing marketing data practices\n- Handling data subject requests\n- Documenting lawful basis\n\n## Methodology Foundation\n\nBased on **GDPR Articles 6, 7, 12-23** and **EDPB Guidelines**, covering:\n- Lawful basis determination\n- Consent requirements\n- Transparency obligations\n- Data subject rights\n- Documentation requirements\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Explains GDPR requirements | Business risk tolerance |\n| Drafts compliant language | Implementation priority |\n| Identifies gaps | Legal interpretation |\n| Creates documentation | DPO consultation needs |\n| Suggests controls | Resource allocation |\n\n## Instructions\n\n### Step 1: Lawful Basis Assessment\n\n**Six Lawful Bases (Article 6):**\n\n| Basis | Marketing Use | Documentation Needed |\n|-------|---------------|----------------------|\n| **Consent** | Email marketing, cookies, tracking | Consent records |\n| **Contract** | Customer communications | Contract terms |\n| **Legitimate Interest** | Soft opt-in, B2B marketing | LIA document |\n| **Legal Obligation** | Regulatory comms | Legal reference |\n| **Vital Interest** | Rarely applicable | - |\n| **Public Task** | Rarely applicable | - |\n\n**Marketing Activity Mapping:**\n\n| Activity | Typical Basis | Requirements |\n|----------|---------------|--------------|\n| Email newsletter | Consent | Double opt-in, easy unsubscribe |\n| Existing customer upsell | Legitimate Interest | LIA, opt-out available |\n| Cold B2B outreach | Legitimate Interest | LIA, clear identity |\n| Website cookies | Consent | Banner, granular choices |\n| Retargeting ads | Consent | Cookie consent |\n| Lead magnets | Consent | Clear purpose, separate consent |\n\n### Step 2: Consent Requirements\n\n**Valid Consent Criteria (Article 7):**\n| Requirement | What It Means | Example |\n|-------------|---------------|---------|\n| Freely given | No bundling, no penalty | Separate from T&Cs |\n| Specific | Clear purpose stated | \"Marketing emails about [X]\" |\n| Informed | Who, what, why explained | Privacy notice linked |\n| Unambiguous | Clear affirmative action | Unchecked checkbox |\n| Withdrawable | Easy to revoke | One-click unsubscribe |\n\n**Consent Record Requirements:**\n```\nRecord for each consent:\n- Who consented (identifier)\n- When (timestamp)\n- What they consented to (purpose)\n- How (mechanism)\n- What they were told (notice version)\n```\n\n### Step 3: Privacy Notice Requirements\n\n**Required Elements (Articles 13-14):**\n\n| Element | First-Party Data | Third-Party Data |\n|---------|------------------|------------------|\n| Controller identity | Required | Required |\n| DPO contact | If applicable | If applicable |\n| Purposes | Required | Required |\n| Lawful basis | Required | Required |\n| Recipients | Required | Required |\n| Transfers | If applicable | If applicable |\n| Retention | Required | Required |\n| Rights | Required | Required |\n| Withdrawal | If consent | If consent |\n| Complaint right | Required | Required |\n| Source | N\u002FA | Required |\n\n### Step 4: Data Subject Rights\n\n**Rights Framework:**\n\n| Right | Timeline | Marketing Impact |\n|-------|----------|------------------|\n| Access (Art. 15) | 1 month | Provide all marketing data |\n| Rectification (Art. 16) | 1 month | Update preferences |\n| Erasure (Art. 17) | 1 month | Remove from lists |\n| Restriction (Art. 18) | 1 month | Pause processing |\n| Portability (Art. 20) | 1 month | Export in machine format |\n| Objection (Art. 21) | Immediate for marketing | Stop direct marketing |\n\n### Step 5: Documentation & Records\n\n**Required Documentation:**\n1. Records of Processing Activities (ROPA)\n2. Legitimate Interest Assessments\n3. Consent records and mechanisms\n4. Privacy notices (versioned)\n5. Data Subject Request log\n6. Breach notification procedures\n\n## Examples\n\n### Example 1: Marketing Email Consent Flow\n\n**Input:**\n```\nDesign a GDPR-compliant consent flow for:\n- SaaS product newsletter\n- Product updates\n- Promotional offers\n- Third-party partner offers\n```\n\n**Output:**\n```\n## GDPR-Compliant Email Consent Flow\n\n### Consent Collection UI\n\n---\n\n**Signup Form Fields:**\n\n```\nEmail: [________________]\n\n[ ] I agree to receive the monthly newsletter with industry insights\n[ ] I agree to receive product updates and feature announcements\n[ ] I agree to receive promotional offers and discounts\n[ ] I agree to receive relevant offers from our trusted partners\n\n[Sign Up]\n\nBy signing up, you confirm you've read our [Privacy Notice].\nYou can withdraw consent anytime via unsubscribe link or contacting us.\n```\n\n**Design Requirements:**\n- All checkboxes unchecked by default\n- No \"select all\" option\n- Each purpose separate\n- Privacy notice linked, not buried\n- No dark patterns\n\n---\n\n### Consent Record Structure\n\n```json\n{\n  \"email\": \"user@example.com\",\n  \"consents\": [\n    {\n      \"purpose\": \"newsletter\",\n      \"granted\": true,\n      \"timestamp\": \"2026-01-31T10:30:00Z\",\n      \"source\": \"signup_form_v3\",\n      \"notice_version\": \"privacy_v2.1\"\n    },\n    {\n      \"purpose\": \"product_updates\",\n      \"granted\": true,\n      \"timestamp\": \"2026-01-31T10:30:00Z\",\n      \"source\": \"signup_form_v3\",\n      \"notice_version\": \"privacy_v2.1\"\n    },\n    {\n      \"purpose\": \"promotional\",\n      \"granted\": false,\n      \"timestamp\": null,\n      \"source\": null,\n      \"notice_version\": null\n    },\n    {\n      \"purpose\": \"third_party\",\n      \"granted\": false,\n      \"timestamp\": null,\n      \"source\": null,\n      \"notice_version\": null\n    }\n  ],\n  \"ip_address\": \"192.168.1.1\",\n  \"user_agent\": \"Mozilla\u002F5.0...\"\n}\n```\n\n---\n\n### Email Footer (Required)\n\n```\n---\nYou're receiving this because you subscribed to our [newsletter\u002Fupdates].\n\nManage preferences: [link]\nUnsubscribe from this list: [link]\nUnsubscribe from all: [link]\n\n[Company Name]\n[Address]\n[Contact Email]\n```\n\n---\n\n### Preference Center\n\n| Subscription | Status | Action |\n|--------------|--------|--------|\n| Monthly Newsletter | [ON\u002FOFF] | Industry insights and tips |\n| Product Updates | [ON\u002FOFF] | New features and improvements |\n| Promotional Offers | [ON\u002FOFF] | Discounts and special deals |\n| Partner Offers | [ON\u002FOFF] | Relevant third-party offers |\n\n[Update Preferences] [Unsubscribe from All]\n\n---\n\n### Compliance Checklist\n\n- [ ] All consents granular (separate checkboxes)\n- [ ] Checkboxes unchecked by default\n- [ ] Clear description of each purpose\n- [ ] Privacy notice accessible\n- [ ] Withdrawal mechanism clear\n- [ ] Consent records stored\n- [ ] Double opt-in implemented\n- [ ] Unsubscribe in every email\n- [ ] Preference center available\n```\n\n### Example 2: Legitimate Interest Assessment\n\n**Input:**\n```\nWe want to email our existing customers about related products.\nDo we need consent or can we use legitimate interest?\n```\n\n**Output:**\n```\n## Legitimate Interest Assessment: Customer Cross-Sell\n\n### Summary\n\nYou can likely rely on legitimate interest (not consent) for\nemailing existing customers about **similar** products, but must\ncomplete this assessment and offer easy opt-out.\n\n---\n\n### Three-Part LIA Test\n\n#### 1. Purpose Test: Is There a Legitimate Interest?\n\n**Interest:** Promote related products to existing customers\n**Legitimacy:** Yes - recognized business interest in customer development\n**Benefit:** Revenue growth, customer relationship deepening\n\n✅ **PASS**\n\n---\n\n#### 2. Necessity Test: Is Processing Necessary?\n\n| Question | Answer |\n|----------|--------|\n| Is email necessary to achieve the interest? | Yes - direct communication channel |\n| Is there a less intrusive way? | In-app notifications possible but less effective |\n| Is the processing proportionate? | Yes - limited frequency, relevant content |\n\n✅ **PASS** (with conditions)\n\n**Conditions:**\n- Limit to genuinely related products\n- Reasonable frequency (not daily)\n- Honor opt-outs immediately\n\n---\n\n#### 3. Balancing Test: Individual Rights vs. Your Interest\n\n| Factor | Assessment |\n|--------|------------|\n| Nature of data | Basic contact info - low sensitivity |\n| Reasonable expectations | Customers expect marketing from sellers |\n| Relationship | Existing customer relationship |\n| Impact on individual | Minor inconvenience, easy to opt out |\n| Safeguards | Opt-out in every email |\n\n✅ **PASS**\n\n---\n\n### Conclusion\n\n**Lawful Basis:** Legitimate Interest (Article 6(1)(f))\n\n**Requirements for Compliance:**\n\n1. **Document this LIA** and keep on file\n2. **Include in privacy notice:**\n   \"We may contact existing customers about similar products\n   based on legitimate interest. You can opt out at any time.\"\n3. **Easy opt-out:** Every email must have unsubscribe\n4. **Honor preferences:** Immediate suppression on opt-out\n5. **Similar products only:** Don't expand to unrelated offerings\n6. **Reasonable frequency:** No more than weekly\n\n---\n\n### Template Email Footer\n\n```\nYou're receiving this as a valued [Company] customer.\n\nNot interested in product updates?\n[Opt out of marketing] | [Manage preferences]\n\nThis email was sent based on our legitimate interest in keeping\ncustomers informed about relevant products. See our Privacy Notice\nfor details and your rights.\n```\n\n---\n\n### When This Doesn't Apply\n\nUse **consent** instead if:\n- Products are significantly different\n- Customer bought once 2+ years ago\n- You acquired data from third party\n- Customer previously opted out\n- Emails are primarily promotional (not informational)\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Explaining GDPR requirements\n- Drafting compliant language\n- Creating documentation templates\n- Identifying compliance gaps\n\n### What This Skill Cannot Do\n- Provide legal advice\n- Know your specific jurisdiction nuances\n- Guarantee regulatory acceptance\n- Replace DPO consultation\n\n### When to Escalate to Human\n- Complex cross-border transfers\n- Regulatory investigation\n- Data breach response\n- Novel processing activities\n\n## Iteration Guide\n\n**Follow-up Prompts:**\n- \"Draft the privacy notice section for [activity]\"\n- \"How do we handle a right to erasure request?\"\n- \"What documentation do we need for [processing]?\"\n- \"Is this cookie banner compliant?\"\n\n## References\n\n- GDPR Text (Regulation 2016\u002F679)\n- EDPB Guidelines on Consent\n- ICO Direct Marketing Guidance\n- CNIL Cookie Guidelines\n\n## Related Skills\n\n- `terms-analyzer` - Terms of service review\n- `contract-review` - DPA analysis\n- `nda-generator` - Confidentiality\n\n## Skill Metadata\n\n- **Domain**: Legal \u002F Marketing\n- **Complexity**: Intermediate\n- **Mode**: centaur\n- **Time to Value**: 1-2 hours per assessment\n- **Prerequisites**: Basic GDPR familiarity\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25,"mcp-server":26},"ClawFu","1.0.0","@clawfu\u002Fmcp-skills","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fgdpr-compliance",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add roohe\u002Fagentic-super-skills --skill gdpr-compliance",{"tool":41,"command":42},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill gdpr-compliance",{"tool":44,"command":45},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill gdpr-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fgdpr-compliance\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]