[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQERYP587CCAYV75WZBRSK":3,"skill-same:01M7BQERYP587CCAYV75WZBRSK":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BQERYP587CCAYV75WZBRSK","fda-qsr-audit-prep",null,"\u002Fcs:fda-qsr-audit-prep \u003Cscope> — FDA 21 CFR 820 (QSR \u002F QMSR) audit 6-question forcing interrogation. Post-Feb 2026 substantially harmonized with ISO 13485. Use before annual internal QSR audit, pre-FDA-inspection readiness, or Form 483 response.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Ffda-qsr-audit-prep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"fda-qsr-audit-prep\"\ndescription: \"\u002Fcs:fda-qsr-audit-prep \u003Cscope> — FDA 21 CFR 820 (QSR \u002F QMSR) audit 6-question forcing interrogation. Post-Feb 2026 substantially harmonized with ISO 13485. Use before annual internal QSR audit, pre-FDA-inspection readiness, or Form 483 response.\"\n---\n\n# \u002Fcs:fda-qsr-audit-prep — FDA QSR Forcing Questions\n\n**Command:** `\u002Fcs:fda-qsr-audit-prep \u003Cscope>`\n\nThe FDA QSR auditor pressure-tests any US medical-device QSR work. Six questions before any internal audit, FDA inspection, Form 483 response, or recall decision.\n\n## When to Run\n\n- Before annual internal QSR audit\n- Before pre-FDA-inspection readiness review (any device commercially distributed in US)\n- After receiving Form 483 observations\n- After Warning Letter receipt\n- After MDR-reportable event\n- Before recall decision (voluntary vs FDA-initiated)\n- Before submitting 510(k) \u002F PMA (where QSR posture affects approval timeline)\n\n## The Six QSR Questions\n\n### 1. Show me the complaint files from the last quarter — and the corresponding MDR reports.\n**21 CFR 820.198 + 21 CFR 803 — most-cited FDA inspection area.**\n- Complaint log complete: who \u002F what \u002F when \u002F device \u002F batch\n- Investigation closure within reasonable timeline\n- MDR-reporting decision tree applied: death OR serious injury OR malfunction-that-could-cause = MDR\n- 30-day timeline for most MDR reports; 5 days for certain serious events\n- Complaint trending input to management review\n\n### 2. When was process validation (IQ\u002FOQ\u002FPQ) last revalidated per 21 CFR 820.75?\n**Cross-walks ISO 13485 Clause 7.5.6 (substantially harmonized post-Feb 2026).**\n- Initial validation at process introduction\n- Revalidation triggers: process \u002F equipment \u002F material change OR periodic schedule\n- Statistical techniques per 21 CFR 820.250 where applicable\n- Cross-check with cs-cqm-iso13485 for ISO 13485 alignment\n\n### 3. Show me the DHRs for products commercially distributed in last 2 years.\n**21 CFR 820.180 — 2-year retention from commercial distribution; check sampling for completeness.**\n- Device History Record (DHR) for each unit\u002Flot\u002Fbatch\n- Must include: dates of manufacture, quantity manufactured, quantity released, acceptance records, primary identification label, device identification, control number\n- Sample stratified by product class\n- Verify DHR closeness to DHF (design history file)\n\n### 4. Show me CAPAs from the last 6 months with effectiveness verification.\n**21 CFR 820.100 = ISO 13485 8.5.2 substantially harmonized.**\n- Root cause analysis depth (5 Why minimum)\n- Effectiveness verification = measurable evidence, not \"we updated the procedure\"\n- Containment \u002F correction \u002F corrective action distinction documented\n- Closure approval by appropriate authority\n- Aging CAPAs > 90 days flagged\n\n### 5. Show me labeling (21 CFR 801) review for the most recent product launch.\n**FDA-specific overlay not in ISO 13485.**\n- Labeling per 21 CFR 801 requirements\n- For specific device types: also 21 CFR 800 series sectoral overlays\n- UDI (Unique Device Identification) per 21 CFR 830\n- Promotional materials reviewed for accuracy + non-misleading\n\n### 6. If a Form 483 was issued in the last 3 years, show me the closure status.\n**Form 483 = FDA observation; not equivalent to ISO nonconformity.**\n- Response within 15 working days\n- Each observation has documented corrective + preventive action with timeline\n- Effectiveness verification evidence\n- For Warning Letters: separate response track + potentially FDA meeting\n\n## Workflow\n\n```bash\n# 1. QSR compliance posture\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fqsr_compliance_checker.py compliance_state.json\n\n# 2. FDA submission tracking (510(k) \u002F PMA \u002F IDE)\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fhipaa_risk_assessment.py phi_inventory.json\n\n# 4. Mock FDA inspection\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py fda_qsr_scope.json\n```\n\n## Output Format\n\n```markdown\n# FDA QSR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | inspection-readiness | 483-response | MDR-decision | recall]\n\n## Complaint + MDR Posture\n- Complaints last quarter: N\n- MDR-reportable events: M\n- MDR reports filed within timeline: % (target 100%)\n- Complaint trending review at management level: yes\u002Fno\n\n## Process Validation Status (21 CFR 820.75)\n- Validations on schedule: %\n- Stale validations: \u003Clist>\n- Statistical techniques applied: yes\u002Fno per process\n\n## DHR Completeness (21 CFR 820.180)\n- DHRs sampled: N\n- Completeness rate: %\n- 2-year retention compliant: yes\u002Fno\n- Stratified by product class: yes\u002Fno\n\n## CAPA Health (21 CFR 820.100)\n- CAPAs sampled: N\n- Root cause analysis depth: adequate\u002Finadequate\n- Effectiveness verification: complete\u002Fincomplete\n- Aging CAPAs > 90 days: N\n\n## Labeling (21 CFR 801)\n- Recent products reviewed: \u003Clist>\n- Labeling accurate + non-misleading: yes\u002Fno\n- UDI compliance per 21 CFR 830: yes\u002Fno\n\n## Form 483 \u002F Warning Letter History\n- Form 483s last 3 years: N (each: closed\u002Fin-progress)\n- Warning Letters last 5 years: N (each: closed\u002Fin-progress)\n- Pattern across observations: \u003Cthematic>\n\n## ISO 13485 Cross-Walk (post-Feb 2026 harmonization)\n- ISO 13485 audit findings: \u003Clink to cs-cqm-iso13485 output>\n- FDA-specific overlays remaining: labeling + complaint handling + MDR reporting + recall procedures\n- Cross-framework reuse: % of evidence shared\n\n## Verdict\n🟢 INSPECTION-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + FDA-cited timeline (15 days \u002F 30 days \u002F etc.)]\n\n## Outside Counsel Required\n[For Warning Letter response, recall decisions, or 510(k) \u002F PMA strategy disputes]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso13485-audit-prep` — for ISO 13485 cross-walk pair (substantially harmonized)\n- `\u002Fcs:gdpr-audit-prep` — if connected device handles personal data\n- `\u002Fcs:gc-review` — for Warning Letter response coordination\n\n## Related\n\n- Agent: [`cs-fda-qsr-auditor`](..\u002F..\u002Fagents\u002Fcs-fda-qsr-auditor.md)\n- Skill: [`fda-consultant-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md)\n- Adjacent: `..\u002Fiso13485-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:fda-qsr-audit-prep — FDA QSR Forcing Questions\n\n**Command:** `\u002Fcs:fda-qsr-audit-prep \u003Cscope>`\n\nThe FDA QSR auditor pressure-tests any US medical-device QSR work. Six questions before any internal audit, FDA inspection, Form 483 response, or recall decision.\n\n## When to Run\n\n- Before annual internal QSR audit\n- Before pre-FDA-inspection readiness review (any device commercially distributed in US)\n- After receiving Form 483 observations\n- After Warning Letter receipt\n- After MDR-reportable event\n- Before recall decision (voluntary vs FDA-initiated)\n- Before submitting 510(k) \u002F PMA (where QSR posture affects approval timeline)\n\n## The Six QSR Questions\n\n### 1. Show me the complaint files from the last quarter — and the corresponding MDR reports.\n**21 CFR 820.198 + 21 CFR 803 — most-cited FDA inspection area.**\n- Complaint log complete: who \u002F what \u002F when \u002F device \u002F batch\n- Investigation closure within reasonable timeline\n- MDR-reporting decision tree applied: death OR serious injury OR malfunction-that-could-cause = MDR\n- 30-day timeline for most MDR reports; 5 days for certain serious events\n- Complaint trending input to management review\n\n### 2. When was process validation (IQ\u002FOQ\u002FPQ) last revalidated per 21 CFR 820.75?\n**Cross-walks ISO 13485 Clause 7.5.6 (substantially harmonized post-Feb 2026).**\n- Initial validation at process introduction\n- Revalidation triggers: process \u002F equipment \u002F material change OR periodic schedule\n- Statistical techniques per 21 CFR 820.250 where applicable\n- Cross-check with cs-cqm-iso13485 for ISO 13485 alignment\n\n### 3. Show me the DHRs for products commercially distributed in last 2 years.\n**21 CFR 820.180 — 2-year retention from commercial distribution; check sampling for completeness.**\n- Device History Record (DHR) for each unit\u002Flot\u002Fbatch\n- Must include: dates of manufacture, quantity manufactured, quantity released, acceptance records, primary identification label, device identification, control number\n- Sample stratified by product class\n- Verify DHR closeness to DHF (design history file)\n\n### 4. Show me CAPAs from the last 6 months with effectiveness verification.\n**21 CFR 820.100 = ISO 13485 8.5.2 substantially harmonized.**\n- Root cause analysis depth (5 Why minimum)\n- Effectiveness verification = measurable evidence, not \"we updated the procedure\"\n- Containment \u002F correction \u002F corrective action distinction documented\n- Closure approval by appropriate authority\n- Aging CAPAs > 90 days flagged\n\n### 5. Show me labeling (21 CFR 801) review for the most recent product launch.\n**FDA-specific overlay not in ISO 13485.**\n- Labeling per 21 CFR 801 requirements\n- For specific device types: also 21 CFR 800 series sectoral overlays\n- UDI (Unique Device Identification) per 21 CFR 830\n- Promotional materials reviewed for accuracy + non-misleading\n\n### 6. If a Form 483 was issued in the last 3 years, show me the closure status.\n**Form 483 = FDA observation; not equivalent to ISO nonconformity.**\n- Response within 15 working days\n- Each observation has documented corrective + preventive action with timeline\n- Effectiveness verification evidence\n- For Warning Letters: separate response track + potentially FDA meeting\n\n## Workflow\n\n```bash\n# 1. QSR compliance posture\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fqsr_compliance_checker.py compliance_state.json\n\n# 2. FDA submission tracking (510(k) \u002F PMA \u002F IDE)\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Ffda_submission_tracker.py submissions.json\n\n# 3. HIPAA overlap (if connected device handles PHI)\npython ra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002Fscripts\u002Fhipaa_risk_assessment.py phi_inventory.json\n\n# 4. Mock FDA inspection\npython ..\u002F..\u002Fskills\u002Fcompliance-os\u002Fscripts\u002Faudit_simulator.py fda_qsr_scope.json\n```\n\n## Output Format\n\n```markdown\n# FDA QSR Audit Prep: \u003Cscope>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[programme-plan | inspection-readiness | 483-response | MDR-decision | recall]\n\n## Complaint + MDR Posture\n- Complaints last quarter: N\n- MDR-reportable events: M\n- MDR reports filed within timeline: % (target 100%)\n- Complaint trending review at management level: yes\u002Fno\n\n## Process Validation Status (21 CFR 820.75)\n- Validations on schedule: %\n- Stale validations: \u003Clist>\n- Statistical techniques applied: yes\u002Fno per process\n\n## DHR Completeness (21 CFR 820.180)\n- DHRs sampled: N\n- Completeness rate: %\n- 2-year retention compliant: yes\u002Fno\n- Stratified by product class: yes\u002Fno\n\n## CAPA Health (21 CFR 820.100)\n- CAPAs sampled: N\n- Root cause analysis depth: adequate\u002Finadequate\n- Effectiveness verification: complete\u002Fincomplete\n- Aging CAPAs > 90 days: N\n\n## Labeling (21 CFR 801)\n- Recent products reviewed: \u003Clist>\n- Labeling accurate + non-misleading: yes\u002Fno\n- UDI compliance per 21 CFR 830: yes\u002Fno\n\n## Form 483 \u002F Warning Letter History\n- Form 483s last 3 years: N (each: closed\u002Fin-progress)\n- Warning Letters last 5 years: N (each: closed\u002Fin-progress)\n- Pattern across observations: \u003Cthematic>\n\n## ISO 13485 Cross-Walk (post-Feb 2026 harmonization)\n- ISO 13485 audit findings: \u003Clink to cs-cqm-iso13485 output>\n- FDA-specific overlays remaining: labeling + complaint handling + MDR reporting + recall procedures\n- Cross-framework reuse: % of evidence shared\n\n## Verdict\n🟢 INSPECTION-READY | 🟡 GAPS-IDENTIFIED | 🔴 NOT-READY\n\n## Top 3 Actions\n[3 concrete next steps with owner + FDA-cited timeline (15 days \u002F 30 days \u002F etc.)]\n\n## Outside Counsel Required\n[For Warning Letter response, recall decisions, or 510(k) \u002F PMA strategy disputes]\n```\n\n## Routing\n\n- `\u002Fcs:compliance-readiness` — for multi-framework view\n- `\u002Fcs:iso13485-audit-prep` — for ISO 13485 cross-walk pair (substantially harmonized)\n- `\u002Fcs:gdpr-audit-prep` — if connected device handles personal data\n- `\u002Fcs:gc-review` — for Warning Letter response coordination\n\n## Related\n\n- Agent: [`cs-fda-qsr-auditor`](..\u002F..\u002Fagents\u002Fcs-fda-qsr-auditor.md)\n- Skill: [`fda-consultant-specialist`](..\u002F..\u002F..\u002Fra-qm-team\u002Fskills\u002Ffda-consultant-specialist\u002FSKILL.md)\n- Adjacent: `..\u002Fiso13485-audit-prep\u002F`, `..\u002Fcompliance-readiness\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","compliance-os\u002Fskills\u002Ffda-qsr-audit-prep",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill fda-qsr-audit-prep",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill fda-qsr-audit-prep",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill fda-qsr-audit-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fcompliance-os\u002Fskills\u002Ffda-qsr-audit-prep\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","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, deepread for evidence-first reading of supplied documents) 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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]