About this skill

Problem It Solves

Many server tasks still rely on ad hoc ssh, scp, and systemctl commands scattered across terminals, making it easy to miss logs, timeouts, and permission issues. This skill groups common operations into explicit actions for service checks, configuration uploads, and log review.

How It Works

The skill uses SSH as the connection layer and supports:
- Status queries for basic server state
- Service management with start, stop, and restart
- Log viewing using --lines, --follow, and --since
- Command execution through exec
- File transfer with upload and download

Typical usage starts from ~/.ssh/config, then targets a server for a specific action. Error handling covers common cases such as Connection refused, Permission denied, Command not found, and Timeout.

Boundaries and Notes

It fits internal operations or controlled environments. In production, use a dedicated account, SSH keys, sane timeouts, a jump host when needed, and audit logging. It does not automatically fix permission or network issues; authentication failures, blocked ports, and missing commands still require checking the actual server state.

Screenshots

Use Cases

After deploying configuration, restart the target service and review recent logs to confirm recovery.
During incident triage, fetch logs by timestamp and follow them to isolate the latest failure.
Across multiple servers, run parallel status checks and commands to compare service states.
Before release, upload configuration files and download runtime logs afterward to verify changes.

Best For

Ops engineers who patrol production services and need quick status checks plus restarts for failing services.
Backend engineers inheriting legacy systems who need consistent log review, command execution, and file transfer.
SREs managing multiple internal test machines who need parallel status checks and service configuration comparison.
Release engineers who upload config files and download runtime logs to verify deployments.