[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K5SJ0FT7KD82E7PJCGATX":3,"skill-same:01M71K5SJ0FT7KD82E7PJCGATX":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M71K5SJ0FT7KD82E7PJCGATX","risk-assessment",null,"Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.","mryfmo\u002Fdotfiles","mryfmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11512262?v=4","01M71K2RDZFFQKYGMHMS5Y9PW1","01M71K2REKJ0WS61PNFQPTYP5T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"assessment","risk assessment","risk","user","Wrong","when","go","assess","decision","trigger","risk register","vendor","process","project","operational","register","with","2026-11-10 10:12:30",false,"---\nname: risk-assessment\ndescription: Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.\n---\n\n# Risk Assessment\n\nSystematically identify, assess, and plan mitigations for operational risks.\n\n## Risk Assessment Matrix\n\n| | Low Impact | Medium Impact | High Impact |\n|---|-----------|---------------|-------------|\n| **High Likelihood** | Medium | High | Critical |\n| **Medium Likelihood** | Low | Medium | High |\n| **Low Likelihood** | Low | Low | Medium |\n\n## Risk Categories\n\n- **Operational**: Process failures, staffing gaps, system outages\n- **Financial**: Budget overruns, vendor cost increases, revenue impact\n- **Compliance**: Regulatory violations, audit findings, policy breaches\n- **Strategic**: Market changes, competitive threats, technology shifts\n- **Reputational**: Customer impact, public perception, partner relationships\n- **Security**: Data breaches, access control failures, third-party vulnerabilities\n\n## Risk Register Format\n\nFor each risk, document:\n- **Description**: What could happen\n- **Likelihood**: High \u002F Medium \u002F Low\n- **Impact**: High \u002F Medium \u002F Low\n- **Risk Level**: Critical \u002F High \u002F Medium \u002F Low\n- **Mitigation**: What we're doing to reduce likelihood or impact\n- **Owner**: Who is responsible for managing this risk\n- **Status**: Open \u002F Mitigated \u002F Accepted \u002F Closed\n\n## Output\n\nProduce a prioritized risk register with specific, actionable mitigations. Focus on risks that are controllable and material.\n","# Risk Assessment\n\nSystematically identify, assess, and plan mitigations for operational risks.\n\n## Risk Assessment Matrix\n\n| | Low Impact | Medium Impact | High Impact |\n|---|-----------|---------------|-------------|\n| **High Likelihood** | Medium | High | Critical |\n| **Medium Likelihood** | Low | Medium | High |\n| **Low Likelihood** | Low | Low | Medium |\n\n## Risk Categories\n\n- **Operational**: Process failures, staffing gaps, system outages\n- **Financial**: Budget overruns, vendor cost increases, revenue impact\n- **Compliance**: Regulatory violations, audit findings, policy breaches\n- **Strategic**: Market changes, competitive threats, technology shifts\n- **Reputational**: Customer impact, public perception, partner relationships\n- **Security**: Data breaches, access control failures, third-party vulnerabilities\n\n## Risk Register Format\n\nFor each risk, document:\n- **Description**: What could happen\n- **Likelihood**: High \u002F Medium \u002F Low\n- **Impact**: High \u002F Medium \u002F Low\n- **Risk Level**: Critical \u002F High \u002F Medium \u002F Low\n- **Mitigation**: What we're doing to reduce likelihood or impact\n- **Owner**: Who is responsible for managing this risk\n- **Status**: Open \u002F Mitigated \u002F Accepted \u002F Closed\n\n## Output\n\nProduce a prioritized risk register with specific, actionable mitigations. Focus on risks that are controllable and material.\n",{"name":5,"description":7},"main","af601a97567f1f07e9337cad899506f601f419f1","tests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmryfmo","2026-11-13 12:53:52",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add mryfmo\u002Fdotfiles --skill risk-assessment",{"tool":52,"command":53},"bunx","bunx skills add mryfmo\u002Fdotfiles --skill risk-assessment",{"tool":55,"command":56},"pnpm","pnpm dlx skills add mryfmo\u002Fdotfiles --skill risk-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",true,[],[61,67,73,102,122,144],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":35},"01M71K61D634ATEV8NWTGGWNGS","x","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":35},"01M71K605VRE3ABPN1MZHJNZ29","y","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fdocs\u002Fskills\u002Fy\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":35},"01M71K5Y3XX1PYZAWA7M5RG9VD","status-report","Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green\u002Fyellow\u002Fred status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fstatus-report\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[85,86,87,88,89,90,91,92,34,93,94,95,96,23,97,98,31,99,100,101],"status","report","status report","decisions","tracker","generate","leadership","narrative","health","project health","team","weekly","use","writing","for","green","attention",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":35},"01M71K5VJAHGE1NH22BGBXP693","runbook","Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frunbook\u002FSKILL.md",[],[104,109,110,111,112,113,30,32,114,115,23,116,117,97,98,118,119,99,120,121],"create","rollback","update","name","run","call","task","ops","Existing","knowledge","things","escalation","recurring",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":35},"01M71K5PYD2A2BDM6KMZ8F01SV","change-request","Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[129,130,131,99,132,20,133,134,34,135,136,137,138,139,23,97,140,141,142,143],"change request","request","change","planning","deployment","rollback plan","communications","stakeholder communications","review","analysis","rollout","impact","change management","impact analysis","system",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":155,"publishedAt":35},"01M71K5N31WQBH7FJFNBM3TCPY","testing-strategy","Design test strategies and test plans. Trigger with \"how should we test\", \"test strategy for\", \"write tests for\", \"test plan\", \"what tests do we need\", or when the user needs help with testing approaches, coverage, or test architecture.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[156,157,158,159,160,161,99,162,163,164,34,165,23,166,167,168,169,170,171,27],"strategy","testing","testing strategy","coverage","strategies","test plan","test strategies","plan","test","architecture","plans","design","tests","write tests","test strategy","do"]