Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

host-ops

Estrellas56

Forks1

Actualizado7 de julio de 2026 a las 16:05

Troubleshoot and manage generic Linux hosts (anything that is not Proxmox or TrueNAS). Use this whenever Evan points at a plain Linux server, VM, or container host by alias and asks about services, disk space, networking, updates, processes, or logs, or when a host is slow, down, or misbehaving. It drives systemd, packages, storage, and networking over SSH. Trigger this for any host-level work the Proxmox and TrueNAS skills do not cover.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

serversathome

serversathome/homelabhero

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

SKILL.md

readonly

name

host-ops

description

Host ops (Linux)

Confirm the target with hh list, then read capabilities/linux.md for the full toolset. Diagnose read-only first, then propose changes and confirm before anything state-changing.

Fast path

hh run <alias> "systemctl --failed"                       # failed units first
hh run <alias> "uptime; free -h; df -h"                   # pressure + space
hh run <alias> "ss -tulpn"                                 # what is listening
hh run <alias> "journalctl -p err -b --no-pager | tail -40"

Common cases

Service down: check status and logs, restart (confirm), re-verify.
Disk full: find the heavy consumer with du -xh --max-depth=1 / before deleting anything. Never blind-delete.
Unreachable: usually network-diag, not the host. Confirm with hh test.
Broke after an update: check systemctl --failed, recent journalctl -p err, and whether a reboot is pending (ls /var/run/reboot-required on Debian/Ubuntu).

Containers on the host

If it runs Docker, hh run <alias> "docker ps" and the docker-stack-ops skill take over for container-level work.

Más de este repositorio

mismo repositorio

homelab-triage

serversathome/homelabhero

Top-level triage and health-overview workflow for the homelab. Use this whenever Evan asks broad or symptom-first questions like "what's wrong", "is everything okay", "something's down", "the homelab feels slow", "give me an overview", "health check", "status of everything", or reports a problem without naming the layer. Also use it as the first step for any incident where the failing component is not yet obvious, before dropping into the host-specific skills. Reach for this even when Evan does not say the word "triage" but is clearly asking for a whole-system look or reporting a vague fault.

2026-07-1856

truenas-ops

serversathome/homelabhero

Troubleshoot and manage TrueNAS SCALE over SSH. Use this whenever Evan mentions TrueNAS, the NAS, ZFS, a pool or dataset, a scrub, a snapshot, replication, a failing or degraded disk, SMART data, an SMB/NFS/iSCSI share, a TrueNAS app, or storage that is full, slow, or throwing errors. Trigger this for anything storage-layer even when the symptom first shows up as an app or VM that lost its data mount. Prefer this over generic shell reasoning for pool, disk, dataset, and share work.

2026-07-1856

docker-stack-ops

serversathome/homelabhero

Troubleshoot and manage the Docker / Dockge stacks over SSH, especially the arr media stack. Use this whenever Evan mentions a container, Docker, Dockge, a compose stack, or any specific app such as Jellyfin, qBittorrent, gluetun, Radarr, Sonarr, Prowlarr, Seerr, Immich, Seafile, SearXNG, or similar, and whenever the symptom is app-level: a container is down, restarting, unhealthy, downloads are stalled, requests are not processing, or a service is unreachable while its host is fine. Trigger this even if he just names an app and says it is broken.

2026-07-0756

add-server

serversathome/homelabhero

Register a new server so HomelabHero can manage it, driven entirely from the chat/UI with no shell access and no password ever entering the conversation. Use this whenever Evan (or a user) asks to add, register, connect, onboard, or "hook up" a server, host, machine, NAS, node, or box, or says things like "add my truenas", "connect to my proxmox at 10.x.x.x", or "I have another Linux box to manage". Trigger it any time someone wants a new machine brought under management, even if they do not say the word "register".

2026-07-0756

backup-restore

serversathome/homelabhero

Understand and operate the homelab's snapshots and backups: how they work on each platform and how to take, list, verify, and restore/roll back safely. Use this whenever Evan asks to snapshot, back up, restore, roll back, or recover a VM, LXC, dataset, pool, config, or app; asks "can I undo this", "is there a backup", "how do snapshots work here", or "are the backups current"; or right before you propose a risky/destructive change and want to offer a snapshot as a safety net. Do NOT snapshot everything pre-emptively on every task - reach for this when recovery is the actual subject, or to offer one safety net before a specific dangerous operation.

2026-07-0756

deploy-app

serversathome/homelabhero

Stand up a NEW containerized app or compose stack on a docker host. Use whenever Evan wants to deploy, install, add, spin up, or "set up" a new container or stack (Jellyfin, Radarr, Sonarr, qBittorrent, Immich, a new arr app, a dashboard, etc.), or add a service to an existing stack. For fixing or operating an app that already exists, use docker-stack-ops instead; for updating images, use patch-management.

2026-07-0756

name

host-ops

description

Host ops (Linux)

Confirm the target with hh list, then read capabilities/linux.md for the full toolset. Diagnose read-only first, then propose changes and confirm before anything state-changing.

Fast path

hh run <alias> "systemctl --failed"                       # failed units first
hh run <alias> "uptime; free -h; df -h"                   # pressure + space
hh run <alias> "ss -tulpn"                                 # what is listening
hh run <alias> "journalctl -p err -b --no-pager | tail -40"

Common cases

Service down: check status and logs, restart (confirm), re-verify.
Disk full: find the heavy consumer with du -xh --max-depth=1 / before deleting anything. Never blind-delete.
Unreachable: usually network-diag, not the host. Confirm with hh test.
Broke after an update: check systemctl --failed, recent journalctl -p err, and whether a reboot is pending (ls /var/run/reboot-required on Debian/Ubuntu).

Containers on the host

If it runs Docker, hh run <alias> "docker ps" and the docker-stack-ops skill take over for container-level work.