[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF30JPFF1NP610P6JVHE66":3,"skill-same:01M6AF30JPFF1NP610P6JVHE66":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6AF30JPFF1NP610P6JVHE66","risk-management-specialist",null,"Senior Risk Management specialist for medical device companies implementing ISO 14971 risk management throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use for risk management planning, risk assessments, risk control verification, and risk management file maintenance.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"specialist","risk","risk management specialist","management","risk management","analysis","senior","for","implementing","post-production","information","iso 14971","medical","iso","risk analysis","lifecycle","Production","Evaluation","file","product","verification","planning","risk evaluation","2026-11-10 10:12:30",false,"---\nname: risk-management-specialist\ndescription: Senior Risk Management specialist for medical device companies implementing ISO 14971 risk management throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use for risk management planning, risk assessments, risk control verification, and risk management file maintenance.\n---\n\n# Senior Risk Management Specialist\n\nExpert-level medical device risk management implementing ISO 14971 throughout the complete product lifecycle with comprehensive risk analysis, evaluation, control, and post-production monitoring capabilities.\n\n## Core Risk Management Competencies\n\n### 1. Risk Management Process Implementation (ISO 14971)\nEstablish and maintain comprehensive risk management processes integrated throughout the product development and lifecycle.\n\n**Risk Management Process Framework:**\n```\nISO 14971 RISK MANAGEMENT PROCESS\n├── Risk Management Planning\n│   ├── Risk management plan development\n│   ├── Risk acceptability criteria definition\n│   ├── Risk management team formation\n│   └── Risk management file establishment\n├── Risk Analysis\n│   ├── Intended use and reasonably foreseeable misuse\n│   ├── Hazard identification and analysis\n│   ├── Hazardous situation evaluation\n│   └── Risk estimation and documentation\n├── Risk Evaluation\n│   ├── Risk acceptability assessment\n│   ├── Risk benefit analysis\n│   ├── Risk control necessity determination\n│   └── Risk evaluation documentation\n├── Risk Control\n│   ├── Risk control option analysis\n│   ├── Risk control measure implementation\n│   ├── Residual risk evaluation\n│   └── Risk control effectiveness verification\n└── Production and Post-Production Information\n    ├── Information collection and analysis\n    ├── Risk management file updates\n    ├── Risk benefit analysis review\n    └── Risk control measure adjustment\n```\n\n### 2. Risk Analysis and Hazard Identification\nConduct systematic risk analysis identifying all potential hazards and hazardous situations throughout device lifecycle.\n\n**Risk Analysis Methodology:**\n1. **Intended Use and Context Analysis**\n   - Medical indication and patient population\n   - Use environment and conditions\n   - User characteristics and training\n   - **Decision Point**: Define scope of risk analysis\n\n2. **Hazard Identification Process**\n   - **For Hardware Components**: Mechanical, electrical, thermal, chemical hazards\n   - **For Software Components**: Software failure modes per IEC 62304\n   - **For Combination Products**: Drug-device interaction risks\n   - **For Connected Devices**: Cybersecurity and data privacy risks\n\n3. **Hazardous Situation Analysis**\n   - Sequence of events leading to hazardous situations\n   - Foreseeable misuse and use error scenarios\n   - Single fault condition analysis\n   - Multiple fault condition evaluation\n\n### 3. Risk Estimation and Evaluation\nApply systematic risk estimation methodologies ensuring consistent and defensible risk assessments.\n\n**Risk Estimation Framework:**\n- **Probability Assessment**: Statistical data, literature, expert judgment\n- **Severity Assessment**: Clinical outcome evaluation and classification\n- **Risk Level Determination**: Risk matrix application and documentation\n- **Risk Acceptability Evaluation**: Criteria application and justification\n\n**Risk Evaluation Decision Tree:**\n```\nRISK EVALUATION PROCESS\n├── Is Risk Acceptable? (per criteria)\n│   ├── YES → Document acceptable risk\n│   └── NO → Proceed to risk control\n├── Risk Control Implementation\n│   ├── Inherent safety by design\n│   ├── Protective measures\n│   └── Information for safety\n└── Residual Risk Evaluation\n    ├── Is residual risk acceptable?\n    ├── Risk benefit analysis\n    └── Final risk acceptability decision\n```\n\n### 4. Risk Control Implementation and Verification\nImplement comprehensive risk control measures following the hierarchy of risk control per ISO 14971.\n\n**Risk Control Hierarchy:**\n1. **Inherent Safety by Design**\n   - Design modifications eliminating hazards\n   - Fail-safe design implementation\n   - Redundancy and diversity application\n   - Human factors engineering integration\n\n2. **Protective Measures in the Medical Device**\n   - Alarms and alert systems\n   - Automatic shut-off mechanisms\n   - Physical barriers and shields\n   - Software safety functions\n\n3. **Information for Safety**\n   - User training and education\n   - Labeling and instructions for use\n   - Warning systems and alerts\n   - Contraindications and precautions\n\n**Risk Control Verification:**\n- Risk control effectiveness testing and validation\n- Verification protocol development and execution\n- Test results analysis and documentation\n- Risk control performance monitoring\n\n## Advanced Risk Management Applications\n\n### Software Risk Management (IEC 62304 Integration)\nIntegrate software lifecycle processes with risk management ensuring comprehensive software safety assessment.\n\n**Software Risk Management Process:**\n- **Software Safety Classification**: Class A, B, or C determination\n- **Software Hazard Analysis**: Software contribution to hazardous situations\n- **Software Risk Control**: Architecture and design safety measures\n- **Software Risk Management File**: Integration with overall risk management file\n\n### Cybersecurity Risk Management\nImplement cybersecurity risk management per FDA guidance and emerging international standards.\n\n**Cybersecurity Risk Framework:**\n1. **Cybersecurity Threat Modeling**\n   - Asset identification and vulnerability assessment\n   - Threat source analysis and attack vector evaluation\n   - Impact assessment on patient safety and device functionality\n   - Cybersecurity risk estimation and prioritization\n\n2. **Cybersecurity Controls Implementation**\n   - **Preventive Controls**: Authentication, authorization, encryption\n   - **Detective Controls**: Monitoring, logging, intrusion detection\n   - **Corrective Controls**: Incident response, recovery procedures\n   - **Compensating Controls**: Additional safeguards and mitigations\n\n### Human Factors and Use Error Risk Management\nIntegrate human factors engineering with risk management addressing use-related risks.\n\n**Use Error Risk Management:**\n- **Use-Related Risk Analysis**: Task analysis and use scenario evaluation\n- **Use Error Identification**: Critical task and use error analysis\n- **Use Error Risk Estimation**: Probability and severity assessment\n- **Use Error Risk Control**: Design controls and user interface optimization\n\n## Risk Management File Management\n\n### Risk Management Documentation\nMaintain comprehensive risk management files ensuring traceability and regulatory compliance.\n\n**Risk Management File Structure:**\n- **Risk Management Plan**: Objectives, scope, criteria, and responsibilities\n- **Risk Analysis Records**: Hazard identification, risk estimation, evaluation\n- **Risk Control Records**: Control measures, verification, validation results\n- **Production and Post-Production Information**: Surveillance data, updates\n- **Risk Management Report**: Summary of risk management activities and conclusions\n\n### Risk Management File Maintenance\nEnsure risk management files remain current throughout product lifecycle.\n\n**File Maintenance Protocol:**\n- **Design Change Impact Assessment**: Risk analysis updates for design changes\n- **Post-Market Information Integration**: Surveillance data incorporation\n- **Risk Control Effectiveness Review**: Ongoing effectiveness verification\n- **Periodic Risk Management Review**: Systematic file review and updates\n\n## Cross-functional Integration\n\n### Quality Management System Integration\nEnsure seamless integration of risk management with quality management system processes.\n\n**QMS-Risk Management Interface:**\n- **Design Controls**: Risk management integration in design and development\n- **Document Control**: Risk management file configuration management\n- **CAPA Integration**: Risk assessment for corrective and preventive actions\n- **Management Review**: Risk management performance reporting\n\n### Regulatory Submission Integration\nCoordinate risk management documentation with regulatory submission requirements.\n\n**Regulatory Integration Points:**\n- **FDA Submissions**: Risk analysis and risk management summaries\n- **EU MDR Technical Documentation**: Risk management file integration\n- **ISO 13485 Certification**: Risk management process compliance\n- **Post-Market Requirements**: Risk management in post-market surveillance\n\n### Clinical and Post-Market Integration\nIntegrate risk management with clinical evaluation and post-market surveillance activities.\n\n**Clinical-Risk Interface:**\n- **Clinical Risk Assessment**: Clinical data integration with risk analysis\n- **Clinical Investigation**: Risk management in clinical study design\n- **Post-Market Surveillance**: Risk signal detection and evaluation\n- **Clinical Evaluation Updates**: Risk-benefit analysis integration\n\n## Resources\n\n### scripts\u002F\n- `risk-assessment-automation.py`: Automated risk analysis workflow and documentation\n- `risk-matrix-calculator.py`: Risk estimation and evaluation automation\n- `risk-control-tracker.py`: Risk control implementation and verification tracking\n- `post-production-risk-monitor.py`: Post-market risk information analysis\n\n### references\u002F\n- `iso14971-implementation-guide.md`: Complete ISO 14971 implementation framework\n- `software-risk-management.md`: IEC 62304 integration with risk management\n- `cybersecurity-risk-framework.md`: Medical device cybersecurity risk management\n- `use-error-risk-analysis.md`: Human factors risk management methodologies\n- `risk-acceptability-criteria.md`: Risk acceptability frameworks and examples\n\n### assets\u002F\n- `risk-templates\u002F`: Risk management plan, risk analysis, and risk control templates\n- `risk-matrices\u002F`: Standardized risk estimation and evaluation matrices\n- `hazard-libraries\u002F`: Medical device hazard identification libraries\n- `training-materials\u002F`: Risk management training and competency programs\n","# Senior Risk Management Specialist\n\nExpert-level medical device risk management implementing ISO 14971 throughout the complete product lifecycle with comprehensive risk analysis, evaluation, control, and post-production monitoring capabilities.\n\n## Core Risk Management Competencies\n\n### 1. Risk Management Process Implementation (ISO 14971)\nEstablish and maintain comprehensive risk management processes integrated throughout the product development and lifecycle.\n\n**Risk Management Process Framework:**\n```\nISO 14971 RISK MANAGEMENT PROCESS\n├── Risk Management Planning\n│   ├── Risk management plan development\n│   ├── Risk acceptability criteria definition\n│   ├── Risk management team formation\n│   └── Risk management file establishment\n├── Risk Analysis\n│   ├── Intended use and reasonably foreseeable misuse\n│   ├── Hazard identification and analysis\n│   ├── Hazardous situation evaluation\n│   └── Risk estimation and documentation\n├── Risk Evaluation\n│   ├── Risk acceptability assessment\n│   ├── Risk benefit analysis\n│   ├── Risk control necessity determination\n│   └── Risk evaluation documentation\n├── Risk Control\n│   ├── Risk control option analysis\n│   ├── Risk control measure implementation\n│   ├── Residual risk evaluation\n│   └── Risk control effectiveness verification\n└── Production and Post-Production Information\n    ├── Information collection and analysis\n    ├── Risk management file updates\n    ├── Risk benefit analysis review\n    └── Risk control measure adjustment\n```\n\n### 2. Risk Analysis and Hazard Identification\nConduct systematic risk analysis identifying all potential hazards and hazardous situations throughout device lifecycle.\n\n**Risk Analysis Methodology:**\n1. **Intended Use and Context Analysis**\n   - Medical indication and patient population\n   - Use environment and conditions\n   - User characteristics and training\n   - **Decision Point**: Define scope of risk analysis\n\n2. **Hazard Identification Process**\n   - **For Hardware Components**: Mechanical, electrical, thermal, chemical hazards\n   - **For Software Components**: Software failure modes per IEC 62304\n   - **For Combination Products**: Drug-device interaction risks\n   - **For Connected Devices**: Cybersecurity and data privacy risks\n\n3. **Hazardous Situation Analysis**\n   - Sequence of events leading to hazardous situations\n   - Foreseeable misuse and use error scenarios\n   - Single fault condition analysis\n   - Multiple fault condition evaluation\n\n### 3. Risk Estimation and Evaluation\nApply systematic risk estimation methodologies ensuring consistent and defensible risk assessments.\n\n**Risk Estimation Framework:**\n- **Probability Assessment**: Statistical data, literature, expert judgment\n- **Severity Assessment**: Clinical outcome evaluation and classification\n- **Risk Level Determination**: Risk matrix application and documentation\n- **Risk Acceptability Evaluation**: Criteria application and justification\n\n**Risk Evaluation Decision Tree:**\n```\nRISK EVALUATION PROCESS\n├── Is Risk Acceptable? (per criteria)\n│   ├── YES → Document acceptable risk\n│   └── NO → Proceed to risk control\n├── Risk Control Implementation\n│   ├── Inherent safety by design\n│   ├── Protective measures\n│   └── Information for safety\n└── Residual Risk Evaluation\n    ├── Is residual risk acceptable?\n    ├── Risk benefit analysis\n    └── Final risk acceptability decision\n```\n\n### 4. Risk Control Implementation and Verification\nImplement comprehensive risk control measures following the hierarchy of risk control per ISO 14971.\n\n**Risk Control Hierarchy:**\n1. **Inherent Safety by Design**\n   - Design modifications eliminating hazards\n   - Fail-safe design implementation\n   - Redundancy and diversity application\n   - Human factors engineering integration\n\n2. **Protective Measures in the Medical Device**\n   - Alarms and alert systems\n   - Automatic shut-off mechanisms\n   - Physical barriers and shields\n   - Software safety functions\n\n3. **Information for Safety**\n   - User training and education\n   - Labeling and instructions for use\n   - Warning systems and alerts\n   - Contraindications and precautions\n\n**Risk Control Verification:**\n- Risk control effectiveness testing and validation\n- Verification protocol development and execution\n- Test results analysis and documentation\n- Risk control performance monitoring\n\n## Advanced Risk Management Applications\n\n### Software Risk Management (IEC 62304 Integration)\nIntegrate software lifecycle processes with risk management ensuring comprehensive software safety assessment.\n\n**Software Risk Management Process:**\n- **Software Safety Classification**: Class A, B, or C determination\n- **Software Hazard Analysis**: Software contribution to hazardous situations\n- **Software Risk Control**: Architecture and design safety measures\n- **Software Risk Management File**: Integration with overall risk management file\n\n### Cybersecurity Risk Management\nImplement cybersecurity risk management per FDA guidance and emerging international standards.\n\n**Cybersecurity Risk Framework:**\n1. **Cybersecurity Threat Modeling**\n   - Asset identification and vulnerability assessment\n   - Threat source analysis and attack vector evaluation\n   - Impact assessment on patient safety and device functionality\n   - Cybersecurity risk estimation and prioritization\n\n2. **Cybersecurity Controls Implementation**\n   - **Preventive Controls**: Authentication, authorization, encryption\n   - **Detective Controls**: Monitoring, logging, intrusion detection\n   - **Corrective Controls**: Incident response, recovery procedures\n   - **Compensating Controls**: Additional safeguards and mitigations\n\n### Human Factors and Use Error Risk Management\nIntegrate human factors engineering with risk management addressing use-related risks.\n\n**Use Error Risk Management:**\n- **Use-Related Risk Analysis**: Task analysis and use scenario evaluation\n- **Use Error Identification**: Critical task and use error analysis\n- **Use Error Risk Estimation**: Probability and severity assessment\n- **Use Error Risk Control**: Design controls and user interface optimization\n\n## Risk Management File Management\n\n### Risk Management Documentation\nMaintain comprehensive risk management files ensuring traceability and regulatory compliance.\n\n**Risk Management File Structure:**\n- **Risk Management Plan**: Objectives, scope, criteria, and responsibilities\n- **Risk Analysis Records**: Hazard identification, risk estimation, evaluation\n- **Risk Control Records**: Control measures, verification, validation results\n- **Production and Post-Production Information**: Surveillance data, updates\n- **Risk Management Report**: Summary of risk management activities and conclusions\n\n### Risk Management File Maintenance\nEnsure risk management files remain current throughout product lifecycle.\n\n**File Maintenance Protocol:**\n- **Design Change Impact Assessment**: Risk analysis updates for design changes\n- **Post-Market Information Integration**: Surveillance data incorporation\n- **Risk Control Effectiveness Review**: Ongoing effectiveness verification\n- **Periodic Risk Management Review**: Systematic file review and updates\n\n## Cross-functional Integration\n\n### Quality Management System Integration\nEnsure seamless integration of risk management with quality management system processes.\n\n**QMS-Risk Management Interface:**\n- **Design Controls**: Risk management integration in design and development\n- **Document Control**: Risk management file configuration management\n- **CAPA Integration**: Risk assessment for corrective and preventive actions\n- **Management Review**: Risk management performance reporting\n\n### Regulatory Submission Integration\nCoordinate risk management documentation with regulatory submission requirements.\n\n**Regulatory Integration Points:**\n- **FDA Submissions**: Risk analysis and risk management summaries\n- **EU MDR Technical Documentation**: Risk management file integration\n- **ISO 13485 Certification**: Risk management process compliance\n- **Post-Market Requirements**: Risk management in post-market surveillance\n\n### Clinical and Post-Market Integration\nIntegrate risk management with clinical evaluation and post-market surveillance activities.\n\n**Clinical-Risk Interface:**\n- **Clinical Risk Assessment**: Clinical data integration with risk analysis\n- **Clinical Investigation**: Risk management in clinical study design\n- **Post-Market Surveillance**: Risk signal detection and evaluation\n- **Clinical Evaluation Updates**: Risk-benefit analysis integration\n\n## Resources\n\n### scripts\u002F\n- `risk-assessment-automation.py`: Automated risk analysis workflow and documentation\n- `risk-matrix-calculator.py`: Risk estimation and evaluation automation\n- `risk-control-tracker.py`: Risk control implementation and verification tracking\n- `post-production-risk-monitor.py`: Post-market risk information analysis\n\n### references\u002F\n- `iso14971-implementation-guide.md`: Complete ISO 14971 implementation framework\n- `software-risk-management.md`: IEC 62304 integration with risk management\n- `cybersecurity-risk-framework.md`: Medical device cybersecurity risk management\n- `use-error-risk-analysis.md`: Human factors risk management methodologies\n- `risk-acceptability-criteria.md`: Risk acceptability frameworks and examples\n\n### assets\u002F\n- `risk-templates\u002F`: Risk management plan, risk analysis, and risk control templates\n- `risk-matrices\u002F`: Standardized risk estimation and evaluation matrices\n- `hazard-libraries\u002F`: Medical device hazard identification libraries\n- `training-materials\u002F`: Risk management training and competency programs\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist",3931,"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-14 06:14:46",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add davila7\u002Fclaude-code-templates --skill risk-management-specialist",{"tool":63,"command":64},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill risk-management-specialist",{"tool":66,"command":67},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill risk-management-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist\u002FSKILL.md",true,[71,77,83],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Fexample_asset.txt","ASSET","资产文件",865,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist\u002Fassets\u002Fexample_asset.txt",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi_reference.md","REFERENCE","参考文档",977,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist\u002Freferences\u002Fapi_reference.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fexample.py","SCRIPT","脚本",611,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Frisk-management-specialist\u002Fscripts\u002Fexample.py",[90,121,148,181,215,239],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":101,"publishedAt":42},"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",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[102,103,104,105,106,26,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":42},"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",[127],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[129,130,131,132,133,134,135,136,137,138,139,110,140,141,142,143,144,145,146,147],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":163,"publishedAt":42},"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",[154,157,158],{"categoryNo":155,"categoryName":156,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[164,165,166,167,168,169,170,26,171,172,173,174,175,176,177,109,178,179,110,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":42},"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":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000009","前端开发",[193,194,195,196,197,198,199,200,201,202,203,204,205,37,206,207,208,209,210,211,212,213,26,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":42},"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":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":190,"categoryName":191,"taxonomyType":99,"taxonomyTypeDesc":100},[227,228,229,230,231,194,232,203,204,233,234,235,236,26,237,112,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":42},"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":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":251,"categoryName":252,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000036","内容创作者",[254,255,256,257,258,259,260,261,196,262,37,140,263,264,265,266,267,176,268,110,269,24,270,271,272,118,273],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]