[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQSE7BWBTHEWEN7JS1D3Z7":3,"skill-same:01M7AQSE7BWBTHEWEN7JS1D3Z7":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AQSE7BWBTHEWEN7JS1D3Z7","gdpr-audit-prep",null,"\u002Fcs:gdpr-audit-prep \u003Cscope> — GDPR audit 6-question Article-cited forcing interrogation. Use before annual internal GDPR review, post-breach internal audit, DPA investigation readiness, or acquisition due diligence.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Fgdpr-audit-prep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"gdpr-audit-prep\"\ndescription: \"\u002Fcs:gdpr-audit-prep \u003Cscope> — GDPR audit 6-question Article-cited forcing interrogation. Use before annual internal GDPR review, post-breach internal audit, DPA investigation readiness, or acquisition due diligence.\"\n---\n\n# \u002Fcs:gdpr-audit-prep — GDPR DPO Forcing Questions\n\n**Command:** `\u002Fcs:gdpr-audit-prep \u003Cscope>`\n\nThe GDPR DPO auditor pressure-tests any privacy compliance work. Six Article-cited questions before any internal audit, breach response, DPA investigation, or acquisition due diligence.\n\n## When to Run\n\n- Before annual internal GDPR audit\n- Before quarterly Article 30 RoPA refresh\n- Before launching new high-risk processing (Article 35 DPIA required)\n- Post-breach (Articles 33-34)\n- Before DPA investigation response or supervisory authority engagement\n- During acquisition due diligence (target company privacy posture)\n- Quarterly during high-volume new-feature shipping\n\n## The Six DPO Questions\n\n### 1. Show me the Article 30 RoPA — with last-updated date.\n**Most-cited finding area.**\n- Must include all Article 30(1)(a)-(g) elements for controllers\n- Must include all Article 30(2)(a)-(d) elements for processors\n- Updated within reasonable time of changes (90 days expected)\n- Joint controller arrangements documented per Article 26\n\n### 2. For this processing activity, what's the lawful basis under Article 6?\n**Article 6 is exclusive — pick ONE basis per purpose.**\n- Six options: consent \u002F contract \u002F legal obligation \u002F vital interests \u002F public task \u002F legitimate interests\n- Where \"legitimate interests\": LIA documented\n- Where \"consent\": records per Article 7; withdrawal mechanism\n- Special categories (Article 9) require an Article 9(2) exception\n\n### 3. For high-risk processing, where's the DPIA per Article 35?\n**Required for high-risk; sample 3-5 activities.**\n- Article 35(7)(a)-(d) required elements:\n  - Systematic description of processing\n  - Necessity + proportionality assessment\n  - Risks to rights + freedoms\n  - Measures to address risks\n- DPO consulted per Article 35(2)\n- Article 36 prior consultation triggered for residual high risk\n- For AI systems: integrates with EU AI Act Article 27 FRIA (cross-check with cs-ai-act-compliance)\n\n### 4. Show me a DSAR from the last 30 days — and the response timing.\n**Articles 15-22 operational workflow.**\n- Response within 1 month (Article 12(3)); extension up to 2 months for complex requests\n- Identity verification process documented\n- Right of access response includes all Article 15 information\n- Right to erasure (Article 17) workflow covers backups + processors\n\n### 5. Show me Transfer Impact Assessments for the largest non-EU transfers.\n**Schrems II discipline.**\n- Adequacy decision OR SCCs (Article 46) OR derogation (Article 49)\n- TIA per EDPB Recommendations 01\u002F2020 + 02\u002F2020\n- Supplementary measures where TIA flagged risk\n- US transfers covered by EU-US Data Privacy Framework adequacy (Jul 2023) — verify list of certified entities\n\n### 6. Show me the breach log per Article 33(5) — all breaches, not just notifiable ones.\n**Article 33(5) requires logging ALL breaches.**\n- Internal breach detection mechanism documented\n- Article 33 DPA notification within 72 hours (where required)\n- Article 34 data subject notification (where high risk)\n- Root cause + corrective action via CAPA system\n- Cross-check with cs-ciso-iso27001 for A.5.24-27 incident management alignment\n\n## Workflow\n\n```bash\n# 1. Compliance posture\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fgdpr_compliance_checker.py compliance_state.json\n\n# 2. DPIA for high-risk activities\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fdpia_generator.py processing_activity.json\n\n# 3. DSAR workflow validation\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fdata_subject_rights_tracker.py dsar_log.json\n\n# 4. Cross-framework reuse with ISO 27001 + SOC 2 + ISO 42001\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# GDPR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n**Article Citations:** Every finding cites Article + paragraph; no paraphrase.\n\n## The Decision Being Made\n[RoPA-refresh | DPIA-required | DSAR-workflow | transfer-risk | breach-followup | DPA-readiness]\n\n## Article 30 RoPA Status\n- Last refresh: YYYY-MM-DD\n- Required elements present: yes\u002Fno per processing activity\n- Joint controller arrangements: documented\u002Fmissing\n\n## Article 6 Lawful Basis Discipline\n- Activities reviewed: N\n- Legitimate-interests claims without LIA: \u003Clist>\n- Article 9 special categories with documented exception: yes\u002Fno\n\n## Article 35 DPIA Quality\n- High-risk activities requiring DPIA: \u003Clist>\n- DPIAs complete per Article 35(7): pass\u002Ffail per activity\n- Article 36 prior consultation triggered: \u003Clist>\n\n## Data Subject Rights (Articles 12-22)\n- DSARs in last 90 days: N\n- Average response time: X days (target: ≤ 30)\n- Right to erasure backup-processor flow: complete\u002Fincomplete\n\n## Article 28 Processor Management\n- Processors reviewed: N\n- Contracts with all Article 28(3)(a)-(j) clauses: % complete\n- Sub-processor flow-down notification mechanism: yes\u002Fno\n\n## Schrems II Transfer Status\n- Non-EU transfers: \u003Clist>\n- Mechanism per transfer: adequacy \u002F SCCs \u002F derogation\n- TIA on file: yes\u002Fno per transfer\n- Supplementary measures where needed: \u003Clist>\n\n## Article 33-34 Breach Discipline\n- Breach log last 12 months: N\n- Article 33 notification timing: ≤ 72h ratio\n- Article 34 data subject notification (where high risk): on-time ratio\n\n## Cross-Framework Impact\n- ISO 27001 Article 32 alignment: clean \u002F gaps\n- EU AI Act Article 27 FRIA integration: applicable \u002F not\n- SOC 2 Privacy TSC alignment (if scope): clean \u002F gaps\n\n## Verdict\n🟢 DPA-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + Article-cited timeline]\n\n## Outside Counsel Required\n[Article-level ambiguities flagged: Schrems II supplementary measure adequacy, EU AI Act ↔ GDPR interaction, sectoral derogation interpretation, novel DPA enforcement]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso27001-audit-prep` — for Article 32 organizational measures\n- `\u002Fcs:ai-act-readiness` — for EU AI Act Article 27 FRIA integration\n- `\u002Fcs:soc2-audit-prep` — for SOC 2 Privacy TSC overlap\n- `\u002Fcs:gc-review` — for novel-case legal review\n\n## Related\n\n- Agent: [`cs-dpo-gdpr`](..\u002F..\u002Fagents\u002Fcs-dpo-gdpr.md)\n- Skill: [`gdpr-dsgvo-expert`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002FSKILL.md)\n- Playbook: [gdpr_audit_playbook.md](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Freferences\u002Fgdpr_audit_playbook.md)\n- Adjacent: `..\u002Fiso27001-audit-prep\u002F`, `..\u002Fai-act-readiness\u002F`, `..\u002Fsoc2-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:gdpr-audit-prep — GDPR DPO Forcing Questions\n\n**Command:** `\u002Fcs:gdpr-audit-prep \u003Cscope>`\n\nThe GDPR DPO auditor pressure-tests any privacy compliance work. Six Article-cited questions before any internal audit, breach response, DPA investigation, or acquisition due diligence.\n\n## When to Run\n\n- Before annual internal GDPR audit\n- Before quarterly Article 30 RoPA refresh\n- Before launching new high-risk processing (Article 35 DPIA required)\n- Post-breach (Articles 33-34)\n- Before DPA investigation response or supervisory authority engagement\n- During acquisition due diligence (target company privacy posture)\n- Quarterly during high-volume new-feature shipping\n\n## The Six DPO Questions\n\n### 1. Show me the Article 30 RoPA — with last-updated date.\n**Most-cited finding area.**\n- Must include all Article 30(1)(a)-(g) elements for controllers\n- Must include all Article 30(2)(a)-(d) elements for processors\n- Updated within reasonable time of changes (90 days expected)\n- Joint controller arrangements documented per Article 26\n\n### 2. For this processing activity, what's the lawful basis under Article 6?\n**Article 6 is exclusive — pick ONE basis per purpose.**\n- Six options: consent \u002F contract \u002F legal obligation \u002F vital interests \u002F public task \u002F legitimate interests\n- Where \"legitimate interests\": LIA documented\n- Where \"consent\": records per Article 7; withdrawal mechanism\n- Special categories (Article 9) require an Article 9(2) exception\n\n### 3. For high-risk processing, where's the DPIA per Article 35?\n**Required for high-risk; sample 3-5 activities.**\n- Article 35(7)(a)-(d) required elements:\n  - Systematic description of processing\n  - Necessity + proportionality assessment\n  - Risks to rights + freedoms\n  - Measures to address risks\n- DPO consulted per Article 35(2)\n- Article 36 prior consultation triggered for residual high risk\n- For AI systems: integrates with EU AI Act Article 27 FRIA (cross-check with cs-ai-act-compliance)\n\n### 4. Show me a DSAR from the last 30 days — and the response timing.\n**Articles 15-22 operational workflow.**\n- Response within 1 month (Article 12(3)); extension up to 2 months for complex requests\n- Identity verification process documented\n- Right of access response includes all Article 15 information\n- Right to erasure (Article 17) workflow covers backups + processors\n\n### 5. Show me Transfer Impact Assessments for the largest non-EU transfers.\n**Schrems II discipline.**\n- Adequacy decision OR SCCs (Article 46) OR derogation (Article 49)\n- TIA per EDPB Recommendations 01\u002F2020 + 02\u002F2020\n- Supplementary measures where TIA flagged risk\n- US transfers covered by EU-US Data Privacy Framework adequacy (Jul 2023) — verify list of certified entities\n\n### 6. Show me the breach log per Article 33(5) — all breaches, not just notifiable ones.\n**Article 33(5) requires logging ALL breaches.**\n- Internal breach detection mechanism documented\n- Article 33 DPA notification within 72 hours (where required)\n- Article 34 data subject notification (where high risk)\n- Root cause + corrective action via CAPA system\n- Cross-check with cs-ciso-iso27001 for A.5.24-27 incident management alignment\n\n## Workflow\n\n```bash\n# 1. Compliance posture\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fgdpr_compliance_checker.py compliance_state.json\n\n# 2. DPIA for high-risk activities\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fdpia_generator.py processing_activity.json\n\n# 3. DSAR workflow validation\npython ra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Fscripts\u002Fdata_subject_rights_tracker.py dsar_log.json\n\n# 4. Cross-framework reuse with ISO 27001 + SOC 2 + ISO 42001\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Fcross_framework_mapper.py program.json\n```\n\n## Output Format\n\n```markdown\n# GDPR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n**Article Citations:** Every finding cites Article + paragraph; no paraphrase.\n\n## The Decision Being Made\n[RoPA-refresh | DPIA-required | DSAR-workflow | transfer-risk | breach-followup | DPA-readiness]\n\n## Article 30 RoPA Status\n- Last refresh: YYYY-MM-DD\n- Required elements present: yes\u002Fno per processing activity\n- Joint controller arrangements: documented\u002Fmissing\n\n## Article 6 Lawful Basis Discipline\n- Activities reviewed: N\n- Legitimate-interests claims without LIA: \u003Clist>\n- Article 9 special categories with documented exception: yes\u002Fno\n\n## Article 35 DPIA Quality\n- High-risk activities requiring DPIA: \u003Clist>\n- DPIAs complete per Article 35(7): pass\u002Ffail per activity\n- Article 36 prior consultation triggered: \u003Clist>\n\n## Data Subject Rights (Articles 12-22)\n- DSARs in last 90 days: N\n- Average response time: X days (target: ≤ 30)\n- Right to erasure backup-processor flow: complete\u002Fincomplete\n\n## Article 28 Processor Management\n- Processors reviewed: N\n- Contracts with all Article 28(3)(a)-(j) clauses: % complete\n- Sub-processor flow-down notification mechanism: yes\u002Fno\n\n## Schrems II Transfer Status\n- Non-EU transfers: \u003Clist>\n- Mechanism per transfer: adequacy \u002F SCCs \u002F derogation\n- TIA on file: yes\u002Fno per transfer\n- Supplementary measures where needed: \u003Clist>\n\n## Article 33-34 Breach Discipline\n- Breach log last 12 months: N\n- Article 33 notification timing: ≤ 72h ratio\n- Article 34 data subject notification (where high risk): on-time ratio\n\n## Cross-Framework Impact\n- ISO 27001 Article 32 alignment: clean \u002F gaps\n- EU AI Act Article 27 FRIA integration: applicable \u002F not\n- SOC 2 Privacy TSC alignment (if scope): clean \u002F gaps\n\n## Verdict\n🟢 DPA-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + Article-cited timeline]\n\n## Outside Counsel Required\n[Article-level ambiguities flagged: Schrems II supplementary measure adequacy, EU AI Act ↔ GDPR interaction, sectoral derogation interpretation, novel DPA enforcement]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso27001-audit-prep` — for Article 32 organizational measures\n- `\u002Fcs:ai-act-readiness` — for EU AI Act Article 27 FRIA integration\n- `\u002Fcs:soc2-audit-prep` — for SOC 2 Privacy TSC overlap\n- `\u002Fcs:gc-review` — for novel-case legal review\n\n## Related\n\n- Agent: [`cs-dpo-gdpr`](..\u002F..\u002Fagents\u002Fcs-dpo-gdpr.md)\n- Skill: [`gdpr-dsgvo-expert`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002FSKILL.md)\n- Playbook: [gdpr_audit_playbook.md](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Fgdpr-dsgvo-expert\u002Freferences\u002Fgdpr_audit_playbook.md)\n- Adjacent: `..\u002Fiso27001-audit-prep\u002F`, `..\u002Fai-act-readiness\u002F`, `..\u002Fsoc2-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","992d25a425dee442a1f6a628d00a4fed33efe839","compliance-os\u002Fskills\u002Fgdpr-audit-prep","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill gdpr-audit-prep",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill gdpr-audit-prep",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill gdpr-audit-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Fgdpr-audit-prep\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","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.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","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\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","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\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","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\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","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\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]