server-management

Guides server process management, monitoring, logging, and scaling decisions for production operations.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pd-phuc/laravel-template --skill server-management-pd-phuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/pd-phuc/laravel-template/tree/main/.claude/skills/server-management
Command: npx skills add https://github.com/pd-phuc/laravel-template --skill server-management-pd-phuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating production servers requires making correct decisions about process managers, monitoring tools, log strategies, and scaling approaches, and wrong choices lead to downtime, disk-full outages, and undetected failures. ## Core Features & Use Cases - Process Management Guidance: Decision tables for choosing between PM2, systemd, Docker, and Kubernetes based on application type and goals like zero-downtime reloads and clustering. - Monitoring and Alerting Strategy: Frameworks for what to monitor (availability, performance, errors, resources), alert severity levels, and tool selection from PM2 metrics to Grafana and Sentry. - Scaling and Troubleshooting Playbooks: Symptom-to-solution mappings for scaling decisions and a prioritized five-step troubleshooting sequence for diagnosing outages. - Use Case: When a Node.js API starts returning slow responses in production, use this Skill to work through the troubleshooting priority order, check process status and resource usage, then decide between vertical and horizontal scaling. ## Quick Start Ask the AI to help you decide how to deploy, monitor, and scale your production application using server management best practices.

Frequently Asked Questions about server-management

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

FAQPage Schema
How do I choose between PM2 and systemd for process management?▼

PM2 suits Node.js applications needing clustering and zero-downtime reloads, while systemd works for any application as a Linux-native solution. Choose based on your app type and whether you need container orchestration like Docker or Kubernetes.

What should I monitor on a production server?▼

Monitor four categories: availability (uptime, health checks), performance (response time, throughput), errors (rate and types), and resources (CPU, memory, disk). Assign alert severity levels so critical issues trigger immediate action.

When should I scale vertically vs horizontally?▼

Vertical scaling (more RAM/CPU on one instance) is a quick fix for single-instance bottlenecks. Horizontal scaling (adding instances) is the sustainable distributed approach, and auto-scaling fits variable traffic patterns.

How do I troubleshoot a server that is down?▼

Follow a priority order: check if the process is running, check logs for error messages, check resources like disk and memory, check network ports and DNS, then check dependencies like databases and external APIs.

What are common server management anti-patterns to avoid?▼

Avoid running services as root, ignoring log rotation, skipping monitoring, relying on manual restarts, and having no backup schedule. Instead use non-root users, structured JSON logging, auto-restart configuration, and regular backups.