server-management

Formalize production server process management, monitoring, and scaling decisions.

132|22|Updated Dec 18, 2025

Search Tags:#monitoring #observability #infrastructure #principles #scaling #server-management

Ready to run

npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill server-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/server-management
Command: npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill server-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides thinking frameworks for designing, operating, and scaling production servers, reducing reliance on memorized commands.

Core Features & Use Cases

Process & lifecycle guidance: establish robust process startup, graceful shutdown, auto-recovery, and failure handling.
Monitoring & observability: define metrics, health checks, alerting strategies, and logging practices to ensure reliability.
Capacity planning & scaling: outline criteria for horizontal and vertical scaling across environments (on-prem, cloud, containers).

Quick Start

Use the server-management skill to draft a high-level playbook for production server operations, covering process management, monitoring strategy, and scaling decisions.

Frequently Asked Questions about server-management

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

FAQPage Schema

How do I design a monitoring strategy for production servers?▼

Monitoring strategy defines metrics, health checks, and alerting practices to ensure server reliability. Establish what to measure (CPU, memory, disk, application-specific metrics), how often to check, alert thresholds, and log aggregation approach for your production environment.

What's the best way to handle process startup, shutdown, and auto-recovery?▼

Process lifecycle management covers robust startup procedures, graceful shutdown sequences, and automatic recovery mechanisms. Define startup order, dependency checks, signal handling for clean shutdown, and restart policies to maintain availability during failures or deployments.

When should I scale horizontally versus vertically?▼

Scaling decisions depend on workload type, cost constraints, and infrastructure. Horizontal scaling adds servers for stateless services; vertical scaling increases resources on existing machines. Establish criteria based on bottleneck type, latency requirements, and whether your application supports distribution.

How do I plan capacity for on-premises and cloud servers?▼

Capacity planning translates business growth into infrastructure requirements by forecasting load, measuring current resource utilization, and defining scaling thresholds. Consider environment differences: on-prem requires long lead times; cloud offers elasticity but incurs variable costs.

What are common anti-patterns in server management?▼

Server management anti-patterns include manual process restarts, reactive alerting without thresholds, over-provisioning without utilization review, and skipping graceful shutdown. Recognizing these helps avoid operational brittleness and unplanned downtime.