[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RWYAEFVB90T0MJHTAVE9X":3,"skill-same:01M77RWYAEFVB90T0MJHTAVE9X":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77RWYAEFVB90T0MJHTAVE9X","incident-report",null,"Create structured incident reports that document production incidents, impact, timeline, root cause, resolution, and follow-up actions.","panksooungman-dot\u002FAI-Web-Master","panksooungman-dot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263377190?v=4","01M77RQKZAR08JG1JSWP1MVXPV","cnbiz","01M77RQM00YBBJX4F6Y04HT8RN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Ftemplates\u002Fincident-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-report\ndescription: Create structured incident reports that document production incidents, impact, timeline, root cause, resolution, and follow-up actions.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: template\npriority: required\n---\n\n# Incident Report\n\n## Purpose\n\nThis skill creates comprehensive Incident Reports that document operational incidents, their business impact, response activities, root causes, and corrective actions.\n\nIncident reports should support learning, accountability, and continuous operational improvement.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Production incidents occur\n- Service outages happen\n- Security incidents are detected\n- Major defects impact users\n- Critical operational failures require documentation\n\n---\n\n# Objectives\n\nProduce incident reports that are:\n\n- Accurate\n- Timely\n- Objective\n- Actionable\n- Traceable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Incident Details\n- Monitoring Alerts\n- System Logs\n- Timeline\n- Response Actions\n- Stakeholder Updates\n\n---\n\n# Incident Report Structure\n\nGenerate the following sections:\n\n- Incident ID\n- Title\n- Severity\n- Status\n- Detection Time\n- Resolution Time\n- Duration\n- Systems Affected\n- Business Impact\n- Executive Summary\n- Timeline\n- Root Cause\n- Resolution\n- Corrective Actions\n- Preventive Actions\n- Lessons Learned\n- References\n\n---\n\n# Incident Details\n\nDocument:\n\n- Incident Description\n- Detection Method\n- Initial Symptoms\n- Scope\n- Impacted Services\n- Customer Impact\n\nUse factual, evidence-based descriptions.\n\n---\n\n# Timeline\n\nInclude:\n\n- Detection\n- Escalation\n- Investigation\n- Mitigation\n- Resolution\n- Recovery\n- Closure\n\nRecord timestamps whenever possible.\n\n---\n\n# Root Cause Analysis\n\nIdentify:\n\n- Immediate Cause\n- Contributing Factors\n- System Weaknesses\n- Human Factors\n- Process Gaps\n\nSupport conclusions with evidence.\n\n---\n\n# Resolution\n\nDescribe:\n\n- Mitigation Steps\n- Permanent Fix\n- Validation\n- Service Restoration\n- Communication\n\n---\n\n# Follow-up Actions\n\nAssign:\n\n- Action Item\n- Owner\n- Priority\n- Due Date\n- Status\n\nTrack completion until closure.\n\n---\n\n# Validation Checklist\n\nVerify:\n\n- Timeline complete\n- Root cause validated\n- Impact documented\n- Actions assigned\n- Lessons captured\n- Stakeholders informed\n\n---\n\n# Failure Conditions\n\nStop if:\n\n- Incident scope is unclear\n- Timeline is incomplete\n- Root cause is unknown\n- Evidence is insufficient\n- Action items are missing\n\n---\n\n# Outputs\n\nGenerate:\n\n- Incident Report\n- Timeline\n- Action Register\n- Executive Summary\n\n---\n\n# Rules\n\n- Be objective and evidence-based.\n- Avoid assigning blame.\n- Document facts chronologically.\n- Include corrective and preventive actions.\n- Maintain complete traceability.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- the incident is fully documented\n- root causes are understood\n- corrective actions are tracked\n- future incidents can be prevented\n\n---\n\n# Related Skills\n\n- runbook\n- postmortem\n- devops-engineer\n- security-engineer\n- technical-writer\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Incident Report\n\n## Purpose\n\nThis skill creates comprehensive Incident Reports that document operational incidents, their business impact, response activities, root causes, and corrective actions.\n\nIncident reports should support learning, accountability, and continuous operational improvement.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Production incidents occur\n- Service outages happen\n- Security incidents are detected\n- Major defects impact users\n- Critical operational failures require documentation\n\n---\n\n# Objectives\n\nProduce incident reports that are:\n\n- Accurate\n- Timely\n- Objective\n- Actionable\n- Traceable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Incident Details\n- Monitoring Alerts\n- System Logs\n- Timeline\n- Response Actions\n- Stakeholder Updates\n\n---\n\n# Incident Report Structure\n\nGenerate the following sections:\n\n- Incident ID\n- Title\n- Severity\n- Status\n- Detection Time\n- Resolution Time\n- Duration\n- Systems Affected\n- Business Impact\n- Executive Summary\n- Timeline\n- Root Cause\n- Resolution\n- Corrective Actions\n- Preventive Actions\n- Lessons Learned\n- References\n\n---\n\n# Incident Details\n\nDocument:\n\n- Incident Description\n- Detection Method\n- Initial Symptoms\n- Scope\n- Impacted Services\n- Customer Impact\n\nUse factual, evidence-based descriptions.\n\n---\n\n# Timeline\n\nInclude:\n\n- Detection\n- Escalation\n- Investigation\n- Mitigation\n- Resolution\n- Recovery\n- Closure\n\nRecord timestamps whenever possible.\n\n---\n\n# Root Cause Analysis\n\nIdentify:\n\n- Immediate Cause\n- Contributing Factors\n- System Weaknesses\n- Human Factors\n- Process Gaps\n\nSupport conclusions with evidence.\n\n---\n\n# Resolution\n\nDescribe:\n\n- Mitigation Steps\n- Permanent Fix\n- Validation\n- Service Restoration\n- Communication\n\n---\n\n# Follow-up Actions\n\nAssign:\n\n- Action Item\n- Owner\n- Priority\n- Due Date\n- Status\n\nTrack completion until closure.\n\n---\n\n# Validation Checklist\n\nVerify:\n\n- Timeline complete\n- Root cause validated\n- Impact documented\n- Actions assigned\n- Lessons captured\n- Stakeholders informed\n\n---\n\n# Failure Conditions\n\nStop if:\n\n- Incident scope is unclear\n- Timeline is incomplete\n- Root cause is unknown\n- Evidence is insufficient\n- Action items are missing\n\n---\n\n# Outputs\n\nGenerate:\n\n- Incident Report\n- Timeline\n- Action Register\n- Executive Summary\n\n---\n\n# Rules\n\n- Be objective and evidence-based.\n- Avoid assigning blame.\n- Document facts chronologically.\n- Include corrective and preventive actions.\n- Maintain complete traceability.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- the incident is fully documented\n- root causes are understood\n- corrective actions are tracked\n- future incidents can be prevented\n\n---\n\n# Related Skills\n\n- runbook\n- postmortem\n- devops-engineer\n- security-engineer\n- technical-writer\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |",{"name":5,"author":24,"license":15,"version":25,"category":26,"priority":27,"description":7},"AI Business OS","1.0.0","template","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Ftemplates\u002Fincident-report","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master","https:\u002F\u002Fai-web-master-cnbiz-web.vercel.app","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot","2026-11-14 20:43:00",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add panksooungman-dot\u002FAI-Web-Master --skill incident-report",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill incident-report",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill incident-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Ftemplates\u002Fincident-report\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77S2FHFC73NY664GYHNHGE8","rollback","Plan, validate, and execute safe rollback procedures to restore a stable system state when deployments introduce critical issues.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frollback\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77S2C5NW59NY9F939ECFVN0","release-note","Create clear, concise, and stakeholder-friendly release notes that communicate new features, improvements, fixes, breaking changes, and operational guidance for each release.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frelease-note\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77S28YMHR597AZF39CR0CNG","monitoring","Continuously observe application health, performance, reliability, and business metrics after deployment to detect issues early and support operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmonitoring\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77S26FGE7P6W5MDSBQ1WTPV","maintenance","Maintain, improve, and support production systems after release through continuous monitoring, issue resolution, updates, and operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmaintenance\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77S24CZGKFZEXXS3N0B067G","deployment","Plan, validate, and execute application deployments safely and consistently across environments while minimizing downtime and deployment risk.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fdeployment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77S21AG798PAEH5HEVYBYF7","changelog","Maintain a structured, accurate, and versioned changelog that records all notable changes made to the project across releases.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fchangelog\u002FSKILL.md",[],[]]