skills.rest
lloydchang
lloydchangCOMMUNITY
Explore all skills by this author →
GitHub

track-incidents

Identifies and correlates multi-cloud incident history across AWS, Azure, GCP, and on-prem environments.

2|1|Updated Mar 11, 2026
Search Tags:#automation#monitoring#governance#audit-logging#pattern-analysis#incident#multicloud
One-click install
npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill track-incidents
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: track-incidents
Source: https://github.com/lloydchang/agentic-reconciliation-engine/tree/main/core/ai/skills/track-incidents
Command: npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill track-incidents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and analyzes incident history across cloud environments for pattern identification and learning. Use when tracking incidents, analyzing patterns, or implementing incident learning.

Core Features & Use Cases

  • Multi-cloud incident history tracking across AWS, Azure, GCP, and on-prem environments
  • Pattern detection, trend analysis, and learning from historical incidents
  • Auditable incident logs with cross-provider context and governance

Quick Start

Initialize and run the incident history collection across your cloud accounts with a single command.

Frequently Asked Questions about track-incidents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track incident history across multiple cloud providers?▼

Multi-cloud incident tracking is done by correlating incident history across AWS, Azure, GCP, and on-prem environments to reveal cross-provider patterns and root causes for governance.

What is multi-cloud incident pattern analysis and how does it work?▼

Multi-cloud incident pattern analysis identifies trends by correlating historical incident logs across cloud environments, applying learning-driven automation to discover root causes.

How do I set up multi-cloud incident tracking and what prerequisites do I need?▼

Setting up multi-cloud incident tracking requires Python 3.8+, cloud CLI tools, and access to centralized monitoring systems to collect and analyze cross-provider incident history.

Can I use this incident tracking approach for on-premises resources and cloud environments?▼

Yes, incident tracking applies to both on-premises resources and cloud providers, maintaining auditable incident logs with cross-provider context for unified governance and analysis.

What is the best way to analyze incident trends for learning-driven automation?▼

Analyzing incident trends for learning-driven automation involves maintaining auditable incident logs across cloud environments to identify patterns and implement incident learning.

Why does multi-cloud incident correlation require centralized monitoring access?▼

Multi-cloud incident correlation requires centralized monitoring access to aggregate cross-provider data needed to accurately identify patterns and root causes across diverse environments.

Related Skills

Explore More Data & Analytics Skills→
lloydchanglloydchang
2

diagnose-network

Diagnose network issues across AWS, Azure, GCP, and on-prem clusters.

Community
Advanced
ylxaiylxai
2

RootCauseAnalysis

Analyze incident reports to identify root causes and contributing factors.

Community
Advanced
lloydchanglloydchang
2

execute-troubleshooting-playbook

Automate multi-cloud troubleshooting playbooks across AWS, Azure, GCP, and on-prem environments.

Community
Advanced
ekremmkasapekremmkasap

multi-cloud-architecture

Plan cloud-agnostic architectures across AWS, Azure, and GCP with a decision framework.

Community
Advanced