[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G212SDB5YFSY6JPBVCFGAR":3,"skill-same:01M6G212SDB5YFSY6JPBVCFGAR":101},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6G212SDB5YFSY6JPBVCFGAR","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.","oabdelmaksoud\u002FAgention","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D8A4TE76V3DCSH3D94VG1V",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"mdr 745 specialist","mdr","post","technical documentation","eu mdr","iii","clinical","medical","device","files","Market","evidence","technical","Rules","classification","Evaluation","compliance","integration","documentation","2026-11-10 10:12:30",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":48,"description":7},[49,50,51,52,27,53,54,55,56,57],"MDR compliance","EU MDR","medical device classification","Annex VIII","clinical evaluation","PMCF","EUDAMED","UDI","notified body","main","a318f48de3c5718e8ea2e9f6fae7790e8a759e85","upstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:23:03",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add oabdelmaksoud\u002FAgention --skill mdr-745-specialist",{"tool":73,"command":74},"bunx","bunx skills add oabdelmaksoud\u002FAgention --skill mdr-745-specialist",{"tool":76,"command":77},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FAgention --skill mdr-745-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002FSKILL.md",true,[81,87,91,95],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fclinical-evidence-requirements.md","REFERENCE","参考文档",9408,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Freferences\u002Fclinical-evidence-requirements.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fmdr-classification-guide.md",8948,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Freferences\u002Fmdr-classification-guide.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Ftechnical-documentation-templates.md",10364,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Freferences\u002Ftechnical-documentation-templates.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fmdr_gap_analyzer.py","SCRIPT","脚本",18171,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Fscripts\u002Fmdr_gap_analyzer.py",[102,126,140,170,196,216],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":43},"01M6G2QFCBNBYAJF2KTK85G9A6","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[114,115,116,117,118,119,120,121,122,123,124,125],"translate","doc","visa doc translate","bilingual","with","english","application","PDF","translation","documents","create","images",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":43},"01M6G2QB09TSK6BY4ME5X20EVQ","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[133,134,135,136,137,138,139],"verification","loop","verification loop","sessions","code","claude code sessions","system",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":155,"publishedAt":43},"01M6G2Q6V2F7G03VAAF27FXPJR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[146,149,152],{"categoryNo":147,"categoryName":148,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":150,"categoryName":151,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[156,157,158,159,160,161,162,163,41,137,164,165,166,167,118,168,169],"workflow","tdd","tdd workflow","use","unit","coverage","refactoring","e2e","development","e2e tests","tests","driven","test","writing",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":43},"01M6G2Q359YJRWAR2PFCEQAXF3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,118],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":43},"01M6G2PY8B2FWZTWPZ84H83Y7C","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[202],{"categoryNo":147,"categoryName":148,"taxonomyType":111,"taxonomyTypeDesc":112},[204,205,206,207,137,208,209,210,211,139,212,213,214,215],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection","mock",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":43},"01M6G2PSCN2GXV9FFZDRRRWVB6","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[223,224,225,206,226,58,227],"concurrency","swift concurrency","swift concurrency 6 2","default","types"]