server-management

Name: server-management
Availability: InStock
Author: Ivan

Provide decision-making principles and best practices for production server management.

2|Updated Jan 19, 2026

Search Tags:#devops #monitoring #troubleshooting #reliability #operations #scaling #server-management

Ready to run

npx skills add https://github.com/ivanshtokov/copilot-kit --skill server-management-ivanshtokov

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a principled framework for operating reliable, scalable servers and services, helping teams avoid ad-hoc, brittle setups.

Core Features & Use Cases

Process management guidelines for modern runtimes (systemd, PM2, Docker, Kubernetes)
Monitoring, health checks, and log management to detect and respond to issues
Scaling decisions and governance, including when to scale and how to implement auto-scaling
Security practices and troubleshooting checklists to reduce incident risk
Real-world use cases across single services, microservices, and distributed architectures

Quick Start

Audit your current process management and monitoring setup against these principles to start improving reliability today.

Frequently Asked Questions about server-management

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

FAQPage Schema

What is the best way to manage Node.js process management in production?▼

Production Node.js process management requires structured guidelines for selecting and configuring tools like systemd, PM2, Docker, or Kubernetes to ensure reliable execution. This provides decision-making principles to avoid ad-hoc, brittle setups.

How do I set up server monitoring and alerting for containerized services?▼

Server monitoring and alerting for containerized services requires defining specific metrics, implementing health checks, and establishing log management to detect issues. This delivers concrete patterns for metric definitions and logging to help detect and respond to incidents effectively.

When do I need to implement auto-scaling for distributed architectures?▼

Auto-scaling for distributed architectures is needed when traffic demands require dynamic resource adjustment to maintain reliability. This provides scaling decisions and governance, detailing when to scale and concrete patterns for implementing auto-scaling strategies.

Does this server management framework apply to microservices and single services alike?▼

Yes, this server management framework applies to single services, microservices, and distributed architectures. It delivers real-world use cases and structured guidance across these environments, ensuring operations principles are adaptable to various deployment scales and configurations.

What are common anti-patterns to avoid when troubleshooting server reliability?▼

Troubleshooting server reliability anti-patterns include ad-hoc configurations and ignoring structured health checks or security practices. This provides troubleshooting checklists and anti-pattern avoidance guidance to reduce incident risk and ensure consistent, scalable operations across modern runtimes.