关于 troubleshooting-guide
用于编写结构化故障排查文档的技能,服务于用户和支持团队。它通过诊断步骤、示例和解决方法,整理常见错误、配置问题及性能故障。
主要功能
- 01结构化问题指南
- 02分步诊断流程
- 03错误消息与代码参考
- 04预期和实际输出示例
- 05变通方案与验证步骤
适用场景
- 01记录身份验证失败的处理方法
- 02说明限流和超时错误
- 03指导用户排查安装问题
- 04整理性能故障排查步骤
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ aj-geddes/ useful-ai-prompts --skill troubleshooting-guide安装后在 Claude Code 中输入/troubleshooting-guide确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
references/issue-authentication-failed.mdissue-connection-timeout.mdissue-invalid-json-response.mdissue-rate-limit-exceeded.mdissue-slow-performance.mdscripts/validate-api.shtemplates/api-scaffold.yaml详细介绍
故障排查指南
目录
概述
创建结构化的故障排查文档,帮助用户和支持团队快速诊断并解决常见问题。
适用场景
- FAQ 文档
- 常见错误消息
- 调试指南
- 已知问题列表
- 错误代码参考
- 性能故障排查
- 配置问题
- 安装问题
快速入门
- 安装问题
# 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
评论
支持 Markdown