[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEBZB2X0F9FVWE14REPBHY":3,"skill-same:01M6AEBZB2X0F9FVWE14REPBHY":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":28,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6AEBZB2X0F9FVWE14REPBHY","pia-threshold-screening",null,"Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35. Applies the EDPB WP248rev.01 nine-criteria test, national supervisory authority blacklists, and organisational risk appetite to produce a documented screening decision. Keywords: threshold screening, DPIA trigger, pre-DPIA, WP248, Article 35(1), blacklist, screening decision.","mukul975\u002FPrivacy-Data-Protection-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADNKWX1HF4Q5DKEXT5M774",338,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37],"pia threshold screening","test","assessment","produce","data protection","gdpr","privacy","data","dpia","2026-11-10 10:12:30",false,"---\nname: pia-threshold-screening\ndescription: >-\n  Conducts pre-DPIA threshold screening to determine whether a full Data\n  Protection Impact Assessment is required under GDPR Article 35. Applies\n  the EDPB WP248rev.01 nine-criteria test, national supervisory authority\n  blacklists, and organisational risk appetite to produce a documented\n  screening decision. Keywords: threshold screening, DPIA trigger, pre-DPIA,\n  WP248, Article 35(1), blacklist, screening decision.\nlicense: Apache-2.0\nmetadata:\n  author: mukul975\n  version: \"1.0\"\n  domain: privacy\n  subdomain: privacy-impact-assessment\n  tags: \"threshold-screening, dpia-trigger, pre-dpia, wp248, article-35, blacklist\"\n---\n\n# PIA Threshold Screening\n\n## Overview\n\nArticle 35(1) GDPR requires a DPIA when processing is \"likely to result in a high risk to the rights and freedoms of natural persons.\" This skill provides a structured screening methodology to make that determination before committing to a full DPIA.\n\n## Screening Criteria\n\n### EDPB Nine-Criteria Test (WP248rev.01)\n\nProcessing that meets **two or more** of the following criteria generally requires a DPIA:\n\n| # | Criterion | GDPR Reference |\n|---|-----------|----------------|\n| 1 | Evaluation or scoring | Art. 35(3)(a) |\n| 2 | Automated decision-making with legal\u002Fsimilar effect | Art. 35(3)(a) |\n| 3 | Systematic monitoring | Art. 35(3)(c) |\n| 4 | Sensitive data or data of highly personal nature | Art. 9, Art. 10 |\n| 5 | Data processed on a large scale | Recital 91 |\n| 6 | Matching or combining datasets | WP248 |\n| 7 | Data concerning vulnerable data subjects | WP248 |\n| 8 | Innovative use or applying new technological solutions | WP248 |\n| 9 | Processing that prevents data subjects from exercising a right | Art. 22, Art. 35(3)(b) |\n\n### Mandatory DPIA Triggers (Art. 35(3))\n\nA DPIA is always required for:\n\n- **(a)** Systematic and extensive evaluation of personal aspects based on automated processing, including profiling, producing legal effects or similarly significant effects\n- **(b)** Large-scale processing of special categories of data (Art. 9(1)) or criminal conviction data (Art. 10)\n- **(c)** Systematic monitoring of a publicly accessible area on a large scale\n\n### National Supervisory Authority Blacklists (Art. 35(4))\n\nEach EU\u002FEEA supervisory authority publishes a list of processing operations requiring a DPIA. The screening must check the relevant national blacklist based on the controller establishment.\n\n## Screening Process\n\n1. **Identify processing activity** -- Describe the proposed or changed processing\n2. **Check mandatory triggers** -- Evaluate against Art. 35(3)(a)-(c)\n3. **Check national blacklist** -- Consult the relevant SA published list\n4. **Apply nine-criteria test** -- Score each WP248 criterion as met\u002Fnot met\n5. **Document rationale** -- Record the screening decision with justification\n6. **Escalate or close** -- Route to full DPIA or document exemption\n\n## Decision Logic\n\n```\nIF any Art. 35(3) mandatory trigger is met → DPIA REQUIRED\nELSE IF processing appears on national SA blacklist → DPIA REQUIRED\nELSE IF 2+ WP248 criteria are met → DPIA REQUIRED\nELSE IF 1 WP248 criterion is met → DPIA RECOMMENDED (risk-based decision)\nELSE → DPIA NOT REQUIRED (document exemption)\n```\n\n## Integration Points\n\n- **RoPA linkage**: Screening results attach to the corresponding RoPA entry\n- **Change management**: New processing or material changes trigger re-screening\n- **DPIA register**: Positive screening decisions feed the DPIA pipeline\n","# PIA Threshold Screening\n\n## Overview\n\nArticle 35(1) GDPR requires a DPIA when processing is \"likely to result in a high risk to the rights and freedoms of natural persons.\" This skill provides a structured screening methodology to make that determination before committing to a full DPIA.\n\n## Screening Criteria\n\n### EDPB Nine-Criteria Test (WP248rev.01)\n\nProcessing that meets **two or more** of the following criteria generally requires a DPIA:\n\n| # | Criterion | GDPR Reference |\n|---|-----------|----------------|\n| 1 | Evaluation or scoring | Art. 35(3)(a) |\n| 2 | Automated decision-making with legal\u002Fsimilar effect | Art. 35(3)(a) |\n| 3 | Systematic monitoring | Art. 35(3)(c) |\n| 4 | Sensitive data or data of highly personal nature | Art. 9, Art. 10 |\n| 5 | Data processed on a large scale | Recital 91 |\n| 6 | Matching or combining datasets | WP248 |\n| 7 | Data concerning vulnerable data subjects | WP248 |\n| 8 | Innovative use or applying new technological solutions | WP248 |\n| 9 | Processing that prevents data subjects from exercising a right | Art. 22, Art. 35(3)(b) |\n\n### Mandatory DPIA Triggers (Art. 35(3))\n\nA DPIA is always required for:\n\n- **(a)** Systematic and extensive evaluation of personal aspects based on automated processing, including profiling, producing legal effects or similarly significant effects\n- **(b)** Large-scale processing of special categories of data (Art. 9(1)) or criminal conviction data (Art. 10)\n- **(c)** Systematic monitoring of a publicly accessible area on a large scale\n\n### National Supervisory Authority Blacklists (Art. 35(4))\n\nEach EU\u002FEEA supervisory authority publishes a list of processing operations requiring a DPIA. The screening must check the relevant national blacklist based on the controller establishment.\n\n## Screening Process\n\n1. **Identify processing activity** -- Describe the proposed or changed processing\n2. **Check mandatory triggers** -- Evaluate against Art. 35(3)(a)-(c)\n3. **Check national blacklist** -- Consult the relevant SA published list\n4. **Apply nine-criteria test** -- Score each WP248 criterion as met\u002Fnot met\n5. **Document rationale** -- Record the screening decision with justification\n6. **Escalate or close** -- Route to full DPIA or document exemption\n\n## Decision Logic\n\n```\nIF any Art. 35(3) mandatory trigger is met → DPIA REQUIRED\nELSE IF processing appears on national SA blacklist → DPIA REQUIRED\nELSE IF 2+ WP248 criteria are met → DPIA REQUIRED\nELSE IF 1 WP248 criterion is met → DPIA RECOMMENDED (risk-based decision)\nELSE → DPIA NOT REQUIRED (document exemption)\n```\n\n## Integration Points\n\n- **RoPA linkage**: Screening results attach to the corresponding RoPA entry\n- **Change management**: New processing or material changes trigger re-screening\n- **DPIA register**: Positive screening decisions feed the DPIA pipeline\n",{"name":5,"license":15,"metadata":43,"description":7},{"tags":44,"author":9,"domain":35,"version":45,"subdomain":46},"threshold-screening, dpia-trigger, pre-dpia, wp248, article-35, blacklist","1.0","privacy-impact-assessment","main","9b2ef9eae161c00a17241d42a388571321b33e9f","plugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening",68,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-03-17 04:06:52",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill pia-threshold-screening",{"tool":62,"command":63},"bunx","bunx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill pia-threshold-screening",{"tool":65,"command":66},"pnpm","pnpm dlx skills add mukul975\u002FPrivacy-Data-Protection-Skills --skill pia-threshold-screening","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002FSKILL.md",true,[70,76,82,86,90,94,98,102],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002FEvanston09\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fimprove\u002Fagents\u002Fopenai.yaml",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Ftemplate.md","ASSET","资产文件",6530,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002Fassets\u002Ftemplate.md",{"path":83,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Faudit-playbook.md",13343,"https:\u002F\u002Fgithub.com\u002FEvanston09\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fimprove\u002Freferences\u002Faudit-playbook.md",{"path":87,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fclosing-the-loop.md",7317,"https:\u002F\u002Fgithub.com\u002FEvanston09\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fimprove\u002Freferences\u002Fclosing-the-loop.md",{"path":91,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fplan-template.md",8493,"https:\u002F\u002Fgithub.com\u002FEvanston09\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fimprove\u002Freferences\u002Fplan-template.md",{"path":95,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fstandards.md",3634,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002Freferences\u002Fstandards.md",{"path":99,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fworkflows.md",3201,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002Freferences\u002Fworkflows.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py","SCRIPT","脚本",12636,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprivacy-impact-assessment-skills\u002Fskills\u002Fpia-threshold-screening\u002Fscripts\u002Fprocess.py",[109,133,148,161,177,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":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":124,"publishedAt":38},"01M6AG6K8R3XW10ENWH2FH18RH","workplace-email-privacy","Implements email and internet monitoring compliance in the workplace per Barbulescu v Romania (ECHR Grand Chamber), EDPB guidance, and national labour law. Covers acceptable use policies, legitimate expectation of privacy, proportionality testing, and content vs metadata monitoring. Keywords: email monitoring, Barbulescu, workplace privacy, internet monitoring, acceptable use policy, ECHR, proportionality.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fworkplace-email-privacy\u002FSKILL.md",[115,118,121],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":122,"categoryName":123,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[125,126,35,127,128,36,129,130,131,132],"email","workplace email privacy","compliance","content","policy","testing","monitoring","metadata",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":143,"publishedAt":38},"01M6AG6FRCBJY7D061BJZMNV49","whistleblower-data","Implements data protection compliance for whistleblowing systems under EU Directive 2019\u002F1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019\u002F1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fwhistleblower-data\u002FSKILL.md",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":122,"categoryName":123,"taxonomyType":26,"taxonomyTypeDesc":27},[36,144,145,146,127,33,34,35,147],"whistleblower data","identity","reporting","prevention",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":38},"01M6AG6CJP0PW3X65HC7VP9SR9","vendor-termination-data","Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Covers data extraction formats, deletion certification requirements, transition planning, residual data handling, and post-termination verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-termination-data\u002FSKILL.md",[154],{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},[36,156,157,158,159,34,35,160],"vendor termination data","planning","verification","extraction","certification",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":38},"01M6AG69E277DXZB2NF6KV17ZA","vendor-risk-scoring","Vendor privacy risk tiering methodology for processor management. Covers scoring factors including data volume, sensitivity, transfer locations, certifications, breach history, and control maturity with weighted risk calculation and tier assignment.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-risk-scoring\u002FSKILL.md",[167],{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},[169,170,171,172,173,31,174,175,35,36,176],"vendor risk scoring","risk","risk scoring","methodology","risk-scoring","transfer","certifications","processor",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":38},"01M6AG6655ABFKT2BBWHCP4PAT","vendor-privacy-due-diligence","Pre-contract vendor privacy due diligence per GDPR Article 28(1). Covers risk questionnaires, technical controls assessment, certification review, data flow analysis, and documented sufficiency decisions for processor engagement.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-due-diligence\u002FSKILL.md",[183],{"categoryNo":122,"categoryName":123,"taxonomyType":26,"taxonomyTypeDesc":27},[35,185,34,186,31,187,188,36,176,170,160,189],"vendor privacy due diligence","review","onboarding","flow","analysis",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":199,"publishedAt":38},"01M6AG62C3VD8SYNGH4N7RHZTE","vendor-privacy-audit","On-site and remote vendor audit procedures per GDPR Article 28(3)(h). Covers audit planning, evidence collection methodologies, finding classification, remediation tracking, and audit report generation for processor compliance verification.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FPrivacy-Data-Protection-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fprivacy\u002Fvendor-privacy-audit\u002FSKILL.md",[196,197,198],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":122,"categoryName":123,"taxonomyType":26,"taxonomyTypeDesc":27},[200,201,35,202,158,203,127,34,204,176,205,206,207,157],"vendor privacy audit","audit","report","audit report","remediation","collection","remediation-tracking","classification"]