server-management

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

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill server-management-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.agent/skills/server-management
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill server-management-beliciobcardoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running production servers involves recurring decisions about process supervision, monitoring, logging, scaling, and security, and ad-hoc choices often lead to outages, disk-full incidents, and unrecoverable crashes. This Skill provides decision frameworks and principles so you can reason about server operations instead of memorizing commands. ## Core Features & Use Cases - Process Management Guidance: Choose between PM2, systemd, Docker, or Kubernetes based on your application type, with goals like auto-restart, zero-downtime reload, and clustering. - Monitoring & Alerting Strategy: Define what to monitor (availability, performance, errors, resources) and how to tier alert severity from critical to informational. - Scaling & Troubleshooting Frameworks: Decide between vertical, horizontal, and auto-scaling based on symptoms, and follow a prioritized troubleshooting sequence from process status to dependencies. - Use Case: When your Node.js API starts returning slow responses under traffic spikes, use this Skill to decide whether to profile first, scale horizontally, or enable auto-scaling, and to verify health checks and logs before acting. ## Quick Start Ask the AI to help you design a monitoring and restart strategy for your production Node.js application using server management principles.

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?▼

Use PM2 for Node.js applications when you need clustering and zero-downtime reloads. Use systemd for any application on Linux when you want native OS integration and automatic restart on boot.

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?▼

Scale vertically as a quick fix for a single instance, such as adding RAM for memory pressure. Scale horizontally by adding instances for sustainable growth, and use auto-scaling when traffic is variable or spiky.

What is the correct order for troubleshooting a server issue?▼

Check in this order: whether the process is running, the logs for error messages, resource usage (disk, memory, CPU), network connectivity (ports, DNS), and finally external dependencies like databases and 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 logs, auto-restart configuration, and monitoring from day one.