[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEMJ5YBJ6FFYQ32DTTCZ9P":3,"skill-same:01M6AEMJ5YBJ6FFYQ32DTTCZ9P":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6AEMJ5YBJ6FFYQ32DTTCZ9P","it-operations",null,"Manages IT infrastructure, monitoring, incident response, and service reliability. Provides frameworks for ITIL service management, observability strategies, automation, backup\u002Frecovery, capacity planning, and operational excellence practices.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"it","it operations","operations","management","for","service","strategies","incident","frameworks","capacity planning","reliability","incident response","recovery","backup","monitoring","observability","planning","infrastructure","capacity","automation","2026-11-10 10:12:30",false,"---\nname: it-operations\ndescription: Manages IT infrastructure, monitoring, incident response, and service reliability. Provides frameworks for ITIL service management, observability strategies, automation, backup\u002Frecovery, capacity planning, and operational excellence practices.\n---\n\n# IT Operations Expert\n\nA comprehensive skill for managing IT infrastructure operations, ensuring service reliability, implementing monitoring and alerting strategies, managing incidents, and maintaining operational excellence through automation and best practices.\n\n## Core Principles\n\n### 1. Service Reliability First\n- **Proactive Monitoring**: Implement comprehensive observability before incidents occur\n- **Incident Management**: Structured response processes with clear escalation paths\n- **SLA\u002FSLO Management**: Define and maintain service level objectives aligned with business needs\n- **Continuous Improvement**: Learn from incidents through blameless post-mortems\n\n### 2. Automation Over Manual Processes\n- **Infrastructure as Code**: Manage infrastructure configuration through version-controlled code\n- **Runbook Automation**: Convert manual procedures into automated workflows\n- **Self-Healing Systems**: Implement automated remediation for common issues\n- **Configuration Management**: Maintain consistency across environments\n\n### 3. ITIL Service Management\n- **Service Strategy**: Align IT services with business objectives\n- **Service Design**: Design resilient, scalable services\n- **Service Transition**: Manage changes with minimal disruption\n- **Service Operation**: Deliver and support services effectively\n- **Continual Service Improvement**: Iteratively enhance service quality\n\n### 4. Operational Excellence\n- **Documentation**: Maintain current runbooks, procedures, and architecture diagrams\n- **Knowledge Management**: Build searchable knowledge bases from incident resolutions\n- **Capacity Planning**: Forecast and provision resources proactively\n- **Cost Optimization**: Balance performance requirements with infrastructure costs\n\n## Core Workflow\n\n### Infrastructure Operations Workflow\n\n```\n1. MONITORING & OBSERVABILITY\n   ├─ Define SLIs\u002FSLOs\u002FSLAs for critical services\n   ├─ Implement metrics collection (infrastructure, application, business)\n   ├─ Configure alerting with proper thresholds and escalation\n   ├─ Build dashboards for different audiences (ops, devs, executives)\n   └─ Establish on-call rotation and escalation procedures\n\n2. INCIDENT MANAGEMENT\n   ├─ Receive alert or user report\n   ├─ Assess severity and impact (P1\u002FP2\u002FP3\u002FP4)\n   ├─ Engage appropriate responders\n   ├─ Investigate and diagnose root cause\n   ├─ Implement fix or workaround\n   ├─ Communicate status to stakeholders\n   ├─ Document resolution in knowledge base\n   └─ Conduct post-incident review\n\n3. CHANGE MANAGEMENT\n   ├─ Submit change request with impact assessment\n   ├─ Review and approve through CAB (Change Advisory Board)\n   ├─ Schedule change window\n   ├─ Execute change with rollback plan ready\n   ├─ Validate success criteria\n   ├─ Document actual vs planned results\n   └─ Close change ticket\n\n4. CAPACITY PLANNING\n   ├─ Collect resource utilization trends\n   ├─ Analyze growth patterns\n   ├─ Forecast future requirements\n   ├─ Plan procurement or provisioning\n   ├─ Execute capacity additions\n   └─ Monitor effectiveness\n\n5. AUTOMATION & OPTIMIZATION\n   ├─ Identify repetitive manual tasks\n   ├─ Document current process\n   ├─ Design automated solution\n   ├─ Implement and test automation\n   ├─ Deploy to production\n   ├─ Measure time\u002Fcost savings\n   └─ Iterate and improve\n```\n\n## Decision Frameworks\n\n### Alert Configuration Decision Matrix\n\n| Scenario | Alert Type | Threshold | Response Time | Escalation |\n|----------|-----------|-----------|---------------|------------|\n| Service completely down | Page | Immediate | \u003C 5 min | Immediate to on-call |\n| Service degraded | Page | 2-3 failures | \u003C 15 min | After 15 min to on-call |\n| High resource usage | Warning | > 80% sustained | \u003C 1 hour | After 2 hours to team lead |\n| Approaching capacity | Info | > 70% trend | \u003C 24 hours | Weekly capacity review |\n| Configuration drift | Ticket | Any deviation | \u003C 7 days | Monthly review |\n\n### Incident Severity Classification\n\n**Priority 1 (Critical)**\n- Complete service outage affecting all users\n- Data loss or security breach\n- Financial impact > $10K\u002Fhour\n- Response: Immediate, 24\u002F7, all hands on deck\n\n**Priority 2 (High)**\n- Partial service outage affecting many users\n- Significant performance degradation\n- Financial impact $1K-$10K\u002Fhour\n- Response: \u003C 30 minutes during business hours\n\n**Priority 3 (Medium)**\n- Service degradation affecting some users\n- Non-critical functionality impaired\n- Workaround available\n- Response: \u003C 4 hours during business hours\n\n**Priority 4 (Low)**\n- Minor issues with minimal impact\n- Cosmetic problems\n- Enhancement requests\n- Response: Next business day\n\n### Change Management Risk Assessment\n\n```\nRisk Level = Impact × Likelihood × Complexity\n\nImpact (1-5):\n1 = Single user\n2 = Team\n3 = Department\n4 = Company-wide\n5 = Customer-facing\n\nLikelihood of Issues (1-5):\n1 = Routine, tested\n2 = Familiar, documented\n3 = Some uncertainty\n4 = New territory\n5 = Never done before\n\nComplexity (1-5):\n1 = Single component\n2 = Few components\n3 = Multiple systems\n4 = Cross-platform\n5 = Enterprise-wide\n\nRisk Score Interpretation:\n1-20: Standard change (pre-approved)\n21-50: Normal change (CAB review)\n51-75: High-risk change (extensive testing, senior approval)\n76-125: Emergency change only (executive approval)\n```\n\n### Monitoring Tool Selection\n\n| Requirement | Prometheus + Grafana | Datadog | New Relic | ELK Stack | Splunk |\n|-------------|---------------------|---------|-----------|-----------|---------|\n| Cost | Free (self-hosted) | $$$$ | $$$$ | Free-$$ | $$$$$ |\n| Metrics | Excellent | Excellent | Excellent | Good | Good |\n| Logs | Via Loki | Excellent | Excellent | Excellent | Excellent |\n| Traces | Via Tempo | Excellent | Excellent | Limited | Good |\n| Learning Curve | Steep | Moderate | Moderate | Steep | Steep |\n| Cloud-Native | Excellent | Excellent | Excellent | Good | Good |\n| On-Premises | Excellent | Good | Good | Excellent | Excellent |\n| APM | Via exporters | Excellent | Excellent | Limited | Good |\n\n## Common Operational Challenges\n\n### Challenge 1: Alert Fatigue\n**Problem**: Too many false positive alerts causing team burnout\n\n**Solution**:\n```yaml\nAlert Tuning Process:\n1. Measure baseline alert volume and false positive rate\n2. Categorize alerts by actionability:\n   - Actionable + Urgent = Keep as page\n   - Actionable + Not Urgent = Ticket\n   - Not Actionable = Remove or convert to dashboard metric\n3. Implement alert aggregation (group similar alerts)\n4. Add context to alerts (runbook links, relevant metrics)\n5. Regular review meetings (weekly) to tune thresholds\n6. Track metrics:\n   - MTTA (Mean Time to Acknowledge): \u003C 5 min target\n   - False Positive Rate: \u003C 20% target\n   - Alert Volume per Week: Trending down\n```\n\n### Challenge 2: Incident Documentation During Crisis\n**Problem**: Teams skip documentation during high-pressure incidents\n\n**Solution**:\n- Assign dedicated scribe role (not the incident commander)\n- Use incident management tools (PagerDuty, Opsgenie) with automatic timeline\n- Template-based incident reports with required fields\n- Post-incident review scheduled automatically (within 48 hours)\n- Gamify documentation (track and recognize thorough documentation)\n\n### Challenge 3: Knowledge Silos\n**Problem**: Critical knowledge trapped in individual team members' heads\n\n**Solution**:\n```yaml\nKnowledge Transfer Strategy:\n- Pair Programming\u002FShadowing: 20% of sprint capacity\n- Runbook Requirements: Every system must have runbook\n- Lunch & Learn Sessions: Weekly 30-min knowledge sharing\n- Cross-Training Matrix: Track who knows what, identify gaps\n- On-Call Rotation: Everyone rotates to spread knowledge\n- Post-Incident Reviews: Mandatory team sharing\n- Documentation Sprints: Quarterly focus on doc completion\n```\n\n### Challenge 4: Balancing Stability vs Innovation\n**Problem**: Operations team resists change to maintain stability\n\n**Solution**:\n- Implement change windows (planned maintenance periods)\n- Use blue-green or canary deployments for lower risk\n- Establish \"innovation time\" (Google 20% time model)\n- Create sandbox environments for experimentation\n- Measure and reward both stability AND improvement metrics\n- Include \"toil reduction\" as OKR target\n\n## Key Metrics & KPIs\n\n### Service Reliability Metrics\n```yaml\nAvailability:\n  Formula: (Total Time - Downtime) \u002F Total Time × 100\n  Target: 99.9% (43.8 min\u002Fmonth downtime)\n  Measurement: Per service, monthly\n\nMTTR (Mean Time to Recovery):\n  Formula: Sum of recovery times \u002F Number of incidents\n  Target: \u003C 30 minutes for P1, \u003C 4 hours for P2\n  Measurement: Per severity level, monthly\n\nMTBF (Mean Time Between Failures):\n  Formula: Total operational time \u002F Number of failures\n  Target: > 720 hours (30 days)\n  Measurement: Per service, quarterly\n\nMTTA (Mean Time to Acknowledge):\n  Formula: Sum of acknowledgment times \u002F Number of alerts\n  Target: \u003C 5 minutes for pages\n  Measurement: Per on-call engineer, weekly\n\nChange Success Rate:\n  Formula: Successful changes \u002F Total changes × 100\n  Target: > 95%\n  Measurement: Monthly\n\nIncident Recurrence Rate:\n  Formula: Repeat incidents \u002F Total incidents × 100\n  Target: \u003C 10%\n  Measurement: Quarterly (same root cause within 90 days)\n```\n\n### Operational Efficiency Metrics\n```yaml\nToil Percentage:\n  Definition: Time spent on manual, repetitive tasks\n  Target: \u003C 30% of team capacity\n  Measurement: Weekly time tracking\n\nAutomation Coverage:\n  Formula: Automated tasks \u002F Total repetitive tasks × 100\n  Target: > 70%\n  Measurement: Quarterly audit\n\nOn-Call Load:\n  Formula: Alerts per on-call shift\n  Target: \u003C 5 actionable alerts per shift\n  Measurement: Per engineer, weekly\n\nRunbook Coverage:\n  Formula: Services with runbooks \u002F Total services × 100\n  Target: 100%\n  Measurement: Monthly audit\n\nKnowledge Base Utilization:\n  Formula: Incidents resolved via KB \u002F Total incidents × 100\n  Target: > 40%\n  Measurement: Monthly\n```\n\n## Integration Points\n\n### With Development Teams\n- Participate in design reviews for operational requirements\n- Provide deployment automation and CI\u002FCD pipeline support\n- Share monitoring and logging requirements\n- Collaborate on incident response and post-mortems\n- Joint ownership of SLOs and error budgets\n\n### With Security Teams\n- Implement security monitoring and alerting\n- Manage access controls and authentication systems\n- Coordinate vulnerability patching and remediation\n- Conduct security incident response\n- Maintain compliance with security policies\n\n### With Business Stakeholders\n- Report on service availability and performance\n- Communicate planned maintenance windows\n- Provide capacity planning forecasts\n- Translate technical metrics to business impact\n- Participate in business continuity planning\n\n## Best Practices\n\n### 1. Blameless Post-Mortems\n```markdown\nPost-Incident Review Template:\n- Incident Summary (what happened, when, impact)\n- Timeline of Events (detailed chronology)\n- Root Cause Analysis (5 Whys or Fishbone)\n- What Went Well (strengths during response)\n- What Could Be Improved (opportunities)\n- Action Items (with owners and due dates)\n- Lessons Learned (shareable insights)\n\nRules:\n- No blame or punishment\n- Focus on systems and processes, not people\n- Everyone can speak freely\n- Action items must be tracked to completion\n```\n\n### 2. Runbook Standards\n```yaml\nRunbook Contents:\n  - Service Overview: Purpose, dependencies, architecture\n  - SLIs\u002FSLOs\u002FSLAs: Defined thresholds and targets\n  - Common Issues: Symptoms, causes, solutions\n  - Troubleshooting Steps: Step-by-step procedures\n  - Escalation Paths: Who to contact and when\n  - Useful Commands: Copy-paste ready commands\n  - Dashboard Links: Direct links to relevant dashboards\n  - Recent Changes: Link to change log\n  - Contact Information: Team, product owner, SMEs\n\nMaintenance:\n  - Review quarterly or after major incidents\n  - Test procedures during low-traffic periods\n  - Update after every significant change\n  - Track usage metrics (page views, helpfulness ratings)\n```\n\n### 3. On-Call Best Practices\n```yaml\nOn-Call Preparation:\n  - Laptop with VPN access\n  - Mobile device with notification apps\n  - Contact list (escalation paths)\n  - Access to all critical systems\n  - Runbooks bookmarked\n  - Backup on-call identified\n\nDuring On-Call:\n  - Acknowledge alerts within 5 minutes\n  - Update incident status regularly\n  - Follow escalation procedures\n  - Document all actions in incident ticket\n  - Handoff clearly to next on-call\n\nPost On-Call:\n  - Complete incident reports\n  - Submit toil reduction tickets\n  - Provide feedback on runbooks\n  - Update on-call documentation\n```\n\n### 4. Change Management Discipline\n```yaml\nStandard Change Process:\n  1. Create change request (RFC)\n  2. Document:\n     - What: Specific changes being made\n     - Why: Business justification\n     - When: Proposed date\u002Ftime\n     - Who: Change implementer and approver\n     - How: Step-by-step procedure\n     - Risk: Assessment and mitigation\n     - Rollback: Detailed rollback plan\n     - Testing: Validation steps\n  3. Submit for CAB review (7 days advance notice)\n  4. Implement during approved window\n  5. Validate success criteria\n  6. Close change with actual results\n  7. Post-implementation review if issues occurred\n\nEmergency Change Process:\n  - Executive approval required\n  - Implement with heightened monitoring\n  - Full team notification\n  - Complete documentation within 24 hours\n  - Mandatory post-change review\n```\n\n## Reference Files\n\nFor detailed technical guidance, see:\n- [reference\u002Fmonitoring.md](reference\u002Fmonitoring.md) - Observability, metrics, alerting, and dashboard design\n- [reference\u002Fincident-management.md](reference\u002Fincident-management.md) - Incident response, root cause analysis, post-mortems\n- [reference\u002Finfrastructure.md](reference\u002Finfrastructure.md) - Server management, network operations, capacity planning\n- [reference\u002Fautomation.md](reference\u002Fautomation.md) - Scripting, configuration management, orchestration tools\n- [reference\u002Fbackup-recovery.md](reference\u002Fbackup-recovery.md) - Backup strategies, disaster recovery, business continuity\n\n## Getting Started\n\n1. **For New Infrastructure**: Start with [reference\u002Finfrastructure.md](reference\u002Finfrastructure.md) for setup guidance\n2. **For Monitoring Setup**: Review [reference\u002Fmonitoring.md](reference\u002Fmonitoring.md) for observability strategy\n3. **For Incident Response**: See [reference\u002Fincident-management.md](reference\u002Fincident-management.md) for procedures\n4. **For Automation Projects**: Check [reference\u002Fautomation.md](reference\u002Fautomation.md) for tooling recommendations\n5. **For DR Planning**: Consult [reference\u002Fbackup-recovery.md](reference\u002Fbackup-recovery.md) for recovery strategies\n","# IT Operations Expert\n\nA comprehensive skill for managing IT infrastructure operations, ensuring service reliability, implementing monitoring and alerting strategies, managing incidents, and maintaining operational excellence through automation and best practices.\n\n## Core Principles\n\n### 1. Service Reliability First\n- **Proactive Monitoring**: Implement comprehensive observability before incidents occur\n- **Incident Management**: Structured response processes with clear escalation paths\n- **SLA\u002FSLO Management**: Define and maintain service level objectives aligned with business needs\n- **Continuous Improvement**: Learn from incidents through blameless post-mortems\n\n### 2. Automation Over Manual Processes\n- **Infrastructure as Code**: Manage infrastructure configuration through version-controlled code\n- **Runbook Automation**: Convert manual procedures into automated workflows\n- **Self-Healing Systems**: Implement automated remediation for common issues\n- **Configuration Management**: Maintain consistency across environments\n\n### 3. ITIL Service Management\n- **Service Strategy**: Align IT services with business objectives\n- **Service Design**: Design resilient, scalable services\n- **Service Transition**: Manage changes with minimal disruption\n- **Service Operation**: Deliver and support services effectively\n- **Continual Service Improvement**: Iteratively enhance service quality\n\n### 4. Operational Excellence\n- **Documentation**: Maintain current runbooks, procedures, and architecture diagrams\n- **Knowledge Management**: Build searchable knowledge bases from incident resolutions\n- **Capacity Planning**: Forecast and provision resources proactively\n- **Cost Optimization**: Balance performance requirements with infrastructure costs\n\n## Core Workflow\n\n### Infrastructure Operations Workflow\n\n```\n1. MONITORING & OBSERVABILITY\n   ├─ Define SLIs\u002FSLOs\u002FSLAs for critical services\n   ├─ Implement metrics collection (infrastructure, application, business)\n   ├─ Configure alerting with proper thresholds and escalation\n   ├─ Build dashboards for different audiences (ops, devs, executives)\n   └─ Establish on-call rotation and escalation procedures\n\n2. INCIDENT MANAGEMENT\n   ├─ Receive alert or user report\n   ├─ Assess severity and impact (P1\u002FP2\u002FP3\u002FP4)\n   ├─ Engage appropriate responders\n   ├─ Investigate and diagnose root cause\n   ├─ Implement fix or workaround\n   ├─ Communicate status to stakeholders\n   ├─ Document resolution in knowledge base\n   └─ Conduct post-incident review\n\n3. CHANGE MANAGEMENT\n   ├─ Submit change request with impact assessment\n   ├─ Review and approve through CAB (Change Advisory Board)\n   ├─ Schedule change window\n   ├─ Execute change with rollback plan ready\n   ├─ Validate success criteria\n   ├─ Document actual vs planned results\n   └─ Close change ticket\n\n4. CAPACITY PLANNING\n   ├─ Collect resource utilization trends\n   ├─ Analyze growth patterns\n   ├─ Forecast future requirements\n   ├─ Plan procurement or provisioning\n   ├─ Execute capacity additions\n   └─ Monitor effectiveness\n\n5. AUTOMATION & OPTIMIZATION\n   ├─ Identify repetitive manual tasks\n   ├─ Document current process\n   ├─ Design automated solution\n   ├─ Implement and test automation\n   ├─ Deploy to production\n   ├─ Measure time\u002Fcost savings\n   └─ Iterate and improve\n```\n\n## Decision Frameworks\n\n### Alert Configuration Decision Matrix\n\n| Scenario | Alert Type | Threshold | Response Time | Escalation |\n|----------|-----------|-----------|---------------|------------|\n| Service completely down | Page | Immediate | \u003C 5 min | Immediate to on-call |\n| Service degraded | Page | 2-3 failures | \u003C 15 min | After 15 min to on-call |\n| High resource usage | Warning | > 80% sustained | \u003C 1 hour | After 2 hours to team lead |\n| Approaching capacity | Info | > 70% trend | \u003C 24 hours | Weekly capacity review |\n| Configuration drift | Ticket | Any deviation | \u003C 7 days | Monthly review |\n\n### Incident Severity Classification\n\n**Priority 1 (Critical)**\n- Complete service outage affecting all users\n- Data loss or security breach\n- Financial impact > $10K\u002Fhour\n- Response: Immediate, 24\u002F7, all hands on deck\n\n**Priority 2 (High)**\n- Partial service outage affecting many users\n- Significant performance degradation\n- Financial impact $1K-$10K\u002Fhour\n- Response: \u003C 30 minutes during business hours\n\n**Priority 3 (Medium)**\n- Service degradation affecting some users\n- Non-critical functionality impaired\n- Workaround available\n- Response: \u003C 4 hours during business hours\n\n**Priority 4 (Low)**\n- Minor issues with minimal impact\n- Cosmetic problems\n- Enhancement requests\n- Response: Next business day\n\n### Change Management Risk Assessment\n\n```\nRisk Level = Impact × Likelihood × Complexity\n\nImpact (1-5):\n1 = Single user\n2 = Team\n3 = Department\n4 = Company-wide\n5 = Customer-facing\n\nLikelihood of Issues (1-5):\n1 = Routine, tested\n2 = Familiar, documented\n3 = Some uncertainty\n4 = New territory\n5 = Never done before\n\nComplexity (1-5):\n1 = Single component\n2 = Few components\n3 = Multiple systems\n4 = Cross-platform\n5 = Enterprise-wide\n\nRisk Score Interpretation:\n1-20: Standard change (pre-approved)\n21-50: Normal change (CAB review)\n51-75: High-risk change (extensive testing, senior approval)\n76-125: Emergency change only (executive approval)\n```\n\n### Monitoring Tool Selection\n\n| Requirement | Prometheus + Grafana | Datadog | New Relic | ELK Stack | Splunk |\n|-------------|---------------------|---------|-----------|-----------|---------|\n| Cost | Free (self-hosted) | $$$$ | $$$$ | Free-$$ | $$$$$ |\n| Metrics | Excellent | Excellent | Excellent | Good | Good |\n| Logs | Via Loki | Excellent | Excellent | Excellent | Excellent |\n| Traces | Via Tempo | Excellent | Excellent | Limited | Good |\n| Learning Curve | Steep | Moderate | Moderate | Steep | Steep |\n| Cloud-Native | Excellent | Excellent | Excellent | Good | Good |\n| On-Premises | Excellent | Good | Good | Excellent | Excellent |\n| APM | Via exporters | Excellent | Excellent | Limited | Good |\n\n## Common Operational Challenges\n\n### Challenge 1: Alert Fatigue\n**Problem**: Too many false positive alerts causing team burnout\n\n**Solution**:\n```yaml\nAlert Tuning Process:\n1. Measure baseline alert volume and false positive rate\n2. Categorize alerts by actionability:\n   - Actionable + Urgent = Keep as page\n   - Actionable + Not Urgent = Ticket\n   - Not Actionable = Remove or convert to dashboard metric\n3. Implement alert aggregation (group similar alerts)\n4. Add context to alerts (runbook links, relevant metrics)\n5. Regular review meetings (weekly) to tune thresholds\n6. Track metrics:\n   - MTTA (Mean Time to Acknowledge): \u003C 5 min target\n   - False Positive Rate: \u003C 20% target\n   - Alert Volume per Week: Trending down\n```\n\n### Challenge 2: Incident Documentation During Crisis\n**Problem**: Teams skip documentation during high-pressure incidents\n\n**Solution**:\n- Assign dedicated scribe role (not the incident commander)\n- Use incident management tools (PagerDuty, Opsgenie) with automatic timeline\n- Template-based incident reports with required fields\n- Post-incident review scheduled automatically (within 48 hours)\n- Gamify documentation (track and recognize thorough documentation)\n\n### Challenge 3: Knowledge Silos\n**Problem**: Critical knowledge trapped in individual team members' heads\n\n**Solution**:\n```yaml\nKnowledge Transfer Strategy:\n- Pair Programming\u002FShadowing: 20% of sprint capacity\n- Runbook Requirements: Every system must have runbook\n- Lunch & Learn Sessions: Weekly 30-min knowledge sharing\n- Cross-Training Matrix: Track who knows what, identify gaps\n- On-Call Rotation: Everyone rotates to spread knowledge\n- Post-Incident Reviews: Mandatory team sharing\n- Documentation Sprints: Quarterly focus on doc completion\n```\n\n### Challenge 4: Balancing Stability vs Innovation\n**Problem**: Operations team resists change to maintain stability\n\n**Solution**:\n- Implement change windows (planned maintenance periods)\n- Use blue-green or canary deployments for lower risk\n- Establish \"innovation time\" (Google 20% time model)\n- Create sandbox environments for experimentation\n- Measure and reward both stability AND improvement metrics\n- Include \"toil reduction\" as OKR target\n\n## Key Metrics & KPIs\n\n### Service Reliability Metrics\n```yaml\nAvailability:\n  Formula: (Total Time - Downtime) \u002F Total Time × 100\n  Target: 99.9% (43.8 min\u002Fmonth downtime)\n  Measurement: Per service, monthly\n\nMTTR (Mean Time to Recovery):\n  Formula: Sum of recovery times \u002F Number of incidents\n  Target: \u003C 30 minutes for P1, \u003C 4 hours for P2\n  Measurement: Per severity level, monthly\n\nMTBF (Mean Time Between Failures):\n  Formula: Total operational time \u002F Number of failures\n  Target: > 720 hours (30 days)\n  Measurement: Per service, quarterly\n\nMTTA (Mean Time to Acknowledge):\n  Formula: Sum of acknowledgment times \u002F Number of alerts\n  Target: \u003C 5 minutes for pages\n  Measurement: Per on-call engineer, weekly\n\nChange Success Rate:\n  Formula: Successful changes \u002F Total changes × 100\n  Target: > 95%\n  Measurement: Monthly\n\nIncident Recurrence Rate:\n  Formula: Repeat incidents \u002F Total incidents × 100\n  Target: \u003C 10%\n  Measurement: Quarterly (same root cause within 90 days)\n```\n\n### Operational Efficiency Metrics\n```yaml\nToil Percentage:\n  Definition: Time spent on manual, repetitive tasks\n  Target: \u003C 30% of team capacity\n  Measurement: Weekly time tracking\n\nAutomation Coverage:\n  Formula: Automated tasks \u002F Total repetitive tasks × 100\n  Target: > 70%\n  Measurement: Quarterly audit\n\nOn-Call Load:\n  Formula: Alerts per on-call shift\n  Target: \u003C 5 actionable alerts per shift\n  Measurement: Per engineer, weekly\n\nRunbook Coverage:\n  Formula: Services with runbooks \u002F Total services × 100\n  Target: 100%\n  Measurement: Monthly audit\n\nKnowledge Base Utilization:\n  Formula: Incidents resolved via KB \u002F Total incidents × 100\n  Target: > 40%\n  Measurement: Monthly\n```\n\n## Integration Points\n\n### With Development Teams\n- Participate in design reviews for operational requirements\n- Provide deployment automation and CI\u002FCD pipeline support\n- Share monitoring and logging requirements\n- Collaborate on incident response and post-mortems\n- Joint ownership of SLOs and error budgets\n\n### With Security Teams\n- Implement security monitoring and alerting\n- Manage access controls and authentication systems\n- Coordinate vulnerability patching and remediation\n- Conduct security incident response\n- Maintain compliance with security policies\n\n### With Business Stakeholders\n- Report on service availability and performance\n- Communicate planned maintenance windows\n- Provide capacity planning forecasts\n- Translate technical metrics to business impact\n- Participate in business continuity planning\n\n## Best Practices\n\n### 1. Blameless Post-Mortems\n```markdown\nPost-Incident Review Template:\n- Incident Summary (what happened, when, impact)\n- Timeline of Events (detailed chronology)\n- Root Cause Analysis (5 Whys or Fishbone)\n- What Went Well (strengths during response)\n- What Could Be Improved (opportunities)\n- Action Items (with owners and due dates)\n- Lessons Learned (shareable insights)\n\nRules:\n- No blame or punishment\n- Focus on systems and processes, not people\n- Everyone can speak freely\n- Action items must be tracked to completion\n```\n\n### 2. Runbook Standards\n```yaml\nRunbook Contents:\n  - Service Overview: Purpose, dependencies, architecture\n  - SLIs\u002FSLOs\u002FSLAs: Defined thresholds and targets\n  - Common Issues: Symptoms, causes, solutions\n  - Troubleshooting Steps: Step-by-step procedures\n  - Escalation Paths: Who to contact and when\n  - Useful Commands: Copy-paste ready commands\n  - Dashboard Links: Direct links to relevant dashboards\n  - Recent Changes: Link to change log\n  - Contact Information: Team, product owner, SMEs\n\nMaintenance:\n  - Review quarterly or after major incidents\n  - Test procedures during low-traffic periods\n  - Update after every significant change\n  - Track usage metrics (page views, helpfulness ratings)\n```\n\n### 3. On-Call Best Practices\n```yaml\nOn-Call Preparation:\n  - Laptop with VPN access\n  - Mobile device with notification apps\n  - Contact list (escalation paths)\n  - Access to all critical systems\n  - Runbooks bookmarked\n  - Backup on-call identified\n\nDuring On-Call:\n  - Acknowledge alerts within 5 minutes\n  - Update incident status regularly\n  - Follow escalation procedures\n  - Document all actions in incident ticket\n  - Handoff clearly to next on-call\n\nPost On-Call:\n  - Complete incident reports\n  - Submit toil reduction tickets\n  - Provide feedback on runbooks\n  - Update on-call documentation\n```\n\n### 4. Change Management Discipline\n```yaml\nStandard Change Process:\n  1. Create change request (RFC)\n  2. Document:\n     - What: Specific changes being made\n     - Why: Business justification\n     - When: Proposed date\u002Ftime\n     - Who: Change implementer and approver\n     - How: Step-by-step procedure\n     - Risk: Assessment and mitigation\n     - Rollback: Detailed rollback plan\n     - Testing: Validation steps\n  3. Submit for CAB review (7 days advance notice)\n  4. Implement during approved window\n  5. Validate success criteria\n  6. Close change with actual results\n  7. Post-implementation review if issues occurred\n\nEmergency Change Process:\n  - Executive approval required\n  - Implement with heightened monitoring\n  - Full team notification\n  - Complete documentation within 24 hours\n  - Mandatory post-change review\n```\n\n## Reference Files\n\nFor detailed technical guidance, see:\n- [reference\u002Fmonitoring.md](reference\u002Fmonitoring.md) - Observability, metrics, alerting, and dashboard design\n- [reference\u002Fincident-management.md](reference\u002Fincident-management.md) - Incident response, root cause analysis, post-mortems\n- [reference\u002Finfrastructure.md](reference\u002Finfrastructure.md) - Server management, network operations, capacity planning\n- [reference\u002Fautomation.md](reference\u002Fautomation.md) - Scripting, configuration management, orchestration tools\n- [reference\u002Fbackup-recovery.md](reference\u002Fbackup-recovery.md) - Backup strategies, disaster recovery, business continuity\n\n## Getting Started\n\n1. **For New Infrastructure**: Start with [reference\u002Finfrastructure.md](reference\u002Finfrastructure.md) for setup guidance\n2. **For Monitoring Setup**: Review [reference\u002Fmonitoring.md](reference\u002Fmonitoring.md) for observability strategy\n3. **For Incident Response**: See [reference\u002Fincident-management.md](reference\u002Fincident-management.md) for procedures\n4. **For Automation Projects**: Check [reference\u002Fautomation.md](reference\u002Fautomation.md) for tooling recommendations\n5. **For DR Planning**: Consult [reference\u002Fbackup-recovery.md](reference\u002Fbackup-recovery.md) for recovery strategies\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations",3963,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-15 01:32:48",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add davila7\u002Fclaude-code-templates --skill it-operations",{"tool":65,"command":66},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill it-operations",{"tool":68,"command":69},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill it-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002FSKILL.md",true,[73,79,83,87,91,95],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"README.md","REFERENCE","参考文档",9738,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002FREADME.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"reference\u002Fautomation.md",40343,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002Freference\u002Fautomation.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fbackup-recovery.md",26233,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002Freference\u002Fbackup-recovery.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"reference\u002Fincident-management.md",46805,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002Freference\u002Fincident-management.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"reference\u002Finfrastructure.md",45301,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002Freference\u002Finfrastructure.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"reference\u002Fmonitoring.md",38260,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fit-operations\u002Freference\u002Fmonitoring.md",[100,127,154,187,222,246],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":44},"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",[106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,28,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":44},"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",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,136,137,138,139,140,141,142,143,144,145,116,146,147,148,149,150,151,152,153],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":169,"publishedAt":44},"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",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[170,171,172,173,174,175,176,28,177,178,179,180,181,182,183,115,184,185,116,186],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":44},"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",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,28,221],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":233,"publishedAt":44},"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",[229,232],{"categoryNo":230,"categoryName":231,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},[234,235,236,237,238,200,239,209,210,240,241,242,243,28,244,118,245],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":250,"sourceHtmlUrl":251,"categories":252,"keywords":260,"publishedAt":44},"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",[253,256,257],{"categoryNo":254,"categoryName":255,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":258,"categoryName":259,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000036","内容创作者",[261,262,263,264,265,266,267,268,202,269,212,146,270,271,272,273,274,182,275,116,276,277,278,279,280,124,281],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]