[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B7ANN8BAJVXTG3967NEW5A":3,"skill-same:01M7B7ANN8BAJVXTG3967NEW5A":109},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M7B7ANN8BAJVXTG3967NEW5A","implementing-gdpr-data-protection-controls",null,"Implements GDPR (EU 2016\u002F679) technical and organizational measures — privacy by design\u002Fdefault, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access\u002Ferasure requests, or assessing cross-border data transfers.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-gdpr-data-protection-controls\ndescription: Implements GDPR (EU 2016\u002F679) technical and organizational measures — privacy by design\u002Fdefault, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access\u002Ferasure requests, or assessing cross-border data transfers.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- compliance\n- governance\n- gdpr\n- privacy\n- data-protection\n- eu-regulation\nnist_csf:\n- GV.OC-02\n- GV.PO-01\n- PR.DS-01\n- PR.AA-01\n- ID.AM-02\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\n- MEASURE-2.8\n- MEASURE-2.9\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nmitre_attack:\n- T1078\n- T1530\n- T1685.002\n---\n# Implementing GDPR Data Protection Controls\n\n## Overview\nThe General Data Protection Regulation (EU) 2016\u002F679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill covers implementing the technical and organizational measures required by GDPR, including data protection by design and by default, Data Protection Impact Assessments (DPIAs), data subject rights management, breach notification procedures, and cross-border data transfer mechanisms.\n\n\n## When to Use\n\n- When deploying or configuring implementing gdpr data protection controls capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Understanding of EU data protection law and its territorial scope\n- Knowledge of personal data processing activities within the organization\n- Familiarity with data architecture, databases, and application systems\n- Understanding of data flows including cross-border transfers\n\n## Core Concepts\n\n### Key GDPR Articles for Technical Controls\n\n| Article | Requirement |\n|---------|-------------|\n| Art. 5 | Principles: lawfulness, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability |\n| Art. 6 | Lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interest) |\n| Art. 25 | Data protection by design and by default |\n| Art. 28 | Processor obligations and contractual requirements |\n| Art. 30 | Records of processing activities (ROPA) |\n| Art. 32 | Security of processing (technical and organizational measures) |\n| Art. 33 | Breach notification to supervisory authority (72 hours) |\n| Art. 34 | Communication of breach to data subjects |\n| Art. 35 | Data Protection Impact Assessment (DPIA) |\n| Art. 37-39 | Data Protection Officer (DPO) appointment and role |\n| Art. 44-49 | Cross-border data transfers (adequacy, SCCs, BCRs) |\n\n### Article 32 Security Measures\nThe regulation requires organizations to implement measures appropriate to the risk:\n- **Pseudonymization** and encryption of personal data\n- **Confidentiality, integrity, availability, and resilience** of processing systems\n- **Ability to restore** availability and access to personal data in a timely manner\n- **Regular testing** and evaluation of technical and organizational measures\n\n### Data Subject Rights (Articles 12-22)\n| Right | Article | Description |\n|-------|---------|-------------|\n| Right to be informed | 13-14 | Transparent information about processing |\n| Right of access | 15 | Obtain copy of personal data |\n| Right to rectification | 16 | Correct inaccurate data |\n| Right to erasure | 17 | \"Right to be forgotten\" |\n| Right to restrict processing | 18 | Limit processing of data |\n| Right to data portability | 20 | Receive data in machine-readable format |\n| Right to object | 21 | Object to processing (especially direct marketing) |\n| Automated decision-making | 22 | Not be subject to solely automated decisions |\n\n## Workflow\n\n### Phase 1: Data Mapping and Assessment (Weeks 1-6)\n1. Create comprehensive data inventory:\n   - What personal data is collected\n   - From whom (data subjects)\n   - Why (purposes and lawful bases)\n   - Where it's stored (systems, locations, countries)\n   - Who has access (internal and external)\n   - How long it's retained\n   - What security measures protect it\n2. Document Records of Processing Activities (ROPA) per Article 30\n3. Identify lawful basis for each processing activity\n4. Map cross-border data transfers and transfer mechanisms\n5. Identify processing activities requiring DPIA\n\n### Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)\n1. Assess current state against GDPR requirements\n2. Perform DPIAs for high-risk processing activities\n3. Identify security gaps in Article 32 compliance\n4. Evaluate data retention compliance\n5. Assess data subject rights request handling capabilities\n\n### Phase 3: Technical Controls Implementation (Weeks 11-24)\n1. **Encryption**:\n   - Data at rest: AES-256 for databases, file systems, backups\n   - Data in transit: TLS 1.2+ for all personal data transfers\n   - Key management: secure key storage and rotation procedures\n2. **Pseudonymization**:\n   - Implement tokenization for sensitive identifiers\n   - Separate pseudonymization keys from data stores\n3. **Access Controls**:\n   - Role-based access control (RBAC) for personal data\n   - Principle of least privilege\n   - MFA for systems processing personal data\n   - Regular access reviews\n4. **Data Minimization**:\n   - Implement data collection limits at application layer\n   - Default privacy settings (data protection by default)\n   - Automated data retention enforcement\n5. **Erasure and Portability**:\n   - Build data deletion workflows across all systems\n   - Implement data export in machine-readable formats (JSON, CSV)\n   - Cascade deletion to backups and archives\n6. **Consent Management**:\n   - Implement granular consent collection mechanisms\n   - Consent withdrawal functionality\n   - Consent audit trail and versioning\n7. **Breach Detection**:\n   - SIEM for personal data access monitoring\n   - Data loss prevention (DLP) controls\n   - Anomalous access detection\n\n### Phase 4: Organizational Controls (Weeks 11-24)\n1. Appoint Data Protection Officer (DPO) if required\n2. Develop data protection policies and procedures\n3. Create breach notification procedures (72-hour timeline)\n4. Establish data subject request (DSR) handling procedures\n5. Implement vendor management with Data Processing Agreements (DPAs)\n6. Deploy privacy awareness training for all staff\n7. Create data protection by design guidance for development teams\n\n### Phase 5: Documentation and Compliance Evidence (Weeks 25-30)\n1. Finalize ROPA documentation\n2. Document all DPIAs and outcomes\n3. Create data protection policies\n4. Document technical and organizational measures\n5. Establish privacy notice and consent records\n6. Create international transfer documentation (SCCs, TIAs)\n\n### Phase 6: Ongoing Compliance (Continuous)\n1. Regular DPIA reviews for new processing activities\n2. Annual data mapping refresh\n3. Periodic security measure testing (Art. 32 requirement)\n4. Data subject request tracking and SLA monitoring\n5. Breach response readiness testing\n6. Training refresh and awareness campaigns\n\n## Key Artifacts\n- Records of Processing Activities (ROPA)\n- Data Protection Impact Assessments (DPIAs)\n- Data Processing Agreements (DPAs)\n- Privacy Notices and Consent Records\n- Breach Response Procedures and Register\n- Data Subject Request Handling Procedures\n- International Data Transfer Mechanisms (SCCs, BCRs)\n- Technical and Organizational Measures Documentation\n\n## Common Pitfalls\n- Treating GDPR as only a legal\u002Fcompliance exercise without technical implementation\n- Incomplete data mapping missing shadow IT or legacy systems\n- Failing to maintain consent audit trails\n- Not testing 72-hour breach notification capability\n- Ignoring cross-border transfer requirements for cloud services\n- Over-reliance on consent as lawful basis when legitimate interest applies\n\n## References\n- GDPR Official Text: https:\u002F\u002Fgdpr-info.eu\u002F\n- European Data Protection Board (EDPB) Guidelines\n- ICO (UK) GDPR Guidance: https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fguide-to-data-protection\u002Fguide-to-the-general-data-protection-regulation-gdpr\u002F\n- CNIL (France) GDPR Compliance Toolkit\n- Article 29 Working Party Guidelines on DPIAs\n","# Implementing GDPR Data Protection Controls\n\n## Overview\nThe General Data Protection Regulation (EU) 2016\u002F679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill covers implementing the technical and organizational measures required by GDPR, including data protection by design and by default, Data Protection Impact Assessments (DPIAs), data subject rights management, breach notification procedures, and cross-border data transfer mechanisms.\n\n\n## When to Use\n\n- When deploying or configuring implementing gdpr data protection controls capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Understanding of EU data protection law and its territorial scope\n- Knowledge of personal data processing activities within the organization\n- Familiarity with data architecture, databases, and application systems\n- Understanding of data flows including cross-border transfers\n\n## Core Concepts\n\n### Key GDPR Articles for Technical Controls\n\n| Article | Requirement |\n|---------|-------------|\n| Art. 5 | Principles: lawfulness, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability |\n| Art. 6 | Lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interest) |\n| Art. 25 | Data protection by design and by default |\n| Art. 28 | Processor obligations and contractual requirements |\n| Art. 30 | Records of processing activities (ROPA) |\n| Art. 32 | Security of processing (technical and organizational measures) |\n| Art. 33 | Breach notification to supervisory authority (72 hours) |\n| Art. 34 | Communication of breach to data subjects |\n| Art. 35 | Data Protection Impact Assessment (DPIA) |\n| Art. 37-39 | Data Protection Officer (DPO) appointment and role |\n| Art. 44-49 | Cross-border data transfers (adequacy, SCCs, BCRs) |\n\n### Article 32 Security Measures\nThe regulation requires organizations to implement measures appropriate to the risk:\n- **Pseudonymization** and encryption of personal data\n- **Confidentiality, integrity, availability, and resilience** of processing systems\n- **Ability to restore** availability and access to personal data in a timely manner\n- **Regular testing** and evaluation of technical and organizational measures\n\n### Data Subject Rights (Articles 12-22)\n| Right | Article | Description |\n|-------|---------|-------------|\n| Right to be informed | 13-14 | Transparent information about processing |\n| Right of access | 15 | Obtain copy of personal data |\n| Right to rectification | 16 | Correct inaccurate data |\n| Right to erasure | 17 | \"Right to be forgotten\" |\n| Right to restrict processing | 18 | Limit processing of data |\n| Right to data portability | 20 | Receive data in machine-readable format |\n| Right to object | 21 | Object to processing (especially direct marketing) |\n| Automated decision-making | 22 | Not be subject to solely automated decisions |\n\n## Workflow\n\n### Phase 1: Data Mapping and Assessment (Weeks 1-6)\n1. Create comprehensive data inventory:\n   - What personal data is collected\n   - From whom (data subjects)\n   - Why (purposes and lawful bases)\n   - Where it's stored (systems, locations, countries)\n   - Who has access (internal and external)\n   - How long it's retained\n   - What security measures protect it\n2. Document Records of Processing Activities (ROPA) per Article 30\n3. Identify lawful basis for each processing activity\n4. Map cross-border data transfers and transfer mechanisms\n5. Identify processing activities requiring DPIA\n\n### Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)\n1. Assess current state against GDPR requirements\n2. Perform DPIAs for high-risk processing activities\n3. Identify security gaps in Article 32 compliance\n4. Evaluate data retention compliance\n5. Assess data subject rights request handling capabilities\n\n### Phase 3: Technical Controls Implementation (Weeks 11-24)\n1. **Encryption**:\n   - Data at rest: AES-256 for databases, file systems, backups\n   - Data in transit: TLS 1.2+ for all personal data transfers\n   - Key management: secure key storage and rotation procedures\n2. **Pseudonymization**:\n   - Implement tokenization for sensitive identifiers\n   - Separate pseudonymization keys from data stores\n3. **Access Controls**:\n   - Role-based access control (RBAC) for personal data\n   - Principle of least privilege\n   - MFA for systems processing personal data\n   - Regular access reviews\n4. **Data Minimization**:\n   - Implement data collection limits at application layer\n   - Default privacy settings (data protection by default)\n   - Automated data retention enforcement\n5. **Erasure and Portability**:\n   - Build data deletion workflows across all systems\n   - Implement data export in machine-readable formats (JSON, CSV)\n   - Cascade deletion to backups and archives\n6. **Consent Management**:\n   - Implement granular consent collection mechanisms\n   - Consent withdrawal functionality\n   - Consent audit trail and versioning\n7. **Breach Detection**:\n   - SIEM for personal data access monitoring\n   - Data loss prevention (DLP) controls\n   - Anomalous access detection\n\n### Phase 4: Organizational Controls (Weeks 11-24)\n1. Appoint Data Protection Officer (DPO) if required\n2. Develop data protection policies and procedures\n3. Create breach notification procedures (72-hour timeline)\n4. Establish data subject request (DSR) handling procedures\n5. Implement vendor management with Data Processing Agreements (DPAs)\n6. Deploy privacy awareness training for all staff\n7. Create data protection by design guidance for development teams\n\n### Phase 5: Documentation and Compliance Evidence (Weeks 25-30)\n1. Finalize ROPA documentation\n2. Document all DPIAs and outcomes\n3. Create data protection policies\n4. Document technical and organizational measures\n5. Establish privacy notice and consent records\n6. Create international transfer documentation (SCCs, TIAs)\n\n### Phase 6: Ongoing Compliance (Continuous)\n1. Regular DPIA reviews for new processing activities\n2. Annual data mapping refresh\n3. Periodic security measure testing (Art. 32 requirement)\n4. Data subject request tracking and SLA monitoring\n5. Breach response readiness testing\n6. Training refresh and awareness campaigns\n\n## Key Artifacts\n- Records of Processing Activities (ROPA)\n- Data Protection Impact Assessments (DPIAs)\n- Data Processing Agreements (DPAs)\n- Privacy Notices and Consent Records\n- Breach Response Procedures and Register\n- Data Subject Request Handling Procedures\n- International Data Transfer Mechanisms (SCCs, BCRs)\n- Technical and Organizational Measures Documentation\n\n## Common Pitfalls\n- Treating GDPR as only a legal\u002Fcompliance exercise without technical implementation\n- Incomplete data mapping missing shadow IT or legacy systems\n- Failing to maintain consent audit trails\n- Not testing 72-hour breach notification capability\n- Ignoring cross-border transfer requirements for cloud services\n- Over-reliance on consent as lawful basis when legitimate interest applies\n\n## References\n- GDPR Official Text: https:\u002F\u002Fgdpr-info.eu\u002F\n- European Data Protection Board (EDPB) Guidelines\n- ICO (UK) GDPR Guidance: https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fguide-to-data-protection\u002Fguide-to-the-general-data-protection-regulation-gdpr\u002F\n- CNIL (France) GDPR Compliance Toolkit\n- Article 29 Working Party Guidelines on DPIAs\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"nist_csf":34,"subdomain":40,"description":7,"nist_ai_rmf":41,"mitre_attack":47,"atlas_techniques":51},[25,26,27,28,29,30],"compliance","governance","gdpr","privacy","data-protection","eu-regulation","mahipal","cybersecurity","1.0",[35,36,37,38,39],"GV.OC-02","GV.PO-01","PR.DS-01","PR.AA-01","ID.AM-02","compliance-governance",[42,43,44,45,46],"MEASURE-2.7","MAP-5.1","MANAGE-2.4","MEASURE-2.8","MEASURE-2.9",[48,49,50],"T1078","T1530","T1685.002",[52,53,54],"AML.T0070","AML.T0066","AML.T0082","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-gdpr-data-protection-controls",{"tool":67,"command":68},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-gdpr-data-protection-controls",{"tool":70,"command":71},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-gdpr-data-protection-controls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002FSKILL.md",true,[75,81,85,91,95,99,105],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",6211,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fapi-reference.md","REFERENCE","参考文档",2171,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fapi-reference.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fstandards.md",5488,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fstandards.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fworkflows.md",7130,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Freferences\u002Fworkflows.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",9355,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fscripts\u002Fagent.py",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",22121,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-gdpr-data-protection-controls\u002Fscripts\u002Fprocess.py",[110,118,125,132,139,146],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]