skills.rest
g-zenr
g-zenrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

troubleshoot

Diagnose runtime and production issues by analyzing logs and errors.

Updated Feb 13, 2026
Search Tags:#debugging#troubleshooting#log analysis#incident response#runtime errors#production issues
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill troubleshoot-g-zenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/troubleshoot
Command: npx skills add https://github.com/g-zenr/relay-api --skill troubleshoot-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps investigate and diagnose runtime or production issues by analyzing logs, errors, and unexpected behavior, guiding users through a systematic troubleshooting process.

Core Features & Use Cases

  • Systematic Diagnosis: Guides users through steps to gather symptoms, check infrastructure, configuration, and application logs.
  • Root Cause Analysis: Helps identify whether issues stem from configuration, hardware, or software bugs.
  • Use Case: When users report intermittent API errors, this Skill can help pinpoint whether the issue is due to a recent configuration change, a failing external service, or a bug in the application code.

Quick Start

Use the troubleshoot skill to investigate why the health endpoint is returning a 500 error.

Frequently Asked Questions about troubleshoot

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

FAQPage Schema
How do I diagnose runtime errors and system failures in production environments?▼

To diagnose production issues, systematically gather symptoms, verify configurations, check infrastructure, and analyze application logs to identify the root cause of unexpected behavior.

What is the best way to troubleshoot intermittent API errors and performance degradation?▼

Troubleshooting intermittent API errors involves systematically checking recent configuration changes, evaluating external service dependencies, and analyzing application logs to isolate whether the root cause is software, hardware, or configuration.

How do I perform root cause analysis for live application errors?▼

Perform root cause analysis by gathering symptoms, conducting infrastructure checks, verifying system configurations, and analyzing application logs to determine whether issues originate from software bugs, hardware failures, or configuration errors.

Can I use systematic troubleshooting to identify if a configuration change caused my system failure?▼

Yes, systematic troubleshooting verifies configurations to help pinpoint whether a system failure or runtime error stems from a recent configuration change, a failing external service, or an underlying application bug.

What should I check during incident response when my health endpoint returns a 500 error?▼

During incident response for a 500 error, check infrastructure status, verify application configurations, and analyze runtime logs to systematically investigate the unexpected behavior and resolve the production issue.

Related Skills

Explore More Software Engineering Skills→
bricerisingbricerising
7

debug

Triage production issues by interpreting logs, traces, and metrics.

Community
Intermediate
edulazaroedulazaro
12

lc:analyze-error

Analyze Laravel stack traces and apply code fixes across controllers, models, and database layers.

Community
Advanced
mymx2mymx2
4

stacktrace-log-triage

Diagnose Kotlin and Spring failures by analyzing stack traces and startup logs.

Community
Advanced
NagyViktNagyVikt
2

observability

Configure structured logging, tracing, and performance monitoring for Vercel-hosted applications.

Community
Advanced