Daniel Rosehill Hey, It Works!
A Claude Code template for managing Proxmox servers
· Daniel Rosehill

A Claude Code template for managing Proxmox servers

A template repo with 38 slash commands and 10 agents for managing Proxmox and home servers through Claude Code CLI.

My home server runs on Proxmox and hosts a bunch of Docker containers, backup jobs, Cloudflare tunnels, and various other services. Managing all of that through SSH can get tedious, so I created the Claude Server Manager Template to turn Claude Code into a comprehensive server administration console.

danielrosehill/Claude-Proxmox-Manager-Template View on GitHub

38 slash commands for everything

The template packs 38 slash commands organized across several categories. System health and monitoring covers disk space, memory, CPU, uptime, boot analysis, service status, log review, and resource alerts. Storage and filesystem commands handle XFS health checks, RAID status, and disk usage analysis. Docker management includes container health checks, pruning, permission verification, and deployment tracking.

Networking commands cover LAN connectivity, NFS mounts, Cloudflare tunnel status, and port analysis. Security commands handle audits, firewall checks, and certificate monitoring. There are also commands for backup verification, GPU status, Proxmox VM management, system updates, and hardware benchmarking.

10 specialized agents

Beyond the slash commands, the template includes 10 subagents for complex workflows: a Docker troubleshooter, backup manager, log analyzer, service monitor, security auditor, performance optimizer, deployment manager, tunnel manager, storage manager, and a server documentarian that creates comprehensive documentation for debugging operations.

The deployment model is designed to be practical. You clone the repo, run a sync script that copies everything to where Claude Code expects it, and then run an interactive /claude-setup wizard that helps you customize everything for your specific server. The template was built around my particular setup with low-spec hardware and resource conservation in mind, but it's designed to be heavily customized for whatever you're running.

The suggested workflow is to create a private repo from the template for each machine you manage, keeping your server-specific configuration under version control. Check it out on GitHub.

danielrosehill/Claude-Proxmox-Manager-Template View on GitHub