[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G1DN1AX9AEECY3QXP10DTT":3,"skill-same:01M6G1DN1AX9AEECY3QXP10DTT":150},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M6G1DN1AX9AEECY3QXP10DTT","incident-commander",null,"oabdelmaksoud\u002FAgention","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D8A4TE76V3DCSH3D94VG1V",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002FSKILL.md",[],[18,19,20],"incident commander","incident","commander","2026-11-10 10:12:30",false,"# Incident Commander Skill\n\n**Category:** Engineering Team  \n**Tier:** POWERFUL  \n**Author:** Claude Skills Team  \n**Version:** 1.0.0  \n**Last Updated:** February 2026\n\n## Overview\n\nThe Incident Commander skill provides a comprehensive incident response framework for managing technology incidents from detection through resolution and post-incident review. This skill implements battle-tested practices from SRE and DevOps teams at scale, providing structured tools for severity classification, timeline reconstruction, and thorough post-incident analysis.\n\n## Key Features\n\n- **Automated Severity Classification** - Intelligent incident triage based on impact and urgency metrics\n- **Timeline Reconstruction** - Transform scattered logs and events into coherent incident narratives\n- **Post-Incident Review Generation** - Structured PIRs with multiple RCA frameworks\n- **Communication Templates** - Pre-built templates for stakeholder updates and escalations\n- **Runbook Integration** - Generate actionable runbooks from incident patterns\n\n## Skills Included\n\n### Core Tools\n\n1. **Incident Classifier** (`incident_classifier.py`)\n   - Analyzes incident descriptions and outputs severity levels\n   - Recommends response teams and initial actions\n   - Generates communication templates based on severity\n\n2. **Timeline Reconstructor** (`timeline_reconstructor.py`)\n   - Processes timestamped events from multiple sources\n   - Reconstructs chronological incident timeline\n   - Identifies gaps and provides duration analysis\n\n3. **PIR Generator** (`pir_generator.py`)\n   - Creates comprehensive Post-Incident Review documents\n   - Applies multiple RCA frameworks (5 Whys, Fishbone, Timeline)\n   - Generates actionable follow-up items\n\n## Incident Response Framework\n\n### Severity Classification System\n\n#### SEV1 - Critical Outage\n**Definition:** Complete service failure affecting all users or critical business functions\n\n**Characteristics:**\n- Customer-facing services completely unavailable\n- Data loss or corruption affecting users\n- Security breaches with customer data exposure\n- Revenue-generating systems down\n- SLA violations with financial penalties\n\n**Response Requirements:**\n- Immediate escalation to on-call engineer\n- Incident Commander assigned within 5 minutes\n- Executive notification within 15 minutes\n- Public status page update within 15 minutes\n- War room established\n- All hands on deck if needed\n\n**Communication Frequency:** Every 15 minutes until resolution\n\n#### SEV2 - Major Impact\n**Definition:** Significant degradation affecting subset of users or non-critical functions\n\n**Characteristics:**\n- Partial service degradation (>25% of users affected)\n- Performance issues causing user frustration\n- Non-critical features unavailable\n- Internal tools impacting productivity\n- Data inconsistencies not affecting user experience\n\n**Response Requirements:**\n- On-call engineer response within 15 minutes\n- Incident Commander assigned within 30 minutes\n- Status page update within 30 minutes\n- Stakeholder notification within 1 hour\n- Regular team updates\n\n**Communication Frequency:** Every 30 minutes during active response\n\n#### SEV3 - Minor Impact\n**Definition:** Limited impact with workarounds available\n\n**Characteristics:**\n- Single feature or component affected\n- \u003C25% of users impacted\n- Workarounds available\n- Performance degradation not significantly impacting UX\n- Non-urgent monitoring alerts\n\n**Response Requirements:**\n- Response within 2 hours during business hours\n- Next business day response acceptable outside hours\n- Internal team notification\n- Optional status page update\n\n**Communication Frequency:** At key milestones only\n\n#### SEV4 - Low Impact\n**Definition:** Minimal impact, cosmetic issues, or planned maintenance\n\n**Characteristics:**\n- Cosmetic bugs\n- Documentation issues\n- Logging or monitoring gaps\n- Performance issues with no user impact\n- Development\u002Ftest environment issues\n\n**Response Requirements:**\n- Response within 1-2 business days\n- Standard ticket\u002Fissue tracking\n- No special escalation required\n\n**Communication Frequency:** Standard development cycle updates\n\n### Incident Commander Role\n\n#### Primary Responsibilities\n\n1. **Command and Control**\n   - Own the incident response process\n   - Make critical decisions about resource allocation\n   - Coordinate between technical teams and stakeholders\n   - Maintain situational awareness across all response streams\n\n2. **Communication Hub**\n   - Provide regular updates to stakeholders\n   - Manage external communications (status pages, customer notifications)\n   - Facilitate effective communication between response teams\n   - Shield responders from external distractions\n\n3. **Process Management**\n   - Ensure proper incident tracking and documentation\n   - Drive toward resolution while maintaining quality\n   - Coordinate handoffs between team members\n   - Plan and execute rollback strategies if needed\n\n4. **Post-Incident Leadership**\n   - Ensure thorough post-incident reviews are conducted\n   - Drive implementation of preventive measures\n   - Share learnings with broader organization\n\n#### Decision-Making Framework\n\n**Emergency Decisions (SEV1\u002F2):**\n- Incident Commander has full authority\n- Bias toward action over analysis\n- Document decisions for later review\n- Consult subject matter experts but don't get blocked\n\n**Resource Allocation:**\n- Can pull in any necessary team members\n- Authority to escalate to senior leadership\n- Can approve emergency spend for external resources\n- Make call on communication channels and timing\n\n**Technical Decisions:**\n- Lean on technical leads for implementation details\n- Make final calls on trade-offs between speed and risk\n- Approve rollback vs. fix-forward strategies\n- Coordinate testing and validation approaches\n\n### Communication Templates\n\n#### Initial Incident Notification (SEV1\u002F2)\n\n```\nSubject: [SEV{severity}] {Service Name} - {Brief Description}\n\nIncident Details:\n- Start Time: {timestamp}\n- Severity: SEV{level}\n- Impact: {user impact description}\n- Current Status: {investigating\u002Fmitigating\u002Fresolved}\n\nTechnical Details:\n- Affected Services: {service list}\n- Symptoms: {what users are experiencing}\n- Initial Assessment: {suspected root cause if known}\n\nResponse Team:\n- Incident Commander: {name}\n- Technical Lead: {name}\n- SMEs Engaged: {list}\n\nNext Update: {timestamp}\nStatus Page: {link}\nWar Room: {bridge\u002Fchat link}\n\n---\n{Incident Commander Name}\n{Contact Information}\n```\n\n#### Executive Summary (SEV1)\n\n```\nSubject: URGENT - Customer-Impacting Outage - {Service Name}\n\nExecutive Summary:\n{2-3 sentence description of customer impact and business implications}\n\nKey Metrics:\n- Time to Detection: {X minutes}\n- Time to Engagement: {X minutes} \n- Estimated Customer Impact: {number\u002Fpercentage}\n- Current Status: {status}\n- ETA to Resolution: {time or \"investigating\"}\n\nLeadership Actions Required:\n- [ ] Customer communication approval\n- [ ] PR\u002FCommunications coordination  \n- [ ] Resource allocation decisions\n- [ ] External vendor engagement\n\nIncident Commander: {name} ({contact})\nNext Update: {time}\n\n---\nThis is an automated alert from our incident response system.\n```\n\n#### Customer Communication Template\n\n```\nWe are currently experiencing {brief description of issue} affecting {scope of impact}. \n\nOur engineering team was alerted at {time} and is actively working to resolve the issue. We will provide updates every {frequency} until resolved.\n\nWhat we know:\n- {factual statement of impact}\n- {factual statement of scope}\n- {brief status of response}\n\nWhat we're doing:\n- {primary response action}\n- {secondary response action}\n\nWorkaround (if available):\n{workaround steps or \"No workaround currently available\"}\n\nWe apologize for the inconvenience and will share more information as it becomes available.\n\nNext update: {time}\nStatus page: {link}\n```\n\n### Stakeholder Management\n\n#### Stakeholder Classification\n\n**Internal Stakeholders:**\n- **Engineering Leadership** - Technical decisions and resource allocation\n- **Product Management** - Customer impact assessment and feature implications\n- **Customer Support** - User communication and support ticket management\n- **Sales\u002FAccount Management** - Customer relationship management for enterprise clients\n- **Executive Team** - Business impact decisions and external communication approval\n- **Legal\u002FCompliance** - Regulatory reporting and liability assessment\n\n**External Stakeholders:**\n- **Customers** - Service availability and impact communication\n- **Partners** - API availability and integration impacts\n- **Vendors** - Third-party service dependencies and support escalation\n- **Regulators** - Compliance reporting for regulated industries\n- **Public\u002FMedia** - Transparency for public-facing outages\n\n#### Communication Cadence by Stakeholder\n\n| Stakeholder | SEV1 | SEV2 | SEV3 | SEV4 |\n|-------------|------|------|------|------|\n| Engineering Leadership | Real-time | 30min | 4hrs | Daily |\n| Executive Team | 15min | 1hr | EOD | Weekly |\n| Customer Support | Real-time | 30min | 2hrs | As needed |\n| Customers | 15min | 1hr | Optional | None |\n| Partners | 30min | 2hrs | Optional | None |\n\n### Runbook Generation Framework\n\n#### Dynamic Runbook Components\n\n1. **Detection Playbooks**\n   - Monitoring alert definitions\n   - Triage decision trees\n   - Escalation trigger points\n   - Initial response actions\n\n2. **Response Playbooks**\n   - Step-by-step mitigation procedures\n   - Rollback instructions\n   - Validation checkpoints\n   - Communication checkpoints\n\n3. **Recovery Playbooks**\n   - Service restoration procedures\n   - Data consistency checks\n   - Performance validation\n   - User notification processes\n\n#### Runbook Template Structure\n\n```markdown\n# {Service\u002FComponent} Incident Response Runbook\n\n## Quick Reference\n- **Severity Indicators:** {list of conditions for each severity level}\n- **Key Contacts:** {on-call rotations and escalation paths}\n- **Critical Commands:** {list of emergency commands with descriptions}\n\n## Detection\n### Monitoring Alerts\n- {Alert name}: {description and thresholds}\n- {Alert name}: {description and thresholds}\n\n### Manual Detection Signs\n- {Symptom}: {what to look for and where}\n- {Symptom}: {what to look for and where}\n\n## Initial Response (0-15 minutes)\n1. **Assess Severity**\n   - [ ] Check {primary metric}\n   - [ ] Verify {secondary indicator}\n   - [ ] Classify as SEV{level} based on {criteria}\n\n2. **Establish Command**\n   - [ ] Page Incident Commander if SEV1\u002F2\n   - [ ] Create incident tracking ticket\n   - [ ] Join war room: {link\u002Fbridge info}\n\n3. **Initial Investigation**\n   - [ ] Check recent deployments: {deployment log location}\n   - [ ] Review error logs: {log location and queries}\n   - [ ] Verify dependencies: {dependency check commands}\n\n## Mitigation Strategies\n### Strategy 1: {Name}\n**Use when:** {conditions}\n**Steps:**\n1. {detailed step with commands}\n2. {detailed step with expected outcomes}\n3. {validation step}\n\n**Rollback Plan:**\n1. {rollback step}\n2. {verification step}\n\n### Strategy 2: {Name}\n{similar structure}\n\n## Recovery and Validation\n1. **Service Restoration**\n   - [ ] {restoration step}\n   - [ ] Wait for {metric} to return to normal\n   - [ ] Validate end-to-end functionality\n\n2. **Communication**\n   - [ ] Update status page\n   - [ ] Notify stakeholders\n   - [ ] Schedule PIR\n\n## Common Pitfalls\n- **{Pitfall}:** {description and how to avoid}\n- **{Pitfall}:** {description and how to avoid}\n\n## Reference Information\n- **Architecture Diagram:** {link}\n- **Monitoring Dashboard:** {link}\n- **Related Runbooks:** {links to dependent service runbooks}\n```\n\n### Post-Incident Review (PIR) Framework\n\n#### PIR Timeline and Ownership\n\n**Timeline:**\n- **24 hours:** Initial PIR draft completed by Incident Commander\n- **3 business days:** Final PIR published with all stakeholder input\n- **1 week:** Action items assigned with owners and due dates\n- **4 weeks:** Follow-up review on action item progress\n\n**Roles:**\n- **PIR Owner:** Incident Commander (can delegate writing but owns completion)\n- **Technical Contributors:** All engineers involved in response\n- **Review Committee:** Engineering leadership, affected product teams\n- **Action Item Owners:** Assigned based on expertise and capacity\n\n#### Root Cause Analysis Frameworks\n\n#### 1. Five Whys Method\n\nThe Five Whys technique involves asking \"why\" repeatedly to drill down to root causes:\n\n**Example Application:**\n- **Problem:** Database became unresponsive during peak traffic\n- **Why 1:** Why did the database become unresponsive? → Connection pool was exhausted\n- **Why 2:** Why was the connection pool exhausted? → Application was creating more connections than usual\n- **Why 3:** Why was the application creating more connections? → New feature wasn't properly connection pooling\n- **Why 4:** Why wasn't the feature properly connection pooling? → Code review missed this pattern\n- **Why 5:** Why did code review miss this? → No automated checks for connection pooling patterns\n\n**Best Practices:**\n- Ask \"why\" at least 3 times, often need 5+ iterations\n- Focus on process failures, not individual blame\n- Each \"why\" should point to a actionable system improvement\n- Consider multiple root cause paths, not just one linear chain\n\n#### 2. Fishbone (Ishikawa) Diagram\n\nSystematic analysis across multiple categories of potential causes:\n\n**Categories:**\n- **People:** Training, experience, communication, handoffs\n- **Process:** Procedures, change management, review processes\n- **Technology:** Architecture, tooling, monitoring, automation\n- **Environment:** Infrastructure, dependencies, external factors\n\n**Application Method:**\n1. State the problem clearly at the \"head\" of the fishbone\n2. For each category, brainstorm potential contributing factors\n3. For each factor, ask what caused that factor (sub-causes)\n4. Identify the factors most likely to be root causes\n5. Validate root causes with evidence from the incident\n\n#### 3. Timeline Analysis\n\nReconstruct the incident chronologically to identify decision points and missed opportunities:\n\n**Timeline Elements:**\n- **Detection:** When was the issue first observable? When was it first detected?\n- **Notification:** How quickly were the right people informed?\n- **Response:** What actions were taken and how effective were they?\n- **Communication:** When were stakeholders updated?\n- **Resolution:** What finally resolved the issue?\n\n**Analysis Questions:**\n- Where were there delays and what caused them?\n- What decisions would we make differently with perfect information?\n- Where did communication break down?\n- What automation could have detected\u002Fresolved faster?\n\n### Escalation Paths\n\n#### Technical Escalation\n\n**Level 1:** On-call engineer\n- **Responsibility:** Initial response and common issue resolution\n- **Escalation Trigger:** Issue not resolved within SLA timeframe\n- **Timeframe:** 15 minutes (SEV1), 30 minutes (SEV2)\n\n**Level 2:** Senior engineer\u002FTeam lead\n- **Responsibility:** Complex technical issues requiring deeper expertise\n- **Escalation Trigger:** Level 1 requests help or timeout occurs\n- **Timeframe:** 30 minutes (SEV1), 1 hour (SEV2)\n\n**Level 3:** Engineering Manager\u002FStaff Engineer\n- **Responsibility:** Cross-team coordination and architectural decisions\n- **Escalation Trigger:** Issue spans multiple systems or teams\n- **Timeframe:** 45 minutes (SEV1), 2 hours (SEV2)\n\n**Level 4:** Director of Engineering\u002FCTO\n- **Responsibility:** Resource allocation and business impact decisions\n- **Escalation Trigger:** Extended outage or significant business impact\n- **Timeframe:** 1 hour (SEV1), 4 hours (SEV2)\n\n#### Business Escalation\n\n**Customer Impact Assessment:**\n- **High:** Revenue loss, SLA breaches, customer churn risk\n- **Medium:** User experience degradation, support ticket volume\n- **Low:** Internal tools, development impact only\n\n**Escalation Matrix:**\n\n| Severity | Duration | Business Escalation |\n|----------|----------|-------------------|\n| SEV1 | Immediate | VP Engineering |\n| SEV1 | 30 minutes | CTO + Customer Success VP |\n| SEV1 | 1 hour | CEO + Full Executive Team |\n| SEV2 | 2 hours | VP Engineering |\n| SEV2 | 4 hours | CTO |\n| SEV3 | 1 business day | Engineering Manager |\n\n### Status Page Management\n\n#### Update Principles\n\n1. **Transparency:** Provide factual information without speculation\n2. **Timeliness:** Update within committed timeframes\n3. **Clarity:** Use customer-friendly language, avoid technical jargon\n4. **Completeness:** Include impact scope, status, and next update time\n\n#### Status Categories\n\n- **Operational:** All systems functioning normally\n- **Degraded Performance:** Some users may experience slowness\n- **Partial Outage:** Subset of features unavailable\n- **Major Outage:** Service unavailable for most\u002Fall users\n- **Under Maintenance:** Planned maintenance window\n\n#### Update Template\n\n```\n{Timestamp} - {Status Category}\n\n{Brief description of current state}\n\nImpact: {who is affected and how}\nCause: {root cause if known, \"under investigation\" if not}\nResolution: {what's being done to fix it}\n\nNext update: {specific time}\n\nWe apologize for any inconvenience this may cause.\n```\n\n### Action Item Framework\n\n#### Action Item Categories\n\n1. **Immediate Fixes**\n   - Critical bugs discovered during incident\n   - Security vulnerabilities exposed\n   - Data integrity issues\n\n2. **Process Improvements**\n   - Communication gaps\n   - Escalation procedure updates\n   - Runbook additions\u002Fupdates\n\n3. **Technical Debt**\n   - Architecture improvements\n   - Monitoring enhancements\n   - Automation opportunities\n\n4. **Organizational Changes**\n   - Team structure adjustments\n   - Training requirements\n   - Tool\u002Fplatform investments\n\n#### Action Item Template\n\n```\n**Title:** {Concise description of the action}\n**Priority:** {Critical\u002FHigh\u002FMedium\u002FLow}\n**Category:** {Fix\u002FProcess\u002FTechnical\u002FOrganizational}\n**Owner:** {Assigned person}\n**Due Date:** {Specific date}\n**Success Criteria:** {How will we know this is complete}\n**Dependencies:** {What needs to happen first}\n**Related PIRs:** {Links to other incidents this addresses}\n\n**Description:**\n{Detailed description of what needs to be done and why}\n\n**Implementation Plan:**\n1. {Step 1}\n2. {Step 2}\n3. {Validation step}\n\n**Progress Updates:**\n- {Date}: {Progress update}\n- {Date}: {Progress update}\n```\n\n## Usage Examples\n\n### Example 1: Database Connection Pool Exhaustion\n\n```bash\n# Classify the incident\necho '{\"description\": \"Users reporting 500 errors, database connections timing out\", \"affected_users\": \"80%\", \"business_impact\": \"high\"}' | python scripts\u002Fincident_classifier.py\n\n# Reconstruct timeline from logs\npython scripts\u002Ftimeline_reconstructor.py --input assets\u002Fdb_incident_events.json --output timeline.md\n\n# Generate PIR after resolution\npython scripts\u002Fpir_generator.py --incident assets\u002Fdb_incident_data.json --timeline timeline.md --output pir.md\n```\n\n### Example 2: API Rate Limiting Incident\n\n```bash\n# Quick classification from stdin\necho \"API rate limits causing customer API calls to fail\" | python scripts\u002Fincident_classifier.py --format text\n\n# Build timeline from multiple sources\npython scripts\u002Ftimeline_reconstructor.py --input assets\u002Fapi_incident_logs.json --detect-phases --gap-analysis\n\n# Generate comprehensive PIR\npython scripts\u002Fpir_generator.py --incident assets\u002Fapi_incident_summary.json --rca-method fishbone --action-items\n```\n\n## Best Practices\n\n### During Incident Response\n\n1. **Maintain Calm Leadership**\n   - Stay composed under pressure\n   - Make decisive calls with incomplete information\n   - Communicate confidence while acknowledging uncertainty\n\n2. **Document Everything**\n   - All actions taken and their outcomes\n   - Decision rationale, especially for controversial calls\n   - Timeline of events as they happen\n\n3. **Effective Communication**\n   - Use clear, jargon-free language\n   - Provide regular updates even when there's no new information\n   - Manage stakeholder expectations proactively\n\n4. **Technical Excellence**\n   - Prefer rollbacks to risky fixes under pressure\n   - Validate fixes before declaring resolution\n   - Plan for secondary failures and cascading effects\n\n### Post-Incident\n\n1. **Blameless Culture**\n   - Focus on system failures, not individual mistakes\n   - Encourage honest reporting of what went wrong\n   - Celebrate learning and improvement opportunities\n\n2. **Action Item Discipline**\n   - Assign specific owners and due dates\n   - Track progress publicly\n   - Prioritize based on risk and effort\n\n3. **Knowledge Sharing**\n   - Share PIRs broadly within the organization\n   - Update runbooks based on lessons learned\n   - Conduct training sessions for common failure modes\n\n4. **Continuous Improvement**\n   - Look for patterns across multiple incidents\n   - Invest in tooling and automation\n   - Regularly review and update processes\n\n## Integration with Existing Tools\n\n### Monitoring and Alerting\n- PagerDuty\u002FOpsgenie integration for escalation\n- Datadog\u002FGrafana for metrics and dashboards\n- ELK\u002FSplunk for log analysis and correlation\n\n### Communication Platforms\n- Slack\u002FTeams for war room coordination\n- Zoom\u002FMeet for video bridges\n- Status page providers (Statuspage.io, etc.)\n\n### Documentation Systems\n- Confluence\u002FNotion for PIR storage\n- GitHub\u002FGitLab for runbook version control\n- JIRA\u002FLinear for action item tracking\n\n### Change Management\n- CI\u002FCD pipeline integration\n- Deployment tracking systems\n- Feature flag platforms for quick rollbacks\n\n## Conclusion\n\nThe Incident Commander skill provides a comprehensive framework for managing incidents from detection through post-incident review. By implementing structured processes, clear communication templates, and thorough analysis tools, teams can improve their incident response capabilities and build more resilient systems.\n\nThe key to successful incident management is preparation, practice, and continuous learning. Use this framework as a starting point, but adapt it to your organization's specific needs, culture, and technical environment.\n\nRemember: The goal isn't to prevent all incidents (which is impossible), but to detect them quickly, respond effectively, communicate clearly, and learn continuously.",{},"main","a318f48de3c5718e8ea2e9f6fae7790e8a759e85","upstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:23:03",{"source":7,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add oabdelmaksoud\u002FAgention --skill incident-commander",{"tool":40,"command":41},"bunx","bunx skills add oabdelmaksoud\u002FAgention --skill incident-commander",{"tool":43,"command":44},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FAgention --skill incident-commander","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,88,92,96,100,104,108,112,116,120,124,130,134,138,142,146],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"assets\u002Fincident_report_template.md","ASSET","资产文件",4649,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fincident_report_template.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Frunbook_template.md",9709,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Frunbook_template.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Fsample_incident_classification.json",610,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsample_incident_classification.json",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Fsample_incident_data.json",11233,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsample_incident_data.json",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Fsample_incident_pir_data.json",3253,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsample_incident_pir_data.json",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Fsample_timeline_events.json",7766,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsample_timeline_events.json",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Fsimple_incident.json",161,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsimple_incident.json",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Fsimple_timeline_events.json",734,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fassets\u002Fsimple_timeline_events.json",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"expected_outputs\u002Fincident_classification_text_output.txt","REFERENCE","参考文档",1557,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fexpected_outputs\u002Fincident_classification_text_output.txt",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"expected_outputs\u002Fpir_markdown_output.md",3302,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fexpected_outputs\u002Fpir_markdown_output.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"expected_outputs\u002Fsimple_incident_classification.txt",1373,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fexpected_outputs\u002Fsimple_incident_classification.txt",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"expected_outputs\u002Ftimeline_reconstruction_text_output.txt",3235,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fexpected_outputs\u002Ftimeline_reconstruction_text_output.txt",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"README.md",7541,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002FREADME.md",{"path":105,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fcommunication_templates.md",14928,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Freferences\u002Fcommunication_templates.md",{"path":109,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fincident_severity_matrix.md",8952,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Freferences\u002Fincident_severity_matrix.md",{"path":113,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fincident-response-framework.md",26142,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Freferences\u002Fincident-response-framework.md",{"path":117,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Frca_frameworks_guide.md",15641,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Freferences\u002Frca_frameworks_guide.md",{"path":121,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fsla-management-guide.md",23537,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Freferences\u002Fsla-management-guide.md",{"path":125,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fincident_classifier.py","SCRIPT","脚本",34889,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Fincident_classifier.py",{"path":131,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":132,"sourceHtmlUrl":133},"scripts\u002Fincident_timeline_builder.py",29373,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Fincident_timeline_builder.py",{"path":135,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":136,"sourceHtmlUrl":137},"scripts\u002Fpir_generator.py",69566,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Fpir_generator.py",{"path":139,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fpostmortem_generator.py",38855,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Fpostmortem_generator.py",{"path":143,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fseverity_classifier.py",44280,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Fseverity_classifier.py",{"path":147,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":148,"sourceHtmlUrl":149},"scripts\u002Ftimeline_reconstructor.py",40229,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fengineering-team\u002Fincident-commander\u002Fscripts\u002Ftimeline_reconstructor.py",[151,175,189,222,248,268],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":162,"publishedAt":21},"01M6G2QFCBNBYAJF2KTK85G9A6","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[163,164,165,166,167,168,169,170,171,172,173,174],"translate","doc","visa doc translate","bilingual","with","english","application","PDF","translation","documents","create","images",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":21},"01M6G2QB09TSK6BY4ME5X20EVQ","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[182,183,184,185,186,187,188],"verification","loop","verification loop","sessions","code","claude code sessions","system",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":206,"publishedAt":21},"01M6G2Q6V2F7G03VAAF27FXPJR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":199,"categoryName":200,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":202,"categoryName":203,"taxonomyType":204,"taxonomyTypeDesc":205},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[207,208,209,210,211,212,213,214,215,186,216,217,218,219,167,220,221],"workflow","tdd","tdd workflow","use","unit","coverage","refactoring","e2e","integration","development","e2e tests","tests","driven","test","writing",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":21},"01M6G2Q359YJRWAR2PFCEQAXF3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,167],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":252,"categories":253,"keywords":255,"publishedAt":21},"01M6G2PY8B2FWZTWPZ84H83Y7C","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[254],{"categoryNo":196,"categoryName":197,"taxonomyType":160,"taxonomyTypeDesc":161},[256,257,258,259,186,260,261,262,263,188,264,265,266,267],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection","mock",{"skillNo":269,"name":270,"nameZh":6,"description":271,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":272,"categories":273,"keywords":274,"publishedAt":21},"01M6G2PSCN2GXV9FFZDRRRWVB6","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FAgention\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[275,276,277,258,278,25,279],"concurrency","swift concurrency","swift concurrency 6 2","default","types"]