localsetup-linux-service-triage

Diagnose Linux service issues from logs, states, and permissions.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/cptnfren/localsetup --skill localsetup-linux-service-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localsetup-linux-service-triage
Source: https://github.com/cptnfren/localsetup/tree/main/_localsetup/skills/localsetup-linux-service-triage
Command: npx skills add https://github.com/cptnfren/localsetup --skill localsetup-linux-service-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses common Linux service issues by analyzing logs, service states, permissions, reverse proxy configs, and DNS for reliable uptime.

Core Features & Use Cases

  • Triage with logs: Correlates journalctl/PM2 outputs to pinpoint failures.
  • Config & permission checks: Verifies file/directory permissions and config correctness for services.
  • Proxy & DNS sanity: Checks Nginx reverse proxy config, domain DNS, and TLS sanity to ensure accessibility.

Quick Start

Describe the symptoms, gather logs and status outputs, then follow the triage steps to identify and fix the root cause.

Frequently Asked Questions about localsetup-linux-service-triage

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

FAQPage Schema
How do I diagnose Linux service issues using journalctl logs?

Diagnose Linux service issues by analyzing journalctl logs and service states to pinpoint failures. Correlating these outputs with permissions and configurations helps identify the root cause of downtime.

What is the best way to troubleshoot Nginx reverse proxy configuration failures?

Troubleshoot Nginx reverse proxy failures by checking configurations, domain DNS sanity, and TLS settings. Verifying these elements ensures end-to-end connectivity and resolves external accessibility issues.

How do I triage PM2 managed services that keep crashing?

Triage PM2 service crashes by analyzing PM2 log outputs alongside service states. Correlating these logs with file and directory permissions isolates the root cause of the application failure.

Why does my systemd service fail to start after a permissions change?

Systemd service startup failures often stem from incorrect file or directory permissions. Checking permissions and systemd status outputs helps verify access rights and identify the configuration error.

Can I use this triage process for both systemd and PM2 managed applications?

Yes, this triage process supports both systemd and PM2 managed applications. It analyzes logs and service states across both managers to produce a unified triage report with a minimal fix plan.

What inputs do I need to gather before starting Linux service triage?

Before starting Linux service triage, gather symptom descriptions, service status outputs, relevant log snippets, and configuration files. These inputs are required to accurately identify the root cause.