Skip to content
Skills Library
DevOps & cloud · Analysis

linux-server-ops

/linux-server-ops

Use when diagnosing or managing a Linux server over SSH.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when diagnosing or managing a Linux server over SSH.

Original author description

Use when diagnosing or managing a Linux server over SSH.

How it works

  1. First look, before touching anything
  2. Changing things
  3. Reporting
Original SKILL.md headings · 22 lines, 269 words
SKILL.md preview
---
name: linux-server-ops
description: "Use when diagnosing or managing a Linux server over SSH."
version: 1.0.0
category: devops
---

# Linux server operations

## First look, before touching anything
1. Run `uptime; df -h; free -m; systemctl --failed` together. Load, disk, memory and failed services explain most incidents.
2. Only then read the logs: `journalctl -u <service> -n 200 --no-pager`, `journalctl -p err -b`, `dmesg -T | tail -50`.
3. A full disk breaks everything else: above 90 %, find the cause with `du -xh --max-depth=1 / | sort -h | tail` before restarting anything.
4. Check what changed last: `ls -lt /etc | head`, `journalctl --since "2 hours ago"`, the package log (`/var/log/apt/history.log`).

## Changing things
- Never change a file without a backup: `cp -a file file.bak.$(date +%F-%H%M)`. Reason: the rollback must be one command.
- Validate before reloading: `nginx -t`, `sshd -t`, `apachectl configtest`, `named-checkconf`. A broken config plus a restart is an outage.
- Prefer `systemctl reload` to `restart` when the service supports it.
- Before opening a port, see what already listens: `ss -tulpn`. Open the firewall (`ufw allow …` / `firewall-cmd --add-port …`) only once the service is up on the right address.
- Never lock yourself out: keep the current SSH session open while changing sshd or the firewall, and test from a second session.
- One change at a time, checked after each step; stop and report at the first surprise.

## Reporting
- Show the real output (the important lines), never what it "probably" says.
- Say what you changed, where the backup is and how to undo it.
- When the server can't be reached from here, give the exact commands in order and ask for their output.

Versions

The database has no other skills named linux-server-ops.

Database snapshot: 13.11.2026 · package version c5c89a8d6932 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 98ssh-server-ops
    Use when Codex needs to bootstrap, diagnose, transfer files, or operate SSH access from Windows, macOS, or Linux to Linux, POSIX, gateway, bastion, or Slurm/HPC targets using the bundled SSH Server Ops toolkit.
  • 93ssh-server-ops
    Use when Codex needs to bootstrap, diagnose, transfer files, or operate SSH access from Windows, macOS, or Linux to Linux, POSIX, gateway, bastion, or Slurm/HPC targets using the bundled SSH Server Ops toolkit.
  • 100ssh-ops
    This skill should be used when the user asks to "run a command on a server", "check Docker containers", "restart a service", "read a remote file", "check disk usage", or mentions managing remote infrastructure via SSH. Teaches CLI-first workflow with progressive tool discovery.
  • 100linux-server-hardening
    Use when an authorised operator wants to remediate verified Linux security findings interactively across SSH, firewall, MAC, services, permissions, and updates; use linux-security-analysis first.
  • 100linux-service-ops
    Configure and troubleshoot application services on an authorized Linux host with explicit service ownership. Use when managing systemd units, startup, logs, users, permissions or service resources; preserve the administrator existing distro configuration.
  • 100pro-ssh
    Run commands on remote servers over SSH (AWS EC2, Synology NAS, any Linux host), by saved name or direct host/user/key. Use for 'check the server', 'look at logs', 'is the deploy live'.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.