server-management

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill server-management-helcio-nogueira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026/tree/main/.agents/skills/server-management
Command: npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill server-management-helcio-nogueira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating production servers involves many decisions—choosing process managers, setting up monitoring, planning scaling—and this Skill provides structured decision frameworks so you reason through operations instead of memorizing commands. ## Core Features & Use Cases - Process Management Guidance: Decision tables for choosing between PM2, systemd, Docker, and Kubernetes based on your application type. - Monitoring & Alerting Strategy: Frameworks for what to monitor (availability, performance, errors, resources) and how to tier alert severity. - Scaling & Troubleshooting Playbooks: Criteria for vertical vs. horizontal scaling and a prioritized troubleshooting sequence when things break. - Use Case: You are deploying a Node.js API to a Linux VPS and need to decide how to keep it running, what to monitor, and how to respond when CPU spikes—this Skill walks you through each decision. ## Quick Start Ask the AI to help you plan process management, monitoring, and scaling for your production server deployment.

Frequently Asked Questions about server-management

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

FAQPage Schema
How do I choose a process manager for a Node.js app?▼

PM2 is the recommended choice for Node.js apps because it provides clustering, zero-downtime reloads, and auto-restart on crash. For non-Node apps on Linux, systemd is the native option, while Docker suits containerized workloads.

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). Tier alerts as critical, warning, or info to prioritize response.

PM2 vs systemd for running apps on Linux?▼

PM2 suits Node.js apps needing clustering and zero-downtime reloads, while systemd is the Linux-native option for any application type. Both provide restart-on-crash and boot persistence; choose based on your stack.

When should I scale vertically vs horizontally?▼

Vertical scaling (more RAM/CPU on one machine) is a quick fix for single instances, while horizontal scaling (adding instances) is sustainable for distributed growth. High CPU suggests horizontal scaling; high memory may indicate a leak to fix first.

Why is my server slow and how do I troubleshoot it?▼

Follow a priority order: check if the process is running, review logs for errors, check disk/memory/CPU resources, verify network ports and DNS, then check dependencies like databases. Profile before scaling—slow responses are not always a capacity problem.