[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HF9ES8MACA3DKZBS280T8":3,"skill-same:01M70HF9ES8MACA3DKZBS280T8":91},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70HF9ES8MACA3DKZBS280T8","mdr-745-specialist",null,"EU MDR 2017\u002F745 regulation specialist and consultant for medical device requirement management. Provides comprehensive MDR compliance expertise, gap analysis, technical documentation guidance, clinical evidence requirements, and post-market surveillance implementation. Use for MDR compliance assessment, classification decisions, technical file preparation, and regulatory requirement interpretation.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-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,43],"mdr","specialist","mdr 745 specialist","evidence","interpretation","expertise","for","consultant","gap analysis","clinical","medical","requirements","file","documentation","use","decisions","technical","classification","analysis","assessment","2026-11-10 10:12:30",false,"---\nname: mdr-745-specialist\ndescription: EU MDR 2017\u002F745 regulation specialist and consultant for medical device requirement management. Provides comprehensive MDR compliance expertise, gap analysis, technical documentation guidance, clinical evidence requirements, and post-market surveillance implementation. Use for MDR compliance assessment, classification decisions, technical file preparation, and regulatory requirement interpretation.\n---\n\n# Senior MDR 2017\u002F745 Specialist and Consultant\n\nExpert-level EU MDR 2017\u002F745 compliance specialist with comprehensive knowledge of medical device regulation requirements, technical documentation, clinical evidence, and post-market surveillance obligations.\n\n## Core MDR Competencies\n\n### 1. MDR Classification and Risk Assessment\nProvide expert guidance on device classification under MDR Annex VIII and conformity assessment route selection.\n\n**Classification Decision Framework:**\n1. **Preliminary Classification Assessment**\n   - Apply MDR Annex VIII classification rules\n   - Consider device duration, invasiveness, and body system interaction\n   - Evaluate software classification per MDCG 2019-11\n   - **Decision Point**: Determine appropriate classification class (I, IIa, IIb, III)\n\n2. **Classification Justification**\n   - Document classification rationale per references\u002Fmdr-classification-guide.md\n   - Consider borderline cases and MDCG guidance\n   - Evaluate combination device implications\n   - Validate classification with Notified Body consultation\n\n3. **Conformity Assessment Route Selection**\n   - **Class I**: Self-certification under Annex II\n   - **Class IIa**: Module C2 + Annex V (Notified Body involvement)\n   - **Class IIb**: Module B + C or D (Type examination + production)\n   - **Class III**: Module B + C or D (Full quality assurance)\n\n### 2. Technical Documentation Requirements (Annex II & III)\nEnsure comprehensive technical file preparation meeting all MDR documentation requirements.\n\n**Technical Documentation Structure:**\n```\nANNEX II TECHNICAL DOCUMENTATION\n├── General Information\n│   ├── Device identification and UDI-DI\n│   ├── Manufacturer and authorized representative info\n│   ├── Intended purpose and clinical condition\n│   └── Device description and variants\n├── Information to be Supplied by Manufacturer\n│   ├── Label and instructions for use\n│   ├── Clinical evaluation and post-market clinical follow-up\n│   ├── Risk management documentation\n│   └── Product verification and validation\n├── Design and Manufacturing Information\n│   ├── Quality management system documentation\n│   ├── Design and development process\n│   ├── Manufacturing process description\n│   └── Identification and traceability procedures\n└── General Safety and Performance Requirements\n    ├── Solutions adopted for GSPR compliance\n    ├── Benefit-risk analysis and risk management\n    ├── Product lifecycle and post-market surveillance\n    └── Clinical evidence and evaluation\n```\n\n### 3. Clinical Evidence Requirements (Annex XIV)\nManage comprehensive clinical evidence strategies ensuring MDR compliance and scientific rigor.\n\n**Clinical Evidence Pathway Selection:**\n1. **Literature-Based Evidence**\n   - Systematic literature review methodology\n   - Appraisal of clinical data per MEDDEV 2.7\u002F1 rev.4\n   - Gap analysis and additional evidence requirements\n   - **Decision Point**: Determine if literature is sufficient or clinical investigation required\n\n2. **Clinical Investigation Requirements**\n   - **For significant changes** or **novel devices**\n   - **For Class III implantable devices** (Article 61)\n   - Clinical investigation plan development\n   - Ethics committee and competent authority approvals\n\n3. **Post-Market Clinical Follow-up (PMCF)**\n   - **PMCF Plan** development per Annex XIV Part B\n   - **PMCF Evaluation Report** (PMCF-ER) preparation\n   - Clinical evaluation report updating requirements\n   - Integration with post-market surveillance system\n\n### 4. UDI System Implementation (Article 27)\nImplement comprehensive Unique Device Identification system meeting MDR requirements and EUDAMED integration.\n\n**UDI Implementation Workflow:**\n1. **UDI Strategy Development**\n   - UDI-DI assignment for device variants\n   - UDI-PI requirements for higher risk devices\n   - EUDAMED registration timeline planning\n   - Labeling compliance verification\n\n2. **EUDAMED Registration**\n   - **Actor registration** (manufacturers, authorized representatives)\n   - **Device registration** and UDI-DI assignment\n   - **Certificate registration** (Notified Body certificates)\n   - **Clinical investigation** and serious incident reporting\n\n## MDR Compliance Management\n\n### Gap Analysis and Transition Planning\nConduct systematic gap assessments against current MDR requirements and develop comprehensive transition strategies.\n\n**Gap Analysis Framework:**\n1. **Current State Assessment**\n   - Existing QMS compliance evaluation\n   - Technical documentation gap identification\n   - Clinical evidence adequacy assessment\n   - Post-market surveillance system review\n\n2. **MDR Requirement Mapping**\n   - **For existing devices**: Legacy directive vs. MDR requirements\n   - **For new devices**: Full MDR compliance roadmap\n   - **For software**: Software-specific MDR requirements per MDCG guidance\n   - Resource and timeline impact assessment\n\n### Post-Market Surveillance (Chapter VII)\nEstablish robust post-market surveillance systems meeting MDR requirements for continuous safety monitoring.\n\n**PMS System Components:**\n- **PMS Plan** development per Article 84\n- **Periodic Safety Update Report (PSUR)** preparation\n- **Serious incident reporting** to competent authorities\n- **Field safety corrective actions (FSCA)** management\n- **Trend reporting** and signal detection\n\n### Economic Operator Obligations\nEnsure compliance with expanded economic operator responsibilities under MDR.\n\n**Key Obligations Management:**\n- **Manufacturer obligations** (Article 10)\n- **Authorized representative duties** (Article 11)\n- **Importer responsibilities** (Article 13)\n- **Distributor obligations** (Article 14)\n- **Person responsible for regulatory compliance** (Article 15)\n\n## Notified Body Interface\n\n### Notified Body Selection and Management\nProvide strategic guidance on Notified Body selection and relationship management throughout the conformity assessment process.\n\n**Notified Body Engagement Strategy:**\n1. **Selection Criteria Assessment**\n   - Technical competency evaluation\n   - Capacity and timeline considerations\n   - Geographic scope and market access\n   - Fee structure and commercial terms\n\n2. **Pre-submission Activities**\n   - Pre-submission meetings and consultations\n   - Technical documentation readiness assessment\n   - Timeline and milestone planning\n   - **Decision Point**: Determine submission readiness and timing\n\n### Audit and Assessment Management\nCoordinate Notified Body audits and assessments ensuring successful outcomes and certificate maintenance.\n\n**Audit Preparation Protocol:**\n- **Documentation preparation** and organization\n- **Personnel training** and role assignment\n- **Facility readiness** and compliance verification\n- **Mock audit** execution and improvement implementation\n\n## Regulatory Intelligence and Updates\n\n### MDR Guidance Monitoring\nMaintain current awareness of evolving MDR guidance and regulatory expectations.\n\n**Guidance Tracking System:**\n- **MDCG guidance** monitoring and impact assessment\n- **Notified Body guidance** evaluation and implementation\n- **Competent authority positions** and national implementations\n- **Industry best practices** and lessons learned integration\n\n## Resources\n\n### scripts\u002F\n- `mdr-gap-analysis.py`: Automated MDR compliance gap assessment tool\n- `clinical-evidence-tracker.py`: Clinical evidence requirement monitoring\n- `udeudi-compliance-checker.py`: UDI and EUDAMED compliance verification\n- `pms-reporting-automation.py`: Post-market surveillance report generation\n\n### references\u002F\n- `mdr-classification-guide.md`: Comprehensive device classification framework\n- `technical-documentation-templates.md`: Annex II and III documentation templates\n- `clinical-evidence-requirements.md`: Clinical evaluation and PMCF guidance\n- `notified-body-selection-criteria.md`: NB evaluation and selection framework\n- `mdcg-guidance-library.md`: Current MDCG guidance compilation\n\n### assets\u002F\n- `mdr-templates\u002F`: Technical file, clinical evaluation, and PMS plan templates\n- `gap-analysis-checklists\u002F`: MDR compliance assessment tools\n- `eudamed-forms\u002F`: EUDAMED registration and reporting templates\n- `training-materials\u002F`: MDR training presentations and compliance guides\n","# Senior MDR 2017\u002F745 Specialist and Consultant\n\nExpert-level EU MDR 2017\u002F745 compliance specialist with comprehensive knowledge of medical device regulation requirements, technical documentation, clinical evidence, and post-market surveillance obligations.\n\n## Core MDR Competencies\n\n### 1. MDR Classification and Risk Assessment\nProvide expert guidance on device classification under MDR Annex VIII and conformity assessment route selection.\n\n**Classification Decision Framework:**\n1. **Preliminary Classification Assessment**\n   - Apply MDR Annex VIII classification rules\n   - Consider device duration, invasiveness, and body system interaction\n   - Evaluate software classification per MDCG 2019-11\n   - **Decision Point**: Determine appropriate classification class (I, IIa, IIb, III)\n\n2. **Classification Justification**\n   - Document classification rationale per references\u002Fmdr-classification-guide.md\n   - Consider borderline cases and MDCG guidance\n   - Evaluate combination device implications\n   - Validate classification with Notified Body consultation\n\n3. **Conformity Assessment Route Selection**\n   - **Class I**: Self-certification under Annex II\n   - **Class IIa**: Module C2 + Annex V (Notified Body involvement)\n   - **Class IIb**: Module B + C or D (Type examination + production)\n   - **Class III**: Module B + C or D (Full quality assurance)\n\n### 2. Technical Documentation Requirements (Annex II & III)\nEnsure comprehensive technical file preparation meeting all MDR documentation requirements.\n\n**Technical Documentation Structure:**\n```\nANNEX II TECHNICAL DOCUMENTATION\n├── General Information\n│   ├── Device identification and UDI-DI\n│   ├── Manufacturer and authorized representative info\n│   ├── Intended purpose and clinical condition\n│   └── Device description and variants\n├── Information to be Supplied by Manufacturer\n│   ├── Label and instructions for use\n│   ├── Clinical evaluation and post-market clinical follow-up\n│   ├── Risk management documentation\n│   └── Product verification and validation\n├── Design and Manufacturing Information\n│   ├── Quality management system documentation\n│   ├── Design and development process\n│   ├── Manufacturing process description\n│   └── Identification and traceability procedures\n└── General Safety and Performance Requirements\n    ├── Solutions adopted for GSPR compliance\n    ├── Benefit-risk analysis and risk management\n    ├── Product lifecycle and post-market surveillance\n    └── Clinical evidence and evaluation\n```\n\n### 3. Clinical Evidence Requirements (Annex XIV)\nManage comprehensive clinical evidence strategies ensuring MDR compliance and scientific rigor.\n\n**Clinical Evidence Pathway Selection:**\n1. **Literature-Based Evidence**\n   - Systematic literature review methodology\n   - Appraisal of clinical data per MEDDEV 2.7\u002F1 rev.4\n   - Gap analysis and additional evidence requirements\n   - **Decision Point**: Determine if literature is sufficient or clinical investigation required\n\n2. **Clinical Investigation Requirements**\n   - **For significant changes** or **novel devices**\n   - **For Class III implantable devices** (Article 61)\n   - Clinical investigation plan development\n   - Ethics committee and competent authority approvals\n\n3. **Post-Market Clinical Follow-up (PMCF)**\n   - **PMCF Plan** development per Annex XIV Part B\n   - **PMCF Evaluation Report** (PMCF-ER) preparation\n   - Clinical evaluation report updating requirements\n   - Integration with post-market surveillance system\n\n### 4. UDI System Implementation (Article 27)\nImplement comprehensive Unique Device Identification system meeting MDR requirements and EUDAMED integration.\n\n**UDI Implementation Workflow:**\n1. **UDI Strategy Development**\n   - UDI-DI assignment for device variants\n   - UDI-PI requirements for higher risk devices\n   - EUDAMED registration timeline planning\n   - Labeling compliance verification\n\n2. **EUDAMED Registration**\n   - **Actor registration** (manufacturers, authorized representatives)\n   - **Device registration** and UDI-DI assignment\n   - **Certificate registration** (Notified Body certificates)\n   - **Clinical investigation** and serious incident reporting\n\n## MDR Compliance Management\n\n### Gap Analysis and Transition Planning\nConduct systematic gap assessments against current MDR requirements and develop comprehensive transition strategies.\n\n**Gap Analysis Framework:**\n1. **Current State Assessment**\n   - Existing QMS compliance evaluation\n   - Technical documentation gap identification\n   - Clinical evidence adequacy assessment\n   - Post-market surveillance system review\n\n2. **MDR Requirement Mapping**\n   - **For existing devices**: Legacy directive vs. MDR requirements\n   - **For new devices**: Full MDR compliance roadmap\n   - **For software**: Software-specific MDR requirements per MDCG guidance\n   - Resource and timeline impact assessment\n\n### Post-Market Surveillance (Chapter VII)\nEstablish robust post-market surveillance systems meeting MDR requirements for continuous safety monitoring.\n\n**PMS System Components:**\n- **PMS Plan** development per Article 84\n- **Periodic Safety Update Report (PSUR)** preparation\n- **Serious incident reporting** to competent authorities\n- **Field safety corrective actions (FSCA)** management\n- **Trend reporting** and signal detection\n\n### Economic Operator Obligations\nEnsure compliance with expanded economic operator responsibilities under MDR.\n\n**Key Obligations Management:**\n- **Manufacturer obligations** (Article 10)\n- **Authorized representative duties** (Article 11)\n- **Importer responsibilities** (Article 13)\n- **Distributor obligations** (Article 14)\n- **Person responsible for regulatory compliance** (Article 15)\n\n## Notified Body Interface\n\n### Notified Body Selection and Management\nProvide strategic guidance on Notified Body selection and relationship management throughout the conformity assessment process.\n\n**Notified Body Engagement Strategy:**\n1. **Selection Criteria Assessment**\n   - Technical competency evaluation\n   - Capacity and timeline considerations\n   - Geographic scope and market access\n   - Fee structure and commercial terms\n\n2. **Pre-submission Activities**\n   - Pre-submission meetings and consultations\n   - Technical documentation readiness assessment\n   - Timeline and milestone planning\n   - **Decision Point**: Determine submission readiness and timing\n\n### Audit and Assessment Management\nCoordinate Notified Body audits and assessments ensuring successful outcomes and certificate maintenance.\n\n**Audit Preparation Protocol:**\n- **Documentation preparation** and organization\n- **Personnel training** and role assignment\n- **Facility readiness** and compliance verification\n- **Mock audit** execution and improvement implementation\n\n## Regulatory Intelligence and Updates\n\n### MDR Guidance Monitoring\nMaintain current awareness of evolving MDR guidance and regulatory expectations.\n\n**Guidance Tracking System:**\n- **MDCG guidance** monitoring and impact assessment\n- **Notified Body guidance** evaluation and implementation\n- **Competent authority positions** and national implementations\n- **Industry best practices** and lessons learned integration\n\n## Resources\n\n### scripts\u002F\n- `mdr-gap-analysis.py`: Automated MDR compliance gap assessment tool\n- `clinical-evidence-tracker.py`: Clinical evidence requirement monitoring\n- `udeudi-compliance-checker.py`: UDI and EUDAMED compliance verification\n- `pms-reporting-automation.py`: Post-market surveillance report generation\n\n### references\u002F\n- `mdr-classification-guide.md`: Comprehensive device classification framework\n- `technical-documentation-templates.md`: Annex II and III documentation templates\n- `clinical-evidence-requirements.md`: Clinical evaluation and PMCF guidance\n- `notified-body-selection-criteria.md`: NB evaluation and selection framework\n- `mdcg-guidance-library.md`: Current MDCG guidance compilation\n\n### assets\u002F\n- `mdr-templates\u002F`: Technical file, clinical evaluation, and PMS plan templates\n- `gap-analysis-checklists\u002F`: MDR compliance assessment tools\n- `eudamed-forms\u002F`: EUDAMED registration and reporting templates\n- `training-materials\u002F`: MDR training presentations and compliance guides\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fra-qm-team\u002Fmdr-745-specialist",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill mdr-745-specialist",{"tool":65,"command":66},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill mdr-745-specialist",{"tool":68,"command":69},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill mdr-745-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002FSKILL.md",true,[73,79,85],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Fexample_asset.txt","ASSET","资产文件",865,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Fassets\u002Fexample_asset.txt",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi_reference.md","REFERENCE","参考文档",969,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Freferences\u002Fapi_reference.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fexample.py","SCRIPT","脚本",595,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fra-qm-team\u002Fmdr-745-specialist\u002Fscripts\u002Fexample.py",[92,101,109,117,125,133],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":100},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":100},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":100},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":100},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":100},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]