Automated summary
Presents high-level principles for managing production servers, covering process supervision, monitoring, logging, scaling, health checks, security, and troubleshooting priorities.
Strengths
- Organizes operational decisions into clear comparison tables for tool selection, scaling symptoms, and alert severity.
- Covers the full lifecycle from process management to monitoring, logging, and incident triage in one compact document.
- Emphasizes principles and anti-patterns rather than platform-specific commands, so it stays portable.
- Includes a pragmatic troubleshooting order: process, logs, resources, network, dependencies.
Limitations
- Stays conceptual and provides no concrete commands, configuration examples, or runnable health-check code.
- Tool recommendations are generic and may not reflect current best practices or cost constraints.
- The security section is brief and does not address hardening, compliance, or incident response in depth.
Use when planning or reviewing production server operations, choosing a process manager, or establishing monitoring and troubleshooting baselines.
Do not use when you need executable setup commands, platform-specific configuration, or deep incident-response procedures.
Security analysis
SafeThe content is purely advisory prose and reference tables about server operations; it contains no executable commands, no network calls, no credential handling, and no instructions to modify or delete anything. Bash is declared in allowed-tools, which is broader than the document actually needs, but nothing in the text directs its use, so execution risk is negligible.
No concerns found
How this analysis is madeExamples
Review my production server setup and recommend whether to use PM2, systemd, or Docker for a Node.js API that must survive crashes and reboots.Help me define what to monitor and how to prioritize alerts for a small SaaS deployed on a single Linux VPS.My server is slow and sometimes stops responding. Walk me through a prioritized troubleshooting checklist and tell me when to scale vertically vs horizontally.name: server-management description: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands. allowed-tools: Read, Write, Edit, Glob, Grep, Bash
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
- Rotate logs to prevent disk fill
- Structured logging (JSON) for parsing
- Appropriate levels (error/warn/info/debug)
- 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:
- Check if running (process status)
- Check logs (error messages)
- Check resources (disk, memory, CPU)
- Check network (ports, DNS)
- 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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/server-management-principles-mvda87py/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/server-management-principles-mvda87py' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/server-management-principles-mvda87py/download' --output '.skill-downloads/server-management-principles-mvda87py/SKILL.md.part' && mv '.skill-downloads/server-management-principles-mvda87py/SKILL.md.part' '.skill-downloads/server-management-principles-mvda87py/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep, Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && test -s '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/server-management' && cp -R '.skill-downloads/server-management-principles-mvda87py' '.claude/skills/server-management'Cursor
test -f '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && test -s '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/server-management' && cp -R '.skill-downloads/server-management-principles-mvda87py' '.cursor/skills/server-management'Codex
test -f '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && test -s '.skill-downloads/server-management-principles-mvda87py/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/server-management' && cp -R '.skill-downloads/server-management-principles-mvda87py' '.agents/skills/server-management'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/server-management-principles-mvda87py'openskills read 'server-management-principles-mvda87py'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/server-management-principles-mvda87py/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.