troubleshooting-doc

Record structured troubleshooting knowledge into centralized docs with YAML frontmatter.

1|Updated Feb 21, 2026

Search Tags:#templates #documentation #troubleshooting #postmortem #knowledge-base #incident-management

Ready to run

npx skills add https://github.com/kssumin/claude-playground --skill troubleshooting-doc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: troubleshooting-doc
Source: https://github.com/kssumin/claude-playground/tree/main/.claude/skills/troubleshooting-doc
Command: npx skills add https://github.com/kssumin/claude-playground --skill troubleshooting-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams structure and store troubleshooting experiences as documented knowledge in docs/troubleshooting, enabling faster learning and recurrence avoidance.

Core Features & Use Cases

Structured templates for incident documentation (phase-based prompts, evidence, root-cause analysis, actions, and prevention)
Auto-triggers after complex debugging sessions or resolved incidents to capture lessons learned
Centralized storage under docs/troubleshooting with an index to surface past problems

Quick Start

Record a new troubleshooting entry using the standardized template and save it to docs/troubleshooting.

Frequently Asked Questions about troubleshooting-doc

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

FAQPage Schema

What is the best way to document troubleshooting experiences for a knowledge base?▼

Documenting troubleshooting experiences involves recording structured knowledge into centralized docs. Using standardized templates for incident documentation captures evidence, root-cause analysis, actions, and prevention steps to enable rapid learning and reuse.

How do I structure a post-incident review for complex debugging sessions?▼

Structure a post-incident review by using phase-based prompts to capture evidence, root-cause analysis, actions, and prevention. Save the documented troubleshooting entry into a centralized docs directory to build a searchable incident management knowledge base.

When do I need to use a template for incident documentation?▼

You need an incident documentation template after complex debugging sessions, bug investigations, or resolved incidents. Auto-triggering template creation ensures critical troubleshooting knowledge is captured for future reference and recurrence avoidance.

Can I use this postmortem approach without any external dependencies?▼

Yes, this postmortem approach requires no external dependencies. It functions by writing a YAML frontmatter with name and description in SKILL.md, optionally referencing local directories for scripts, references, and assets to support on-demand troubleshooting resources.

How to organize postmortem templates in a centralized knowledge base?▼

Organize postmortem templates by saving structured troubleshooting entries under a centralized docs directory. Maintain an index within this directory to surface past problems, enabling fast retrieval and reuse of documented incident management knowledge.