[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76S40V1SW3KPDKW2FAXGKTX":3,"skill-same:01M76S40V1SW3KPDKW2FAXGKTX":74},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":13,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M76S40V1SW3KPDKW2FAXGKTX","mdr-745-specialist",null,"EU MDR 2017\u002F745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II\u002FIII technical files, Annex XIV clinical evaluation, and EUDAMED integration.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"mdr-745-specialist\"\ndescription: EU MDR 2017\u002F745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II\u002FIII technical files, Annex XIV clinical evaluation, and EUDAMED integration.\ntriggers:\n  - MDR compliance\n  - EU MDR\n  - medical device classification\n  - Annex VIII\n  - technical documentation\n  - clinical evaluation\n  - PMCF\n  - EUDAMED\n  - UDI\n  - notified body\n---\n\n# MDR 2017\u002F745 Specialist\n\nEU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence.\n\n---\n\n## Table of Contents\n\n- [Device Classification Workflow](#device-classification-workflow)\n- [Technical Documentation](#technical-documentation)\n- [Clinical Evidence](#clinical-evidence)\n- [Post-Market Surveillance](#post-market-surveillance)\n- [EUDAMED and UDI](#eudamed-and-udi)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## Device Classification Workflow\n\nClassify device under MDR Annex VIII:\n\n1. Identify device duration (transient, short-term, long-term)\n2. Determine invasiveness level (non-invasive, body orifice, surgical)\n3. Assess body system contact (CNS, cardiac, other)\n4. Check if active device (energy dependent)\n5. Apply classification rules 1-22\n6. For software, apply MDCG 2019-11 algorithm\n7. Document classification rationale\n8. **Validation:** Classification confirmed with Notified Body\n\n### Classification Matrix\n\n| Factor | Class I | Class IIa | Class IIb | Class III |\n|--------|---------|-----------|-----------|-----------|\n| Duration | Any | Short-term | Long-term | Long-term |\n| Invasiveness | Non-invasive | Body orifice | Surgical | Implantable |\n| System | Any | Non-critical | Critical organs | CNS\u002Fcardiac |\n| Risk | Lowest | Low-medium | Medium-high | Highest |\n\n### Software Classification (MDCG 2019-11)\n\n| Information Use | Condition Severity | Class |\n|-----------------|-------------------|-------|\n| Informs decision | Non-serious | IIa |\n| Informs decision | Serious | IIb |\n| Drives\u002Ftreats | Critical | III |\n\n### Classification Examples\n\n**Example 1: Absorbable Surgical Suture**\n- Rule 8 (implantable, long-term)\n- Duration: > 30 days (absorbed)\n- Contact: General tissue\n- Classification: **Class IIb**\n\n**Example 2: AI Diagnostic Software**\n- Rule 11 + MDCG 2019-11\n- Function: Diagnoses serious condition\n- Classification: **Class IIb**\n\n**Example 3: Cardiac Pacemaker**\n- Rule 8 (implantable)\n- Contact: Central circulatory system\n- Classification: **Class III**\n\n---\n\n## Technical Documentation\n\nPrepare technical file per Annex II and III:\n\n1. Create device description (variants, accessories, intended purpose)\n2. Develop labeling (Article 13 requirements, IFU)\n3. Document design and manufacturing process\n4. Complete GSPR compliance matrix\n5. Prepare benefit-risk analysis\n6. Compile verification and validation evidence\n7. Integrate risk management file (ISO 14971)\n8. **Validation:** Technical file reviewed for completeness\n\n### Technical File Structure\n\n```\nANNEX II TECHNICAL DOCUMENTATION\n├── Device description and UDI-DI\n├── Label and instructions for use\n├── Design and manufacturing info\n├── GSPR compliance matrix\n├── Benefit-risk analysis\n├── Verification and validation\n└── Clinical evaluation report\n```\n\n### GSPR Compliance Checklist\n\n| Requirement | Evidence | Status |\n|-------------|----------|--------|\n| Safe design (GSPR 1-3) | Risk management file | ☐ |\n| Chemical properties (GSPR 10.1) | Biocompatibility report | ☐ |\n| Infection risk (GSPR 10.2) | Sterilization validation | ☐ |\n| Software requirements (GSPR 17) | IEC 62304 documentation | ☐ |\n| Labeling (GSPR 23) | Label artwork, IFU | ☐ |\n\n### Conformity Assessment Routes\n\n| Class | Route | NB Involvement |\n|-------|-------|----------------|\n| I | Annex II self-declaration | None |\n| Is\u002FIm | Annex II + IX\u002FXI | Sterile\u002Fmeasuring aspects |\n| IIa | Annex II + IX or XI | Product or QMS |\n| IIb | Annex IX + X or X + XI | Type exam + production |\n| III | Annex IX + X | Full QMS + type exam |\n\n---\n\n## Clinical Evidence\n\nDevelop clinical evidence strategy per Annex XIV:\n\n1. Define clinical claims and endpoints\n2. Conduct systematic literature search\n3. Appraise clinical data quality\n4. Assess equivalence (technical, biological, clinical)\n5. Identify evidence gaps\n6. Determine if clinical investigation required\n7. Prepare Clinical Evaluation Report (CER)\n8. **Validation:** CER reviewed by qualified evaluator\n\n### Evidence Requirements by Class\n\n| Class | Minimum Evidence | Investigation |\n|-------|------------------|---------------|\n| I | Risk-benefit analysis | Not typically required |\n| IIa | Literature + post-market | May be required |\n| IIb | Systematic literature review | Often required |\n| III | Comprehensive clinical data | Required (Article 61) |\n\n### Clinical Evaluation Report Structure\n\n```\nCER CONTENTS\n├── Executive summary\n├── Device scope and intended purpose\n├── Clinical background (state of the art)\n├── Literature search methodology\n├── Data appraisal and analysis\n├── Safety and performance conclusions\n├── Benefit-risk determination\n└── PMCF plan summary\n```\n\n### Qualified Evaluator Requirements\n\n- Medical degree or equivalent healthcare qualification\n- 4+ years clinical experience in relevant field\n- Training in clinical evaluation methodology\n- Understanding of MDR requirements\n\n---\n\n## Post-Market Surveillance\n\nEstablish PMS system per Chapter VII:\n\n1. Develop PMS plan (Article 84)\n2. Define data collection methods\n3. Establish complaint handling procedures\n4. Create vigilance reporting process\n5. Plan Periodic Safety Update Reports (PSUR)\n6. Integrate with PMCF activities\n7. Define trend analysis and signal detection\n8. **Validation:** PMS system audited annually\n\n### PMS System Components\n\n| Component | Requirement | Frequency |\n|-----------|-------------|-----------|\n| PMS Plan | Article 84 | Maintain current |\n| PSUR | Class IIa and higher | Per class schedule |\n| PMCF Plan | Annex XIV Part B | Update with CER |\n| PMCF Report | Annex XIV Part B | Annual (Class III) |\n| Vigilance | Articles 87-92 | As events occur |\n\n### PSUR Schedule\n\n| Class | Frequency |\n|-------|-----------|\n| Class III | Annual |\n| Class IIb implantable | Annual |\n| Class IIb | Every 2 years |\n| Class IIa | When necessary |\n\n### Serious Incident Reporting\n\n| Timeline | Requirement |\n|----------|-------------|\n| 2 days | Serious public health threat |\n| 10 days | Death or serious deterioration |\n| 15 days | Other serious incidents |\n\n---\n\n## EUDAMED and UDI\n\nImplement UDI system per Article 27:\n\n1. Obtain issuing entity code (GS1, HIBCC, ICCBBA)\n2. Assign UDI-DI to each device variant\n3. Assign UDI-PI (production identifier)\n4. Apply UDI carrier to labels (AIDC + HRI)\n5. Register actor in EUDAMED\n6. Register devices in EUDAMED\n7. Upload certificates when available\n8. **Validation:** UDI verified on sample labels\n\n### EUDAMED Modules\n\n| Module | Content | Actor |\n|--------|---------|-------|\n| Actor | Company registration | Manufacturer, AR |\n| UDI\u002FDevice | Device and variant data | Manufacturer |\n| Certificates | NB certificates | Notified Body |\n| Clinical Investigation | Study registration | Sponsor |\n| Vigilance | Incident reports | Manufacturer |\n| Market Surveillance | Authority actions | Competent Authority |\n\n### UDI Label Requirements\n\nRequired elements per Article 13:\n\n- [ ] UDI-DI (device identifier)\n- [ ] UDI-PI (production identifier) for Class II+\n- [ ] AIDC format (barcode\u002FRFID)\n- [ ] HRI format (human-readable)\n- [ ] Manufacturer name and address\n- [ ] Lot\u002Fserial number\n- [ ] Expiration date (if applicable)\n\n---\n\n## Reference Documentation\n\n### MDR Classification Guide\n\n`references\u002Fmdr-classification-guide.md` contains:\n\n- Complete Annex VIII classification rules (Rules 1-22)\n- Software classification per MDCG 2019-11\n- Worked classification examples\n- Conformity assessment route selection\n\n### Clinical Evidence Requirements\n\n`references\u002Fclinical-evidence-requirements.md` contains:\n\n- Clinical evidence framework and hierarchy\n- Literature search methodology\n- Clinical Evaluation Report structure\n- PMCF plan and evaluation report guidance\n\n### Technical Documentation Templates\n\n`references\u002Ftechnical-documentation-templates.md` contains:\n\n- Annex II and III content requirements\n- Design History File structure\n- GSPR compliance matrix template\n- Declaration of Conformity template\n- Notified Body submission checklist\n\n---\n\n## Tools\n\n### MDR Gap Analyzer\n\n```bash\n# Quick gap analysis\npython scripts\u002Fmdr_gap_analyzer.py --device \"Device Name\" --class IIa\n\n# JSON output for integration\npython scripts\u002Fmdr_gap_analyzer.py --device \"Device Name\" --class III --output json\n\n# Interactive assessment\npython scripts\u002Fmdr_gap_analyzer.py --interactive\n```\n\nAnalyzes device against MDR requirements, identifies compliance gaps, generates prioritized recommendations.\n\n**Output includes:**\n- Requirements checklist by category\n- Gap identification with priorities\n- Critical gap highlighting\n- Compliance roadmap recommendations\n\n---\n\n## Notified Body Interface\n\n### Selection Criteria\n\n| Factor | Considerations |\n|--------|----------------|\n| Designation scope | Covers your device type |\n| Capacity | Timeline for initial audit |\n| Geographic reach | Markets you need to access |\n| Technical expertise | Experience with your technology |\n| Fee structure | Transparency, predictability |\n\n### Pre-Submission Checklist\n\n- [ ] Technical documentation complete\n- [ ] GSPR matrix fully addressed\n- [ ] Risk management file current\n- [ ] Clinical evaluation report complete\n- [ ] QMS (ISO 13485) certified\n- [ ] Labeling and IFU finalized\n- [ ] **Validation:** Internal gap assessment complete\n","# MDR 2017\u002F745 Specialist\n\nEU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence.\n\n---\n\n## Table of Contents\n\n- [Device Classification Workflow](#device-classification-workflow)\n- [Technical Documentation](#technical-documentation)\n- [Clinical Evidence](#clinical-evidence)\n- [Post-Market Surveillance](#post-market-surveillance)\n- [EUDAMED and UDI](#eudamed-and-udi)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## Device Classification Workflow\n\nClassify device under MDR Annex VIII:\n\n1. Identify device duration (transient, short-term, long-term)\n2. Determine invasiveness level (non-invasive, body orifice, surgical)\n3. Assess body system contact (CNS, cardiac, other)\n4. Check if active device (energy dependent)\n5. Apply classification rules 1-22\n6. For software, apply MDCG 2019-11 algorithm\n7. Document classification rationale\n8. **Validation:** Classification confirmed with Notified Body\n\n### Classification Matrix\n\n| Factor | Class I | Class IIa | Class IIb | Class III |\n|--------|---------|-----------|-----------|-----------|\n| Duration | Any | Short-term | Long-term | Long-term |\n| Invasiveness | Non-invasive | Body orifice | Surgical | Implantable |\n| System | Any | Non-critical | Critical organs | CNS\u002Fcardiac |\n| Risk | Lowest | Low-medium | Medium-high | Highest |\n\n### Software Classification (MDCG 2019-11)\n\n| Information Use | Condition Severity | Class |\n|-----------------|-------------------|-------|\n| Informs decision | Non-serious | IIa |\n| Informs decision | Serious | IIb |\n| Drives\u002Ftreats | Critical | III |\n\n### Classification Examples\n\n**Example 1: Absorbable Surgical Suture**\n- Rule 8 (implantable, long-term)\n- Duration: > 30 days (absorbed)\n- Contact: General tissue\n- Classification: **Class IIb**\n\n**Example 2: AI Diagnostic Software**\n- Rule 11 + MDCG 2019-11\n- Function: Diagnoses serious condition\n- Classification: **Class IIb**\n\n**Example 3: Cardiac Pacemaker**\n- Rule 8 (implantable)\n- Contact: Central circulatory system\n- Classification: **Class III**\n\n---\n\n## Technical Documentation\n\nPrepare technical file per Annex II and III:\n\n1. Create device description (variants, accessories, intended purpose)\n2. Develop labeling (Article 13 requirements, IFU)\n3. Document design and manufacturing process\n4. Complete GSPR compliance matrix\n5. Prepare benefit-risk analysis\n6. Compile verification and validation evidence\n7. Integrate risk management file (ISO 14971)\n8. **Validation:** Technical file reviewed for completeness\n\n### Technical File Structure\n\n```\nANNEX II TECHNICAL DOCUMENTATION\n├── Device description and UDI-DI\n├── Label and instructions for use\n├── Design and manufacturing info\n├── GSPR compliance matrix\n├── Benefit-risk analysis\n├── Verification and validation\n└── Clinical evaluation report\n```\n\n### GSPR Compliance Checklist\n\n| Requirement | Evidence | Status |\n|-------------|----------|--------|\n| Safe design (GSPR 1-3) | Risk management file | ☐ |\n| Chemical properties (GSPR 10.1) | Biocompatibility report | ☐ |\n| Infection risk (GSPR 10.2) | Sterilization validation | ☐ |\n| Software requirements (GSPR 17) | IEC 62304 documentation | ☐ |\n| Labeling (GSPR 23) | Label artwork, IFU | ☐ |\n\n### Conformity Assessment Routes\n\n| Class | Route | NB Involvement |\n|-------|-------|----------------|\n| I | Annex II self-declaration | None |\n| Is\u002FIm | Annex II + IX\u002FXI | Sterile\u002Fmeasuring aspects |\n| IIa | Annex II + IX or XI | Product or QMS |\n| IIb | Annex IX + X or X + XI | Type exam + production |\n| III | Annex IX + X | Full QMS + type exam |\n\n---\n\n## Clinical Evidence\n\nDevelop clinical evidence strategy per Annex XIV:\n\n1. Define clinical claims and endpoints\n2. Conduct systematic literature search\n3. Appraise clinical data quality\n4. Assess equivalence (technical, biological, clinical)\n5. Identify evidence gaps\n6. Determine if clinical investigation required\n7. Prepare Clinical Evaluation Report (CER)\n8. **Validation:** CER reviewed by qualified evaluator\n\n### Evidence Requirements by Class\n\n| Class | Minimum Evidence | Investigation |\n|-------|------------------|---------------|\n| I | Risk-benefit analysis | Not typically required |\n| IIa | Literature + post-market | May be required |\n| IIb | Systematic literature review | Often required |\n| III | Comprehensive clinical data | Required (Article 61) |\n\n### Clinical Evaluation Report Structure\n\n```\nCER CONTENTS\n├── Executive summary\n├── Device scope and intended purpose\n├── Clinical background (state of the art)\n├── Literature search methodology\n├── Data appraisal and analysis\n├── Safety and performance conclusions\n├── Benefit-risk determination\n└── PMCF plan summary\n```\n\n### Qualified Evaluator Requirements\n\n- Medical degree or equivalent healthcare qualification\n- 4+ years clinical experience in relevant field\n- Training in clinical evaluation methodology\n- Understanding of MDR requirements\n\n---\n\n## Post-Market Surveillance\n\nEstablish PMS system per Chapter VII:\n\n1. Develop PMS plan (Article 84)\n2. Define data collection methods\n3. Establish complaint handling procedures\n4. Create vigilance reporting process\n5. Plan Periodic Safety Update Reports (PSUR)\n6. Integrate with PMCF activities\n7. Define trend analysis and signal detection\n8. **Validation:** PMS system audited annually\n\n### PMS System Components\n\n| Component | Requirement | Frequency |\n|-----------|-------------|-----------|\n| PMS Plan | Article 84 | Maintain current |\n| PSUR | Class IIa and higher | Per class schedule |\n| PMCF Plan | Annex XIV Part B | Update with CER |\n| PMCF Report | Annex XIV Part B | Annual (Class III) |\n| Vigilance | Articles 87-92 | As events occur |\n\n### PSUR Schedule\n\n| Class | Frequency |\n|-------|-----------|\n| Class III | Annual |\n| Class IIb implantable | Annual |\n| Class IIb | Every 2 years |\n| Class IIa | When necessary |\n\n### Serious Incident Reporting\n\n| Timeline | Requirement |\n|----------|-------------|\n| 2 days | Serious public health threat |\n| 10 days | Death or serious deterioration |\n| 15 days | Other serious incidents |\n\n---\n\n## EUDAMED and UDI\n\nImplement UDI system per Article 27:\n\n1. Obtain issuing entity code (GS1, HIBCC, ICCBBA)\n2. Assign UDI-DI to each device variant\n3. Assign UDI-PI (production identifier)\n4. Apply UDI carrier to labels (AIDC + HRI)\n5. Register actor in EUDAMED\n6. Register devices in EUDAMED\n7. Upload certificates when available\n8. **Validation:** UDI verified on sample labels\n\n### EUDAMED Modules\n\n| Module | Content | Actor |\n|--------|---------|-------|\n| Actor | Company registration | Manufacturer, AR |\n| UDI\u002FDevice | Device and variant data | Manufacturer |\n| Certificates | NB certificates | Notified Body |\n| Clinical Investigation | Study registration | Sponsor |\n| Vigilance | Incident reports | Manufacturer |\n| Market Surveillance | Authority actions | Competent Authority |\n\n### UDI Label Requirements\n\nRequired elements per Article 13:\n\n- [ ] UDI-DI (device identifier)\n- [ ] UDI-PI (production identifier) for Class II+\n- [ ] AIDC format (barcode\u002FRFID)\n- [ ] HRI format (human-readable)\n- [ ] Manufacturer name and address\n- [ ] Lot\u002Fserial number\n- [ ] Expiration date (if applicable)\n\n---\n\n## Reference Documentation\n\n### MDR Classification Guide\n\n`references\u002Fmdr-classification-guide.md` contains:\n\n- Complete Annex VIII classification rules (Rules 1-22)\n- Software classification per MDCG 2019-11\n- Worked classification examples\n- Conformity assessment route selection\n\n### Clinical Evidence Requirements\n\n`references\u002Fclinical-evidence-requirements.md` contains:\n\n- Clinical evidence framework and hierarchy\n- Literature search methodology\n- Clinical Evaluation Report structure\n- PMCF plan and evaluation report guidance\n\n### Technical Documentation Templates\n\n`references\u002Ftechnical-documentation-templates.md` contains:\n\n- Annex II and III content requirements\n- Design History File structure\n- GSPR compliance matrix template\n- Declaration of Conformity template\n- Notified Body submission checklist\n\n---\n\n## Tools\n\n### MDR Gap Analyzer\n\n```bash\n# Quick gap analysis\npython scripts\u002Fmdr_gap_analyzer.py --device \"Device Name\" --class IIa\n\n# JSON output for integration\npython scripts\u002Fmdr_gap_analyzer.py --device \"Device Name\" --class III --output json\n\n# Interactive assessment\npython scripts\u002Fmdr_gap_analyzer.py --interactive\n```\n\nAnalyzes device against MDR requirements, identifies compliance gaps, generates prioritized recommendations.\n\n**Output includes:**\n- Requirements checklist by category\n- Gap identification with priorities\n- Critical gap highlighting\n- Compliance roadmap recommendations\n\n---\n\n## Notified Body Interface\n\n### Selection Criteria\n\n| Factor | Considerations |\n|--------|----------------|\n| Designation scope | Covers your device type |\n| Capacity | Timeline for initial audit |\n| Geographic reach | Markets you need to access |\n| Technical expertise | Experience with your technology |\n| Fee structure | Transparency, predictability |\n\n### Pre-Submission Checklist\n\n- [ ] Technical documentation complete\n- [ ] GSPR matrix fully addressed\n- [ ] Risk management file current\n- [ ] Clinical evaluation report complete\n- [ ] QMS (ISO 13485) certified\n- [ ] Labeling and IFU finalized\n- [ ] **Validation:** Internal gap assessment complete\n",{"name":5,"triggers":23,"description":7},[24,25,26,27,28,29,30,31,32,33],"MDR compliance","EU MDR","medical device classification","Annex VIII","technical documentation","clinical evaluation","PMCF","EUDAMED","UDI","notified body","main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","ra-qm-team\u002Fskills\u002Fmdr-745-specialist","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add msm47\u002FGitskil --skill mdr-745-specialist",{"tool":46,"command":47},"bunx","bunx skills add msm47\u002FGitskil --skill mdr-745-specialist",{"tool":49,"command":50},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill mdr-745-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fclinical-evidence-requirements.md","REFERENCE","参考文档",9408,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002Freferences\u002Fclinical-evidence-requirements.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fmdr-classification-guide.md",8948,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002Freferences\u002Fmdr-classification-guide.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Ftechnical-documentation-templates.md",10364,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002Freferences\u002Ftechnical-documentation-templates.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fmdr_gap_analyzer.py","SCRIPT","脚本",18171,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fmdr-745-specialist\u002Fscripts\u002Fmdr_gap_analyzer.py",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","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. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","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. Triggers — \"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]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","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. Triggers: '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]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","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. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. 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\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M76S78K1ZJ092YYRKX0KBTYJ","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.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' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: '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 trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]