Create structured troubleshooting documentation that helps users and support teams quickly diagnose and resolve common issues.
When to Use
FAQ documentation
Common error messages
Debug guides
Known issues lists
Error code reference
Performance troubleshooting
Configuration issues
Installation problems
Quick Start
Installation problems
# Troubleshooting Guide
## Quick Diagnosis
### Is the Service Working?
Check our [Status Page](https://status.example.com) first.
### Quick Health Checks
```bash
# 1. Check service is running
curl https://api.example.com/health
# 2. Check your API key
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.example.com/api/v1/status
# 3. Check network connectivity
ping api.example.com
# 4. Check DNS resolution
nslookup api.example.com
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Issue: "Authentication Failed"](references/issue-authentication-failed.md) | Issue: "Authentication Failed" |
| [Issue: "Rate Limit Exceeded"](references/issue-rate-limit-exceeded.md) | Issue: "Rate Limit Exceeded" |
| [Issue: "Connection Timeout"](references/issue-connection-timeout.md) | Issue: "Connection Timeout" |
| [Issue: "Invalid JSON Response"](references/issue-invalid-json-response.md) | Issue: "Invalid JSON Response" |
| [Issue: "Slow Performance"](references/issue-slow-performance.md) | Issue: "Slow Performance" |
## Best Practices
### ✅ DO
- Start with most common issues
- Include error messages verbatim
- Provide step-by-step diagnostics
- Show expected vs actual output
- Include code examples
- Document error codes
- Add screenshots/videos
- Link to related documentation
- Keep solutions up-to-date
- Include workarounds
- Test all solutions
### ❌ DON'T
- Use vague descriptions
- Skip diagnostic steps
- Forget to show examples
- Assume technical knowledge
- Skip verification steps
- Forget edge cases
---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/aj-geddes) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->
1---2name: aj-geddes-useful-ai-prompts-troubleshooting-guide3description: Troubleshooting Guide4---56# Troubleshooting Guide78## Table of Contents910- [Overview](#overview)11- [When to Use](#when-to-use)12- [Quick Start](#quick-start)13- [Reference Guides](#reference-guides)14- [Best Practices](#best-practices)1516## Overview1718Create structured troubleshooting documentation that helps users and support teams quickly diagnose and resolve common issues.1920## When to Use2122- FAQ documentation23- Common error messages24- Debug guides25- Known issues lists26- Error code reference27- Performance troubleshooting28- Configuration issues29- Installation problems3031## Quick Start3233- Installation problems3435````markdown36# Troubleshooting Guide3738## Quick Diagnosis3940### Is the Service Working?4142Check our [Status Page](https://status.example.com) first.4344### Quick Health Checks4546```bash47# 1. Check service is running48curl https://api.example.com/health4950# 2. Check your API key51curl -H "Authorization: Bearer YOUR_API_KEY" \52 https://api.example.com/api/v1/status5354# 3. Check network connectivity55ping api.example.com5657# 4. Check DNS resolution58nslookup api.example.com59```6061## Reference Guides6263Detailed implementations in the `references/` directory:6465| Guide | Contents |66|---|---|67| [Issue: "Authentication Failed"](references/issue-authentication-failed.md) | Issue: "Authentication Failed" |68| [Issue: "Rate Limit Exceeded"](references/issue-rate-limit-exceeded.md) | Issue: "Rate Limit Exceeded" |69| [Issue: "Connection Timeout"](references/issue-connection-timeout.md) | Issue: "Connection Timeout" |70| [Issue: "Invalid JSON Response"](references/issue-invalid-json-response.md) | Issue: "Invalid JSON Response" |71| [Issue: "Slow Performance"](references/issue-slow-performance.md) | Issue: "Slow Performance" |7273## Best Practices7475### ✅ DO7677- Start with most common issues78- Include error messages verbatim79- Provide step-by-step diagnostics80- Show expected vs actual output81- Include code examples82- Document error codes83- Add screenshots/videos84- Link to related documentation85- Keep solutions up-to-date86- Include workarounds87- Test all solutions8889### ❌ DON'T9091- Use vague descriptions92- Skip diagnostic steps93- Forget to show examples94- Assume technical knowledge95- Skip verification steps96- Forget edge cases9798---99> Converted and distributed by [TomeVault](https://tomevault.io/claim/aj-geddes) — claim your Tome and manage your conversions.100<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/aj-geddes-useful-ai-prompts-troubleshooting-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Troubleshooting Guide It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.