Menu
Add a new service to the Homepage dashboard. Use when a new container or VM has been set up on Proxmox and needs to be added to Homepage. Discovers IP and port automatically from the container.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run two heterogeneous fresh-context Herdr reviewers against both code quality and a governing plan, then synthesize evidence-backed feedback. Use when the user asks for a dual or adversarial review, code-versus-plan verification, or independent Claude and Pi reviewers before deciding whether a PR needs changes.
Control herdr from Codex. Use when the user says "use Herder" or asks to inspect, focus, prompt, spawn, or manage herdr workspaces, tabs, panes, or agents from a Codex session, without deciding whether they are inside or outside herdr.
Use when the user explicitly asks Codex Desktop or another shell outside Herdr to create, inspect, prompt, follow up with, or monitor Herdr agent tabs, or when the `codex-herdr` router skill hands off external control.
Fan out a user-provided task list into one reviewed PR per task through Herdr, then shepherd the PR fleet through CI and review without merging. Use when the user asks to fan out PRs, parallelize backlog items into separate PRs, or autonomously drive multiple agent-owned PRs to green.
Inspect and import content into my self-hosted AutoCaliWeb library. Use for catalog status, search, recent imports, shelves, metadata, or importing an ebook, comic, PDF, or audiobook.
Correct-by-construction TypeScript standards. Use for TypeScript engineering or when another skill needs the user's coding standards.
| name | homepage-add |
| description | Add a new service to the Homepage dashboard. Use when a new container or VM has been set up on Proxmox and needs to be added to Homepage. Discovers IP and port automatically from the container. |
| allowed-tools | Bash, Read, Edit, Write, AskUserQuestion |
Add services running on Proxmox to the Homepage dashboard (LXC 103).
Expects: <CTID> <service-name>
Example: /homepage-add 117 CommaFeed
If no arguments provided, ask the user for the container ID and service name.
ssh proxmox "pct exec <CTID> -- ip -4 addr show eth0" 2>/dev/null | grep inet | awk '{print $2}' | cut -d/ -f1
# Find non-system ports (excludes 22, 25, 111, etc)
ssh proxmox "pct exec <CTID> -- ss -tlnp" 2>/dev/null
Look for ports that are likely the service (typically 8000-9999 range, or well-known app ports).
ssh proxmox "pct exec <CTID> -- systemctl list-units --type=service --state=running" 2>/dev/null | grep -v systemd
Homepage runs on LXC 103. Config file:
/opt/homepage/config/services.yaml
Add entries under the appropriate section (Infrastructure, Documents & Books, Utilities, Media).
Basic entry (no widget):
- ServiceName:
icon: service-name.png
href: http://<IP>:<PORT>
description: Short description
proxmoxNode: pve
proxmoxType: lxc
proxmoxVMID: <CTID>
Homepage uses Dashboard Icons. Common patterns:
service-name.pngjellyfin.png, radarr.png, sonarr.png, adguard-home.pngssh proxmox "pct exec <CTID> -- ip -4 addr show eth0" and extract IPssh proxmox "pct exec <CTID> -- ss -tlnp" and identify service portssh proxmox "pct exec 103 -- cat /opt/homepage/config/services.yaml"ssh proxmox "pct exec 103 -- tee /opt/homepage/config/services.yaml > /dev/null"ssh proxmox "pct exec 103 -- grep -A6 <ServiceName> /opt/homepage/config/services.yaml"From the current config (ordered by card height):
The | indicates where widget cards end and no-widget cards begin.
Cards with widgets are taller than cards without. Homepage uses row-based layout, so mixing heights creates whitespace gaps.
Rule: Group cards by height within each section.
Example for Utilities (8 items, 3 columns):
When adding a new service:
proxmoxVMID without proxmoxTypeproxmoxVMID and proxmoxType: lxc