troubleshooting-config-items

Diagnose health issues of infrastructure and application configuration items.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-config-items
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-config-items
Source: https://github.com/flanksource/claude-code-plugin/tree/main/skills/config_item
Command: npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-config-items

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users struggle to quickly pinpoint the root cause of unhealthy infrastructure or application components. This Skill automates the diagnostic process, saving time and reducing the complexity of sifting through logs and configurations.

Core Features & Use Cases

  • Health Diagnosis: Automatically identify and explain why a configuration item (e.g., Kubernetes Pod, AWS EC2) is unhealthy.
  • Change Analysis: Pinpoint recent configuration changes that might have caused an issue, showing what changed and when.
  • Relationship Mapping: Understand how different infrastructure components relate to each other (parents, children, dependencies) to trace issues through complex systems.
  • Use Case: A Kubernetes deployment is unhealthy. Use this Skill to automatically find the failing pod, analyze its logs, check recent image updates, and suggest a fix.

Quick Start

Troubleshoot the unhealthy config item named 'my-app-deployment' in Mission Control.

Frequently Asked Questions about troubleshooting-config-items

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

FAQPage Schema
How do I diagnose why my Kubernetes pod or AWS instance is unhealthy?

Diagnose unhealthy infrastructure by automatically inspecting health status, configuration details, and recent changes to pinpoint root causes. The Skill analyzes pod logs, image updates, and configuration diffs to identify what caused degradation or failure across Kubernetes and AWS resources.

Can I trace configuration changes that broke my infrastructure?

Yes. Change analysis compares current and historical configurations to show exactly what changed and when, helping you identify recent modifications to pods, deployments, EC2 instances, or other components that triggered failures or errors.

How do I understand relationships between infrastructure components?

Relationship mapping reveals parent, child, and dependency connections across your infrastructure. Navigate hierarchies to trace issues through related Kubernetes services, deployments, pods, or AWS resources and understand how one component's failure cascades.

What infrastructure platforms does this support for troubleshooting?

Troubleshooting works across Kubernetes pods, deployments, and services; AWS EC2 instances and volumes; Azure VMs; and other infrastructure components. The Skill applies to any unhealthy or failing resource in your environment.

Do I need to manually inspect logs and configs to find the root cause?

No. The Skill automates diagnosis by gathering health status, configuration details, error messages, and change history into evidence-based conclusions, eliminating manual sifting through logs and reducing troubleshooting time.

Can I use this to troubleshoot application configuration issues, not just infrastructure?

Yes. Beyond infrastructure, the Skill diagnoses health issues in application configuration items, enabling root-cause identification when applications are degraded or error-prone across your infrastructure stack.