Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

homelab-overview

Étoiles0

Forks0

Mis à jour29 juin 2026 à 20:30

Orientation for the homelab-assist plugin suite — what plugins and skills exist (Proxmox, Docker), how they relate, and how to route a homelab request to the right skill. Load this when the user makes a broad homelab request, when you're unsure which homelab skill applies, or when a task spans both Proxmox and Docker.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Redth

Redth/homelab-assist

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	homelab-overview
description	Orientation for the homelab-assist plugin suite — what plugins and skills exist (Proxmox, Docker), how they relate, and how to route a homelab request to the right skill. Load this when the user makes a broad homelab request, when you're unsure which homelab skill applies, or when a task spans both Proxmox and Docker.

Homelab-assist: orientation & routing

This suite helps you manage a homelab through Claude Code. It is API-first and safety-gated. Start here when a request is broad or spans layers.

The plugins

homelab-core (this plugin) — the conventions every other skill defers to:
- homelab-safety — change-approval + SSH-confirmation policy. Apply before any change or SSH drop.
- homelab-ssh — the execution discipline for any work done over SSH (host identity, backup/rollback, validate-before-apply, dangerous-command guardrails, lockout avoidance). Load it whenever a task will run shell commands or edit files on a host.
- homelab-secrets — store/retrieve credentials in the OS-native secret store (Keychain / Credential Vault / libsecret / pass) and handle SSH keys. Load it whenever a task needs a token, password, or SSH credential.
- homelab-research — find version-correct canonical docs before acting on anything non-obvious.
proxmox — manage Proxmox VE. Start at proxmox:proxmox-overview, which routes to VM/LXC/storage/ backup/update skills (REST API) and to proxmox-host-config (SSH-level: GPU passthrough, idmap, network).
docker — manage Docker compose stacks. Start at docker:docker-overview, which routes to Dockhand (primary), Portainer, Dockge, the shared compose skill, NPM reverse-proxy label routing, and the Docker-on-Proxmox networking/storage skill.

Routing a request

Always load the safety policy before changing anything, and research the version before acting on anything you're unsure about.
Identify the layer:
- Hypervisor / VM / LXC / passthrough / cluster / PVE backups → proxmox plugin.
- Containers / compose stacks / reverse proxy / container networking → docker plugin.
- Spanning both (e.g. "my Docker LXC can't see the NFS share" or "set up a VLAN for my Docker host") → start with docker:docker-on-proxmox, which bridges the two.
Drill into the specific task skill from the plugin's overview.

Cross-layer awareness

The homelab is a stack: a Docker host is often a Proxmox VM or LXC (privileged or unprivileged), with VLAN-tagged networking and passed-through storage. Problems frequently cross the boundary — a container that "can't reach the network" may actually be a Proxmox bridge/VLAN issue; a "permission denied" on a bind mount may be an unprivileged-LXC idmap issue. When debugging, consider both layers and use docker:docker-on-proxmox to reason about how they interact.

The two rules that never bend

Confirm before significant/destructive changes and before any SSH drop (homelab-safety).
Be version-correct — check the running version and canonical docs before acting (homelab-research).

Plus depuis ce dépôt

même dépôt

dockhand

Redth/homelab-assist

Manage Docker via Dockhand — the preferred control plane in this homelab — and its Hawser remote agents. Covers the Dockhand architecture (central server + Hawser Standard/Edge agents), how to drive it (the mcp-dockhand MCP server or its REST API), compose-stack and container operations, multi-host/environment targeting, and Git-synced stacks. Load this when the user manages Docker with Dockhand.

2026-07-010

docker-compose-stacks

Redth/homelab-assist

Shared foundational knowledge for working with Docker Compose stacks — the compose file format, services/networks/volumes/secrets, environment and .env handling, healthchecks, common operations (up/down/pull/logs/ps), and safe-change practices. Load this for any compose-based work, alongside the control-plane skill (Dockhand/Portainer/Dockge) that actually applies the changes.

2026-06-290

docker-on-proxmox

Redth/homelab-assist

Understand and troubleshoot a Docker host running inside Proxmox — as a VM or as a privileged/unprivileged LXC — and how VLAN networking, macvlan/ipvlan, VLAN-aware bridges, and passed-through/bind-mounted storage interact across the Proxmox and Docker layers. Load this when a Docker networking or storage problem may originate at the Proxmox layer, or when planning how to host Docker on Proxmox.

2026-06-290

docker-overview

Redth/homelab-assist

Entry point and router for managing Docker in a homelab. Load this first for any Docker request — it identifies which control plane is in use (Dockhand preferred, or Portainer/Dockge/raw Engine), establishes the version check, and routes to the right skill (compose stacks, Dockhand, reverse-proxy label routing, or Docker-on-Proxmox networking).

2026-06-290

dockge

Redth/homelab-assist

Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

2026-06-290

npm-reverse-proxy

Redth/homelab-assist

Set up and manage domain routing for homelab services using nginx-proxy-manager (NPM) driven by Docker container labels via npm-docker-sync. Load this when the user wants to expose a container/stack at a domain, debug why a service isn't routing, or understand the label-based proxy-host automation pattern. Covers the npm.* label scheme, how sync maps containers to NPM proxy hosts, and SSL/forced-host details.

2026-06-290

name	homelab-overview
description	Orientation for the homelab-assist plugin suite — what plugins and skills exist (Proxmox, Docker), how they relate, and how to route a homelab request to the right skill. Load this when the user makes a broad homelab request, when you're unsure which homelab skill applies, or when a task spans both Proxmox and Docker.

Homelab-assist: orientation & routing

This suite helps you manage a homelab through Claude Code. It is API-first and safety-gated. Start here when a request is broad or spans layers.

The plugins

homelab-core (this plugin) — the conventions every other skill defers to:
- homelab-safety — change-approval + SSH-confirmation policy. Apply before any change or SSH drop.
- homelab-ssh — the execution discipline for any work done over SSH (host identity, backup/rollback, validate-before-apply, dangerous-command guardrails, lockout avoidance). Load it whenever a task will run shell commands or edit files on a host.
- homelab-secrets — store/retrieve credentials in the OS-native secret store (Keychain / Credential Vault / libsecret / pass) and handle SSH keys. Load it whenever a task needs a token, password, or SSH credential.
- homelab-research — find version-correct canonical docs before acting on anything non-obvious.
proxmox — manage Proxmox VE. Start at proxmox:proxmox-overview, which routes to VM/LXC/storage/ backup/update skills (REST API) and to proxmox-host-config (SSH-level: GPU passthrough, idmap, network).
docker — manage Docker compose stacks. Start at docker:docker-overview, which routes to Dockhand (primary), Portainer, Dockge, the shared compose skill, NPM reverse-proxy label routing, and the Docker-on-Proxmox networking/storage skill.

Routing a request

Always load the safety policy before changing anything, and research the version before acting on anything you're unsure about.
Identify the layer:
- Hypervisor / VM / LXC / passthrough / cluster / PVE backups → proxmox plugin.
- Containers / compose stacks / reverse proxy / container networking → docker plugin.
- Spanning both (e.g. "my Docker LXC can't see the NFS share" or "set up a VLAN for my Docker host") → start with docker:docker-on-proxmox, which bridges the two.
Drill into the specific task skill from the plugin's overview.

Cross-layer awareness

The two rules that never bend

Confirm before significant/destructive changes and before any SSH drop (homelab-safety).
Be version-correct — check the running version and canonical docs before acting (homelab-research).