troubleshooting

Diagnose system and application failures using logs, metrics, and diagnostic decision trees.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/kunallimaye/lib-agents --skill troubleshooting-kunallimaye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/kunallimaye/lib-agents/tree/main/skills/troubleshooting
Command: npx skills add https://github.com/kunallimaye/lib-agents --skill troubleshooting-kunallimaye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnosing and resolving a wide range of system and application failures, reducing downtime and MTTR.

Core Features & Use Cases

  • Guided Investigation: Offers decision trees for common failure scenarios like container startup failures, CI/CD pipeline issues, and application crashes.
  • Metric Correlation: Helps correlate log errors with Prometheus metrics to pinpoint resource bottlenecks or performance degradation.
  • Diagnostic Tools: Integrates checks for network connectivity, DNS resolution, port conflicts, and disk space.
  • Use Case: When a critical service becomes unresponsive, use this Skill to analyze recent logs, check relevant Prometheus metrics for CPU/memory spikes, and verify network reachability to identify the root cause.

Quick Start

Use the troubleshooting skill to investigate why a container is not starting.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema
How do I troubleshoot why a container is failing to start?

Use this troubleshooting framework to diagnose container startup failures by analyzing system logs, checking network connectivity and port conflicts, and verifying disk space availability to isolate the root cause.

How do I correlate application log errors with Prometheus metrics to find performance bottlenecks?

Correlate application log errors with Prometheus metrics by running pre-built PromQL queries to pinpoint CPU or memory spikes that cause resource bottlenecks and performance degradation during an incident.

Can I use this skill to diagnose issues in CI/CD pipelines and Terraform deployments?

Yes, this skill supports diagnosing common failure modes in cloud build pipelines and Terraform deployments through systematic diagnostic decision trees designed for incident response and resolution.

What is the best way to investigate an unresponsive critical service?

Investigate an unresponsive service by analyzing recent application logs, checking Prometheus metrics for resource exhaustion, and verifying network reachability to identify the underlying system failure.

Do I need Prometheus set up to use the diagnostic decision trees?

No, Prometheus is not required to use the diagnostic decision trees for network connectivity, DNS resolution, and disk space checks, but pre-built PromQL queries are available for metric correlation if Prometheus metrics are present.