server-management

Guide server process management, monitoring, and scaling decisions.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill server-management-brunosantanadeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/server-management
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill server-management-brunosantanadeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production services often struggle with outages and latency due to ad-hoc decision-making around processes, monitoring, and scaling. This Skill provides a principled framework for thinking about server management, enabling operators to design resilient operations and reduce firefighting.

Core Features & Use Cases

  • Process management guidelines for selecting tools (systemd, PM2, Docker/Podman, Kubernetes) and implementing restart on crash, zero-downtime reload, and clustering.
  • Monitoring and logging discipline with defined metrics, alert strategies, log rotation, health checks, and dependency health.
  • Scaling and security guidance covering when to scale, horizontal vs vertical scaling, auto-scaling approaches, and security best practices.
  • Use Case: A production API experiences latency spikes; apply the framework to improve reliability and automate recovery with minimal ops effort.

Quick Start

Start by auditing current processes, implement a basic restart policy, and establish essential health checks to begin operating with a principled server-management approach.

Frequently Asked Questions about server-management

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

FAQPage Schema
What's the best way to manage server processes and prevent downtime in production?

Reliable server management requires a structured framework for process selection, restart policies, and health checks. Using tools like systemd, PM2, or Docker ensures resilient operations and reduces firefighting during outages.

How do I choose between systemd, PM2, and Docker for process management?

Process management tool selection depends on your environment and scaling needs. The framework guides choosing between systemd, PM2, Docker/Podman, or Kubernetes based on requirements for restart-on-crash, zero-downtime reloads, and clustering.

How do I set up monitoring and alerting for production API latency spikes?

Monitoring production latency requires defined metrics, log rotation, and alert strategies. Establishing health checks and dependency monitoring allows you to automate recovery and improve reliability with minimal ops effort.

When should I use horizontal vs vertical scaling for my servers?

Scaling decisions depend on your workload and resource bottlenecks. The framework provides principled guidance on when to scale and whether to apply horizontal or vertical scaling, including auto-scaling approaches for production deployments.

Does this server management approach work for incident response scenarios?

Yes, server management principles apply directly to incident response. The framework gives operators structured guidance for process management and monitoring during outages, replacing ad-hoc commands with principled decision-making.