Server Management
- 849 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
server-management is a DevOps skill that teaches production server decision-making for process managers, monitoring strategy, and scaling approaches so developers can operate services without memorizing command cheat she
About
server-management is an antigravity-awesome-skills guide focused on production operations thinking rather than rote commands. The skill maps scenarios to tools—PM2 for Node.js clustering, systemd for Linux-native services, Docker or Podman for containers, and Kubernetes or Docker Swarm for orchestration—and explains goals like graceful reloads, health checks, and horizontal scaling tradeoffs. Developers reach for server-management when choosing how to supervise processes, design monitoring coverage, or plan scale-up paths for a live service. It emphasizes decision frameworks over copy-paste snippets, making it useful during architecture reviews, incident postmortems, or first production deployments. The skill covers process management principles, monitoring strategy, and scaling decisions as interconnected operational choices.
- Decision tables for process managers: PM2 for Node.js, systemd for any app, Docker for containers, Kubernetes for orches
- Four core process management goals: auto-recovery on crash, zero-downtime reload, CPU clustering, and reboot persistence
- Monitoring coverage across availability, performance, errors, and resource usage
- Three-tier alert severity strategy: Critical, Warning, and Info with defined response expectations
- Tool selection guidance from simple PM2/htop to full-stack Grafana and Datadog
Server Management by the numbers
- 849 all-time installs (skills.sh)
- +24 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #324 of 1,041 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill server-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 849 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you choose a process manager for production?
Learn how to choose the right process manager, monitoring strategy, and scaling approach for production services without memorizing commands.
Who is it for?
Backend developers and DevOps engineers deciding how to supervise, monitor, and scale production services on Linux or containers.
Skip if: Developers who only need one-off shell commands without operational strategy, or teams already standardized on a managed PaaS with no self-hosted infra.
When should I use this skill?
A developer asks which process manager to use, how to monitor production services, or how to approach scaling a live deployment.
What you get
A documented process-management, monitoring, and scaling decision framework aligned to the application's runtime and deployment model.
- operations decision framework
Files
Server Management
Server management principles for production operations.
Learn to THINK, not memorize commands.
---
1. Process Management Principles
Tool Selection
| Scenario | Tool |
|---|---|
| Node.js app | PM2 (clustering, reload) |
| Any app | systemd (Linux native) |
| Containers | Docker/Podman |
| Orchestration | Kubernetes, Docker Swarm |
Process Management Goals
| Goal | What It Means |
|---|---|
| Restart on crash | Auto-recovery |
| Zero-downtime reload | No service interruption |
| Clustering | Use all CPU cores |
| Persistence | Survive server reboot |
---
2. Monitoring Principles
What to Monitor
| Category | Key Metrics |
|---|---|
| Availability | Uptime, health checks |
| Performance | Response time, throughput |
| Errors | Error rate, types |
| Resources | CPU, memory, disk |
Alert Severity Strategy
| Level | Response |
|---|---|
| Critical | Immediate action |
| Warning | Investigate soon |
| Info | Review daily |
Monitoring Tool Selection
| Need | Options |
|---|---|
| Simple/Free | PM2 metrics, htop |
| Full observability | Grafana, Datadog |
| Error tracking | Sentry |
| Uptime | UptimeRobot, Pingdom |
---
3. Log Management Principles
Log Strategy
| Log Type | Purpose |
|---|---|
| Application logs | Debug, audit |
| Access logs | Traffic analysis |
| Error logs | Issue detection |
Log Principles
1. Rotate logs to prevent disk fill 2. Structured logging (JSON) for parsing 3. Appropriate levels (error/warn/info/debug) 4. No sensitive data in logs
---
4. Scaling Decisions
When to Scale
| Symptom | Solution |
|---|---|
| High CPU | Add instances (horizontal) |
| High memory | Increase RAM or fix leak |
| Slow response | Profile first, then scale |
| Traffic spikes | Auto-scaling |
Scaling Strategy
| Type | When to Use |
|---|---|
| Vertical | Quick fix, single instance |
| Horizontal | Sustainable, distributed |
| Auto | Variable traffic |
---
5. Health Check Principles
What Constitutes Healthy
| Check | Meaning |
|---|---|
| HTTP 200 | Service responding |
| Database connected | Data accessible |
| Dependencies OK | External services reachable |
| Resources OK | CPU/memory not exhausted |
Health Check Implementation
- Simple: Just return 200
- Deep: Check all dependencies
- Choose based on load balancer needs
---
6. Security Principles
| Area | Principle |
|---|---|
| Access | SSH keys only, no passwords |
| Firewall | Only needed ports open |
| Updates | Regular security patches |
| Secrets | Environment vars, not files |
| Audit | Log access and changes |
---
7. Troubleshooting Priority
When something's wrong:
1. Check if running (process status) 2. Check logs (error messages) 3. Check resources (disk, memory, CPU) 4. Check network (ports, DNS) 5. Check dependencies (database, APIs)
---
8. Anti-Patterns
| ❌ Don't | ✅ Do |
|---|---|
| Run as root | Use non-root user |
| Ignore logs | Set up log rotation |
| Skip monitoring | Monitor from day one |
| Manual restarts | Auto-restart config |
| No backups | Regular backup schedule |
---
Remember: A well-managed server is boring. That's the goal.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
Azure AiIntegrates Azure AI Content Safety, Document Intelligence, Speech, and Search services into Java-based agents and applications.479k1.3kAzure PrepareGenerate the exact Azure infrastructure files, Dockerfiles, and azure.yaml configuration needed before deploying any new or modernized application.479k1.3kAzure StorageConnect agents and applications to Azure Blob Storage, File Shares, Queues, Tables, and Data Lake without leaving the coding environment.478k1.3kAppinsights InstrumentationAutomatically instrument web applications running on Azure App Service with Application Insights for observability without manual configuration.478k1.3kAzure Resource LookupInstantly list, query, and discover any Azure resources across subscriptions without leaving the agent chat.478k1.3kAzure AigatewayConfigure Azure API Management as a secure, governed gateway for routing traffic to LLMs, MCP servers, and agent tools.478k1.3kHow it compares
Pick server-management over generic Linux cheat sheets when you need scenario-based tool selection and scaling rationale for production services.
FAQ
What process managers does server-management recommend?
server-management recommends PM2 for Node.js apps needing clustering and reload, systemd for Linux-native services, Docker or Podman for containerized apps, and Kubernetes or Docker Swarm for orchestration at scale.
Does server-management provide copy-paste commands?
server-management focuses on decision frameworks for process management, monitoring, and scaling rather than memorized command lists. Developers use it to choose the right operational approach for their stack.
Is Server Management safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.