skills.rest
TheBushidoCollective
TheBushidoCollectiveOFFICIAL
Explore all skills by this author →
WebsiteGitHub

runbooks-troubleshooting-guides

Diagnose operational issues using structured troubleshooting runbooks.

187|20|Updated Nov 20, 2025
Search Tags:#troubleshooting#diagnosis#runbooks#ops
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill runbooks-troubleshooting-guides
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runbooks-troubleshooting-guides
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-runbooks/skills/troubleshooting-guides
Command: npx skills add https://github.com/TheBushidoCollective/han --skill runbooks-troubleshooting-guides

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a framework for diagnosing and resolving operational issues.

Core Features & Use Cases

  • Troubleshooting framework: 5-step method.
  • Checklists & quick checks: Common causes and steps.
  • Resolution & prevention: Document fixes and prevention.

Quick Start

Create a basic runbook for a common outage scenario.

Frequently Asked Questions about runbooks-troubleshooting-guides

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

FAQPage Schema
How do I diagnose an API outage or service failure?▼

Diagnose API outages using structured troubleshooting runbooks that systematically collect data, form hypotheses, test them iteratively, and document findings. The 5-step method guides you through identifying root causes across Kubernetes, microservices, databases, and external dependencies.

What's the best way to troubleshoot latency spikes in a microservices architecture?▼

Apply hypothesis-driven troubleshooting to isolate latency sources across your cloud-native stack. Runbooks provide checklists for common causes—database queries, service dependencies, Kubernetes resource constraints—enabling systematic diagnosis and iterative fixes.

Can I use runbooks to diagnose error bursts and root-cause database issues?▼

Yes. Runbooks structure root-cause analysis for error bursts, database failures, and cascading failures in microservices. Checklists identify quick checks and common causes, while the framework ensures comprehensive data collection and verified resolution.

How do I document fixes and prevent recurring operational issues?▼

Runbooks include resolution and prevention steps, capturing fixes and preventive measures in structured form. Documentation aligned with the 5-step method ensures reproducible troubleshooting and builds operational knowledge for your team.

What should I check first when diagnosing Kubernetes deployment failures?▼

Start with quick-check checklists in troubleshooting runbooks targeting Kubernetes. These prioritize common causes—pod scheduling, resource limits, service connectivity—to accelerate diagnosis before moving to deeper hypothesis testing.

Related Skills

Explore More Software Engineering Skills→
williamzujkowskiwilliamzujkowski
17

devops-monitoring

Collect metrics, logs, and traces for distributed systems observability.

Community
Intermediate
flonatflonat
127

postmortem

Conduct structured incident post-mortems with root cause analysis and preventive fixes.

Community
Advanced
Proxy2021Proxy2021
5

api_monitor

Aggregate endpoint metrics, latency, and alert status to monitor API health.

Community
Advanced
vahagn-madatyanvahagn-madatyan

incident-response-network

Analyze network-forensics artifacts to guide evidence collection across Cisco, Juniper, and Arista devices.

Community
Advanced