homelab-ops

DevOps Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Operate the homelab platform — start/stop services, backups, updates, disaster-recovery, and Docker management. Use when this ca…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Repository Layout”, “Docker Compose Commands”, “Platform Scripts”, “Start the entire platform”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name homelab-ops directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Repository Layout / Docker Compose Commands / Platform Scripts” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Homelab — Platform Operations

You can manage the homelab platform through shell scripts and Docker commands.

Repository Layout

The homelab repo lives at ~/homelab on the Mac mini. Key paths:

Path	Purpose
`scripts/platform-up`	Start all platform services (Caddy, Authentik…)
`scripts/app-up <app>`	Start a single app (e.g., `immich`)
`scripts/app-backup <app>`	Snapshot an app's volumes to backup dir
`scripts/app-update <app>`	Pull latest images and recreate an app
`scripts/dr-verify`	Verify disaster-recovery readiness
`platform/`	Platform service compose files
`apps/`	App compose files (immich, etc.)
`DESIGN.md`	Architecture reference
`docs/`	Operational procedures, runbooks, ADRs

Docker Compose Commands

All services use Docker Compose. Compose files live in their respective directories.

# List running containers
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"

# Restart a specific service
cd ~/homelab/platform/caddy && docker compose restart

# View logs (last 50 lines, follow)
docker compose -f ~/homelab/apps/immich/compose.yml logs --tail 50 -f

# Pull latest images for an app
cd ~/homelab/apps/immich && docker compose pull && docker compose up -d

# Check resource usage
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}"

Platform Scripts

Always use the provided scripts when they exist — they handle ordering, health checks, and logging.

Start the entire platform

~/homelab/scripts/platform-up

Starts services in dependency order: networking → Caddy → Authentik → Homepage → Dockge → Uptime Kuma.

Backup an application

~/homelab/scripts/app-backup immich

Creates a timestamped snapshot of all named volumes for the app. Backups go to the configured backup directory.

Update an application

~/homelab/scripts/app-update immich

Pulls latest images, recreates containers, verifies health.

Verify disaster recovery

~/homelab/scripts/dr-verify

Checks backup freshness, volume integrity, and restore readiness.

Service Quick Reference

Service	Directory	Network	Key Ports
Caddy	`platform/caddy`	caddy-net	80, 443
Authentik	`platform/authentik`	caddy-net	9000, 9443
PostgreSQL	`platform/authentik` (bundled)	authentik	5432
Redis	`platform/authentik` (bundled)	authentik	6379
Homepage	`platform/homepage`	caddy-net	3000
Dockge	`platform/dockge`	caddy-net	5001
Uptime Kuma	`platform/uptime-kuma`	caddy-net	3001
Immich	`apps/immich`	caddy-net + immich-internal	2283

Guidelines

Never run destructive commands (docker system prune, docker volume rm) without explicit confirmation and a fresh backup.
Prefer the platform scripts over raw docker compose commands — they handle dependency ordering.
When updating, always check docker ps after to verify containers are healthy.
The Caddy reverse proxy resolves *.home hostnames. If a service is unreachable, check Caddy first.
All compose files use restart: unless-stopped. Manual docker stop persists across reboots.

Source: briancunningham6/homelab — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: DevOps
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Manual integration
External API key: No requirement detected
Detected OS requirements: Docker
Runtime requirements: Docker
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview homelab-ops.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Homelab — Platform Operations

You can manage the homelab platform through shell scripts and Docker commands.

## Repository Layout

The homelab repo lives at `~/homelab` on the Mac mini. Key paths:

| Path                       | Purpose                                        |
| -------------------------- | ---------------------------------------------- |
| `scripts/platform-up`      | Start all platform services (Caddy, Authentik…) |
| `scripts/app-up <app>`     | Start a single app (e.g., `immich`)            |
| `scripts/app-backup <app>` | Snapshot an app's volumes to backup dir         |
| `scripts/app-update <app>` | Pull latest images and recreate an app          |
| `scripts/dr-verify`        | Verify disaster-recovery readiness              |
| `platform/`                | Platform service compose files                  |
| `apps/`                    | App compose files (immich, etc.)                |
| `DESIGN.md`                | Architecture reference                          |
| `docs/`                    | Operational procedures, runbooks, ADRs          |

## Docker Compose Commands

All services use Docker Compose. Compose files live in their respective directories.

```bash
# List running containers
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"

# Restart a specific service
cd ~/homelab/platform/caddy && docker compose restart

# View logs (last 50 lines, follow)
docker compose -f ~/homelab/apps/immich/compose.yml logs --tail 50 -f

# Pull latest images for an app
cd ~/homelab/apps/immich && docker compose pull && docker compose up -d

# Check resource usage
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}"
```

## Platform Scripts

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Repository Layout → Docker Compose Commands → Platform Scripts → Start the entire platform → Backup an application → Update an application
terms    -> Never run destructive commands · You can manage the homelab platform through shell scripts and Docker commands. · The homelab repo lives at ~/homelab on the Mac mini. · All services use Docker Compose. · Always use the provided scripts when they exist — they handle ordering, health checks, and logging. · Starts services in dependency order: networking → Caddy → Authentik → Homepage → Dockge → Uptime Kuma. · Creates a timestamped snapshot of all named volumes for the app. · Pulls latest images, recreates containers, verifies health.
files/cmd -> ~/homelab · scripts/platform-up · scripts/app-up <app> · immich · scripts/app-backup <app> · scripts/app-update <app> · scripts/dr-verify · platform/
body sha256 -> 98f975987eae