[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF2DHTM24TTQ1NVXK4D5H5":3,"skill-same:01M6AF2DHTM24TTQ1NVXK4D5H5":93},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AF2DHTM24TTQ1NVXK4D5H5","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.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\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,44,45],"specialist","mdr 745 specialist","mdr","use","expertise","for","consultant","gap analysis","clinical","medical","requirements","evidence","technical documentation","decisions","technical","classification","analysis","compliance","file","assessment","interpretation","documentation","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","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fmdr-745-specialist",3963,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-15 01:32:48",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add davila7\u002Fclaude-code-templates --skill mdr-745-specialist",{"tool":67,"command":68},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill mdr-745-specialist",{"tool":70,"command":71},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill mdr-745-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fmdr-745-specialist\u002FSKILL.md",true,[75,81,87],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Fexample_asset.txt","ASSET","资产文件",865,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fmdr-745-specialist\u002Fassets\u002Fexample_asset.txt",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi_reference.md","REFERENCE","参考文档",969,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fmdr-745-specialist\u002Freferences\u002Fapi_reference.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fexample.py","SCRIPT","脚本",595,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fmdr-745-specialist\u002Fscripts\u002Fexample.py",[94,124,150,181,215,239],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":46},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[106,107,108,109,110,29,111,112,27,113,114,115,116,117,118,119,120,121,122,123],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":46},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[130],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[132,133,38,134,135,136,137,138,139,140,141,113,142,143,144,145,146,147,148,149],"technical debt","debt","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":163,"publishedAt":46},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[156,159,160],{"categoryNo":157,"categoryName":158,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[164,165,166,167,168,169,170,29,171,172,173,174,175,176,177,27,178,179,113,180],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":185,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":46},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[189],{"categoryNo":190,"categoryName":191,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000009","前端开发",[193,194,195,196,197,198,199,200,201,202,203,204,205,42,206,207,208,209,210,211,212,213,29,214],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":185,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":226,"publishedAt":46},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":190,"categoryName":191,"taxonomyType":103,"taxonomyTypeDesc":104},[227,228,229,230,231,194,232,203,204,233,234,235,236,29,237,115,238],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":185,"licenseFileUrl":243,"sourceHtmlUrl":244,"categories":245,"keywords":253,"publishedAt":46},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[246,249,250],{"categoryNo":247,"categoryName":248,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":251,"categoryName":252,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[254,255,44,256,257,258,259,260,196,261,42,142,262,263,264,265,266,176,267,113,268,40,269,270,271,121,272],"discernment nudge","nudge","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]