[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J2MHY8EE3FDV6FZKVGJYNW":3,"skill-same:01M6J2MHY8EE3FDV6FZKVGJYNW":108},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6J2MHY8EE3FDV6FZKVGJYNW","gdpr-valid-consent",null,"Guide for implementing GDPR-valid consent under Article 7 conditions and Article 4(11) definition. Covers five core requirements: freely given, specific, informed, unambiguous, and clear affirmative action. Includes pre-ticked boxes prohibition per Planet49 CJEU C-673\u002F17, consent form audit checklist, and practical implementation patterns.","onfire7777\u002Funiversal-ai-skills-library","onfire7777","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F240866566?v=4","01M6HZJCF2QEW8DY7HE1JDKGK2","Jake B","01M6HZJCKK8SEXKN76V9SGKZ12",17,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"gdpr","gdpr valid consent","valid","practical","for","implementing","action","form","form audit","clear","article","requirements","consent form","patterns","checklist","implementation","management","privacy","audit","core","2026-11-10 10:12:30",false,"---\nname: gdpr-valid-consent\nlicense: Apache-2.0\ndescription: 'Guide for implementing GDPR-valid consent under Article 7 conditions and Article 4(11) definition. Covers five core requirements: freely given, specific, informed, unambiguous, and clear affirmative action. Includes pre-ticked boxes prohibition per Planet49 CJEU C-673\u002F17, consent form audit checklist, and practical implementation patterns.'\nmetadata:\n  metadata:\n    author: mukul975\n    version: '1.0'\n    domain: privacy\n    subdomain: consent-management\n    tags: gdpr-consent, article-7, valid-consent, affirmative-action, consent-audit\n---\n# Implementing GDPR-Valid Consent\n\n## Overview\n\nValid consent under the GDPR is defined in Article 4(11) as \"any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.\" Article 7 sets out the conditions for consent, and Recital 32 clarifies that silence, pre-ticked boxes, or inactivity do not constitute consent.\n\nThe Court of Justice of the European Union (CJEU) reinforced this in Case C-673\u002F17 (Planet49 GmbH, October 1, 2019), ruling that pre-ticked checkboxes do not constitute valid consent for placing cookies, and that consent must be specific to each processing purpose.\n\n## The Five Requirements of Valid Consent\n\n### 1. Freely Given (Article 7(4), Recitals 42-43)\n\nConsent is not freely given if:\n\n- There is a clear imbalance between the data subject and the controller (e.g., employer-employee relationships, public authority-citizen relationships)\n- Consent is bundled as a non-negotiable condition of a service (the \"conditionality test\" under Article 7(4))\n- The data subject suffers detriment for refusing or withdrawing consent\n- There is no genuine choice or the individual feels compelled to consent\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. separates consent for core cloud storage services from consent for analytics and marketing. Users who decline marketing consent retain full access to storage functionality. The sign-up flow explicitly states: \"Declining optional data processing will not affect your access to CloudVault storage services.\"\n\n### 2. Specific (Article 6(1)(a), Recital 32)\n\nConsent must be:\n\n- Granular: separate consent for each distinct purpose\n- Named: the controller and any third-party controllers must be specifically identified\n- Purpose-limited: clearly linked to a defined processing purpose\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. presents three separate consent requests during onboarding:\n- \"Allow CloudVault SaaS Inc. to analyze your file usage patterns to recommend storage optimization\" (Purpose: Service improvement)\n- \"Allow CloudVault SaaS Inc. to send you product update emails\" (Purpose: Direct marketing)\n- \"Allow CloudVault SaaS Inc. to share anonymized usage statistics with Datalytics Partners Ltd. for industry benchmarking\" (Purpose: Third-party analytics)\n\n### 3. Informed (Article 13, Recitals 42, 60)\n\nBefore consenting, the data subject must be told at minimum:\n\n- The identity of the controller (CloudVault SaaS Inc., registered at 42 Innovation Drive, Dublin, D02 YX88, Ireland)\n- The purpose of each processing operation for which consent is sought\n- The type of data collected\n- The right to withdraw consent at any time\n- Information about automated decision-making, including profiling (Article 22(2)(c))\n- Risks of data transfers to third countries without an adequacy decision or appropriate safeguards (relevant if Article 49(1)(a) explicit consent applies)\n\n**CloudVault SaaS Inc. Implementation:**\nEach consent request includes a layered notice: a short-form summary visible immediately and a \"Learn More\" expandable section with full Article 13 information. The language is plain English at a Flesch-Kincaid grade level of 8 or below.\n\n### 4. Unambiguous Indication\n\nThe data subject's intention must be clear. According to Recital 32:\n\n- Consent requires a clear affirmative act\n- Silence, pre-ticked boxes, or inactivity do not constitute consent (confirmed in CJEU C-673\u002F17 Planet49)\n- Scrolling or continued browsing of a website does not meet this standard (EDPB Guidelines 05\u002F2020, paragraph 86)\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. uses unticked checkboxes for each consent purpose. The \"Create Account\" button is active regardless of consent choices. No default-on toggles are used. The UI state is logged to demonstrate that the user actively engaged each toggle.\n\n### 5. Clear Affirmative Action (Article 4(11), Recital 32)\n\nAcceptable forms of affirmative action include:\n\n- Ticking an unticked checkbox\n- Choosing technical settings on an information society service\n- Typing a consent statement\n- Signing a written declaration (including electronic signatures under eIDAS Regulation (EU) No 910\u002F2014)\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. records the specific UI interaction (checkbox tick, toggle switch activation) along with a timestamp, the user's session ID, the IP address, the version of the consent text displayed, and the user agent string.\n\n## Consent Form Audit Checklist\n\n| # | Audit Item | GDPR Reference | Pass\u002FFail Criteria |\n|---|-----------|----------------|-------------------|\n| 1 | Consent is separated from terms of service | Art. 7(2) | Consent request is clearly distinguishable from other matters |\n| 2 | No pre-ticked boxes or default-on toggles | Art. 4(11), Recital 32, CJEU C-673\u002F17 | All consent mechanisms start in the \"off\" state |\n| 3 | Granular consent per purpose | Recital 32, EDPB Guidelines 05\u002F2020 | Separate opt-in for each distinct processing purpose |\n| 4 | Controller identity stated | Art. 7(2), Art. 13(1)(a) | Full legal name and contact details of data controller visible |\n| 5 | Purpose clearly described | Art. 13(1)(c) | Each purpose described in plain language without legal jargon |\n| 6 | Data types specified | Art. 13(1)(d) | Categories of personal data listed for each purpose |\n| 7 | Third-party recipients named | Art. 13(1)(e) | Specific third parties (not categories) identified by name |\n| 8 | Withdrawal mechanism explained | Art. 7(3) | Clear statement that consent can be withdrawn at any time with instructions |\n| 9 | No detriment for refusal | Art. 7(4), Recital 42 | Service access not conditional on optional consent |\n| 10 | Withdrawal as easy as giving | Art. 7(3) | Withdrawal requires equal or fewer steps than initial consent |\n| 11 | Age verification present | Art. 8 | Age gate or verification for services directed at children |\n| 12 | Language is plain and clear | Art. 7(2), Recital 42 | Flesch-Kincaid grade level 8 or below, no legal jargon |\n| 13 | Consent records stored | Art. 7(1) | Timestamp, version, purpose, mechanism, identity recorded |\n| 14 | Re-consent mechanism for purpose changes | Art. 13(3) | Process exists to obtain fresh consent when purposes change |\n| 15 | No cookie walls blocking access | EDPB Guidelines 05\u002F2020 para 39 | Content accessible regardless of cookie consent choices |\n\n## Implementation Workflow\n\n1. **Map Processing Activities** — Identify every processing activity that relies on consent as its lawful basis under Article 6(1)(a). Document the purpose, data categories, recipients, and retention period for each.\n\n2. **Design Consent Mechanism** — Create granular, unticked consent controls. Ensure the UI clearly separates each purpose. Follow EDPB Guidelines 05\u002F2020 on consent.\n\n3. **Draft Consent Language** — Write concise, plain-language descriptions for each purpose. Include all Article 13 information in a layered format. Test readability at Flesch-Kincaid grade level 8 or below.\n\n4. **Implement Record-Keeping** — Build a consent receipt system that captures: timestamp (ISO 8601), consent version hash, purpose identifier, mechanism type (checkbox\u002Ftoggle\u002Fsignature), data subject identifier, and the exact text presented.\n\n5. **Build Withdrawal Mechanism** — Implement one-click withdrawal accessible from the user's account dashboard. Ensure withdrawal triggers downstream processing cessation within 24 hours.\n\n6. **Run Audit** — Use the checklist above to audit the consent implementation. Document findings and remediation actions.\n\n7. **Schedule Re-Audit** — Set a recurring audit cadence (quarterly recommended) and after any UI changes that affect consent flows.\n\n## Key Regulatory References\n\n- GDPR Article 4(11) — Definition of consent\n- GDPR Article 6(1)(a) — Consent as lawful basis\n- GDPR Article 7 — Conditions for consent\n- GDPR Article 8 — Conditions applicable to child's consent\n- GDPR Recitals 32, 33, 42, 43 — Guidance on consent requirements\n- CJEU Case C-673\u002F17 (Planet49 GmbH) — Pre-ticked boxes ruling\n- EDPB Guidelines 05\u002F2020 on consent under Regulation 2016\u002F679\n- eIDAS Regulation (EU) No 910\u002F2014 — Electronic signatures for consent\n","# Implementing GDPR-Valid Consent\n\n## Overview\n\nValid consent under the GDPR is defined in Article 4(11) as \"any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.\" Article 7 sets out the conditions for consent, and Recital 32 clarifies that silence, pre-ticked boxes, or inactivity do not constitute consent.\n\nThe Court of Justice of the European Union (CJEU) reinforced this in Case C-673\u002F17 (Planet49 GmbH, October 1, 2019), ruling that pre-ticked checkboxes do not constitute valid consent for placing cookies, and that consent must be specific to each processing purpose.\n\n## The Five Requirements of Valid Consent\n\n### 1. Freely Given (Article 7(4), Recitals 42-43)\n\nConsent is not freely given if:\n\n- There is a clear imbalance between the data subject and the controller (e.g., employer-employee relationships, public authority-citizen relationships)\n- Consent is bundled as a non-negotiable condition of a service (the \"conditionality test\" under Article 7(4))\n- The data subject suffers detriment for refusing or withdrawing consent\n- There is no genuine choice or the individual feels compelled to consent\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. separates consent for core cloud storage services from consent for analytics and marketing. Users who decline marketing consent retain full access to storage functionality. The sign-up flow explicitly states: \"Declining optional data processing will not affect your access to CloudVault storage services.\"\n\n### 2. Specific (Article 6(1)(a), Recital 32)\n\nConsent must be:\n\n- Granular: separate consent for each distinct purpose\n- Named: the controller and any third-party controllers must be specifically identified\n- Purpose-limited: clearly linked to a defined processing purpose\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. presents three separate consent requests during onboarding:\n- \"Allow CloudVault SaaS Inc. to analyze your file usage patterns to recommend storage optimization\" (Purpose: Service improvement)\n- \"Allow CloudVault SaaS Inc. to send you product update emails\" (Purpose: Direct marketing)\n- \"Allow CloudVault SaaS Inc. to share anonymized usage statistics with Datalytics Partners Ltd. for industry benchmarking\" (Purpose: Third-party analytics)\n\n### 3. Informed (Article 13, Recitals 42, 60)\n\nBefore consenting, the data subject must be told at minimum:\n\n- The identity of the controller (CloudVault SaaS Inc., registered at 42 Innovation Drive, Dublin, D02 YX88, Ireland)\n- The purpose of each processing operation for which consent is sought\n- The type of data collected\n- The right to withdraw consent at any time\n- Information about automated decision-making, including profiling (Article 22(2)(c))\n- Risks of data transfers to third countries without an adequacy decision or appropriate safeguards (relevant if Article 49(1)(a) explicit consent applies)\n\n**CloudVault SaaS Inc. Implementation:**\nEach consent request includes a layered notice: a short-form summary visible immediately and a \"Learn More\" expandable section with full Article 13 information. The language is plain English at a Flesch-Kincaid grade level of 8 or below.\n\n### 4. Unambiguous Indication\n\nThe data subject's intention must be clear. According to Recital 32:\n\n- Consent requires a clear affirmative act\n- Silence, pre-ticked boxes, or inactivity do not constitute consent (confirmed in CJEU C-673\u002F17 Planet49)\n- Scrolling or continued browsing of a website does not meet this standard (EDPB Guidelines 05\u002F2020, paragraph 86)\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. uses unticked checkboxes for each consent purpose. The \"Create Account\" button is active regardless of consent choices. No default-on toggles are used. The UI state is logged to demonstrate that the user actively engaged each toggle.\n\n### 5. Clear Affirmative Action (Article 4(11), Recital 32)\n\nAcceptable forms of affirmative action include:\n\n- Ticking an unticked checkbox\n- Choosing technical settings on an information society service\n- Typing a consent statement\n- Signing a written declaration (including electronic signatures under eIDAS Regulation (EU) No 910\u002F2014)\n\n**CloudVault SaaS Inc. Implementation:**\nCloudVault SaaS Inc. records the specific UI interaction (checkbox tick, toggle switch activation) along with a timestamp, the user's session ID, the IP address, the version of the consent text displayed, and the user agent string.\n\n## Consent Form Audit Checklist\n\n| # | Audit Item | GDPR Reference | Pass\u002FFail Criteria |\n|---|-----------|----------------|-------------------|\n| 1 | Consent is separated from terms of service | Art. 7(2) | Consent request is clearly distinguishable from other matters |\n| 2 | No pre-ticked boxes or default-on toggles | Art. 4(11), Recital 32, CJEU C-673\u002F17 | All consent mechanisms start in the \"off\" state |\n| 3 | Granular consent per purpose | Recital 32, EDPB Guidelines 05\u002F2020 | Separate opt-in for each distinct processing purpose |\n| 4 | Controller identity stated | Art. 7(2), Art. 13(1)(a) | Full legal name and contact details of data controller visible |\n| 5 | Purpose clearly described | Art. 13(1)(c) | Each purpose described in plain language without legal jargon |\n| 6 | Data types specified | Art. 13(1)(d) | Categories of personal data listed for each purpose |\n| 7 | Third-party recipients named | Art. 13(1)(e) | Specific third parties (not categories) identified by name |\n| 8 | Withdrawal mechanism explained | Art. 7(3) | Clear statement that consent can be withdrawn at any time with instructions |\n| 9 | No detriment for refusal | Art. 7(4), Recital 42 | Service access not conditional on optional consent |\n| 10 | Withdrawal as easy as giving | Art. 7(3) | Withdrawal requires equal or fewer steps than initial consent |\n| 11 | Age verification present | Art. 8 | Age gate or verification for services directed at children |\n| 12 | Language is plain and clear | Art. 7(2), Recital 42 | Flesch-Kincaid grade level 8 or below, no legal jargon |\n| 13 | Consent records stored | Art. 7(1) | Timestamp, version, purpose, mechanism, identity recorded |\n| 14 | Re-consent mechanism for purpose changes | Art. 13(3) | Process exists to obtain fresh consent when purposes change |\n| 15 | No cookie walls blocking access | EDPB Guidelines 05\u002F2020 para 39 | Content accessible regardless of cookie consent choices |\n\n## Implementation Workflow\n\n1. **Map Processing Activities** — Identify every processing activity that relies on consent as its lawful basis under Article 6(1)(a). Document the purpose, data categories, recipients, and retention period for each.\n\n2. **Design Consent Mechanism** — Create granular, unticked consent controls. Ensure the UI clearly separates each purpose. Follow EDPB Guidelines 05\u002F2020 on consent.\n\n3. **Draft Consent Language** — Write concise, plain-language descriptions for each purpose. Include all Article 13 information in a layered format. Test readability at Flesch-Kincaid grade level 8 or below.\n\n4. **Implement Record-Keeping** — Build a consent receipt system that captures: timestamp (ISO 8601), consent version hash, purpose identifier, mechanism type (checkbox\u002Ftoggle\u002Fsignature), data subject identifier, and the exact text presented.\n\n5. **Build Withdrawal Mechanism** — Implement one-click withdrawal accessible from the user's account dashboard. Ensure withdrawal triggers downstream processing cessation within 24 hours.\n\n6. **Run Audit** — Use the checklist above to audit the consent implementation. Document findings and remediation actions.\n\n7. **Schedule Re-Audit** — Set a recurring audit cadence (quarterly recommended) and after any UI changes that affect consent flows.\n\n## Key Regulatory References\n\n- GDPR Article 4(11) — Definition of consent\n- GDPR Article 6(1)(a) — Consent as lawful basis\n- GDPR Article 7 — Conditions for consent\n- GDPR Article 8 — Conditions applicable to child's consent\n- GDPR Recitals 32, 33, 42, 43 — Guidance on consent requirements\n- CJEU Case C-673\u002F17 (Planet49 GmbH) — Pre-ticked boxes ruling\n- EDPB Guidelines 05\u002F2020 on consent under Regulation 2016\u002F679\n- eIDAS Regulation (EU) No 910\u002F2014 — Electronic signatures for consent\n",{"name":5,"license":15,"metadata":57,"description":7},{"metadata":58},{"tags":59,"author":60,"domain":49,"version":61,"subdomain":62},"gdpr-consent, article-7, valid-consent, affirmative-action, consent-audit","mukul975","1.0","consent-management","main","2a76bf42ce5c860adf8d0f3fcf3f6804109ac65b","skills\u002Fgdpr-valid-consent",0,"https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fwiki","https:\u002F\u002Fgithub.com\u002Fonfire7777","trying to create something actually useful","2026-09-11 13:25:26",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add onfire7777\u002Funiversal-ai-skills-library --skill gdpr-valid-consent",{"tool":78,"command":79},"bunx","bunx skills add onfire7777\u002Funiversal-ai-skills-library --skill gdpr-valid-consent",{"tool":81,"command":82},"pnpm","pnpm dlx skills add onfire7777\u002Funiversal-ai-skills-library --skill gdpr-valid-consent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002FSKILL.md",true,[86,92,98,102],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",4394,"https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fstandards.md","REFERENCE","参考文档",4211,"https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002Freferences\u002Fstandards.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fworkflows.md",4555,"https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002Freferences\u002Fworkflows.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py","SCRIPT","脚本",9606,"https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fgdpr-valid-consent\u002Fscripts\u002Fprocess.py",[109,135,144,154,175,190],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":123,"publishedAt":52},"01M6J7MPK8ZE9VQJR4KK6ZMZJQ","zyte-api-automation","Automate Zyte API tasks via Rube MCP (Composio). Always search tools first for current schemas.","MIT","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzyte-api-automation\u002FSKILL.md",[116,119,120],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":121,"categoryName":122,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[124,125,126,36,127,128,129,130,131,132,133,134],"automation","api","zyte api automation","MCP","via","composio","automate","first","Tools","search","tasks",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":52},"01M6J7MK45K2ZZ0EWTP1N6SZ7F","zylvie-automation","Automate Zylvie tasks via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzylvie-automation\u002FSKILL.md",[141],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[124,143,127,134,36,128,129,130,131,132,133],"zylvie automation",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":52},"01M6J7MGDCVZ3YCXGEAPR5V3MS","zoominfo-automation","Automate Zoominfo tasks via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzoominfo-automation\u002FSKILL.md",[150],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[152,153,124,130,129,132,128,134,36,133,127,131],"zoominfo","zoominfo automation",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":52},"01M6J7MDK48N09B7C6H9TCPY9A","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[160],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[162,163,164,165,166,167,168,169,170,171,172,173,174],"zoom out","zoom","perspective","code","re","you","with","understand","it","use","context","how","true",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":52},"01M6J7MAD47Q9A55AK3EXS914H","zoho-mail-automation","Automate Zoho Mail tasks via Rube MCP (Composio): email sending, folders, labels, and mailbox management. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-mail-automation\u002FSKILL.md",[181],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[183,184,185,186,124,187,133,134,127,132,188,36,128,189,129,48,130,131],"mail","zoho mail automation","zoho","zoho mail","email","labels","mailbox",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":52},"01M6J7M76HTWPP8TRWWCDS42NB","zoho-invoice-automation","Automate Zoho Invoice tasks via Rube MCP (Composio): invoices, estimates, expenses, clients, and payment tracking. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fonfire7777\u002Funiversal-ai-skills-library\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-invoice-automation\u002FSKILL.md",[196,197],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":198,"categoryName":199,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000040","财务",[201,124,185,202,127,128,36,203,204,205,129,206,207,130,131,132,133,134],"invoice","zoho invoice automation","invoices","expenses","clients","payment","tracking"]