From linux-service-triage
Diagnoses common Linux service issues using logs, systemd/PM2, file permissions, Nginx reverse proxy checks, and DNS sanity checks. Use when a server app is failing, unreachable, or misconfigured.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linux-service-triage:linux-service-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diagnoses common Linux service issues using logs, systemd/PM2, file permissions, Nginx reverse proxy checks, and DNS sanity checks.
Diagnoses common Linux service issues using logs, systemd/PM2, file permissions, Nginx reverse proxy checks, and DNS sanity checks.
systemctl status myapp output + journalctl excerptTRIAGE REPORT
- Symptom:
- Evidence (what you provided):
- Most likely cause:
- Fix plan (minimal steps):
- Exact commands (ONLY if user approved changes):
- Verification:
- Rollback:
nginx -t before reload and verify ports with ss.Input: "journal shows permission denied on /var/app/uploads." Output: path permission analysis + safe chown/chmod plan + verification.
Input: "App works locally but domain returns 502." Output: upstream port checks + nginx error log interpretation + proxy_pass fix plan.
npx claudepluginhub billyfranklim1/claude-skills --plugin linux-service-triageDiagnoses and resolves Linux system issues including performance problems, service failures, network issues, and resource constraints using a structured workflow.
Provides structured runbook for debugging backend service issues including API errors, performance degradation, crashes, and data inconsistencies. Uses checklists, log greps, git bisect, and reproduction steps.
Diagnoses Docker container failures, networking issues, permissions errors, port conflicts, data persistence problems, and health checks using docker compose logs, inspect, and targeted fixes.