Create structured troubleshooting documentation that helps users and support teams quickly diagnose and resolve common issues.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontroubleshooting-guideExecute the skills CLI command in your project's root directory to begin installation:
Fetches troubleshooting-guide from aj-geddes/useful-ai-prompts and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate troubleshooting-guide. Access via /troubleshooting-guide in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
162
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
162
stars
Create structured troubleshooting documentation that helps users and support teams quickly diagnose and resolve common issues.
# 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
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
Useful defaults in troubleshooting-guide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
troubleshooting-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend troubleshooting-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
troubleshooting-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: troubleshooting-guide is the kind of skill you can hand to a new teammate without a long onboarding doc.
troubleshooting-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: troubleshooting-guide is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in troubleshooting-guide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend troubleshooting-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend troubleshooting-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 47