Run any Skill in Manus with one click

compose-check

Stars0

Forks0

UpdatedJuly 2, 2026 at 19:52

Pre-deploy sanity check for Docker Compose stacks. Validates each compose file with `docker compose config` (read-only), then flags undefined interpolation variables and missing .env before the stack is brought up. Use before `docker compose up`, when editing a compose file, or whenever asked to validate or check a compose stack. Never brings stacks up or down.

Installation

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.

Run Skill in Manus

Source

chipi

chipi/agentic-ai-homelab

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	compose-check
description	Pre-deploy sanity check for Docker Compose stacks. Validates each compose file with `docker compose config` (read-only), then flags undefined interpolation variables and missing .env before the stack is brought up. Use before `docker compose up`, when editing a compose file, or whenever asked to validate or check a compose stack. Never brings stacks up or down.

compose-check

Catch a broken compose stack before docker compose up, not after. Validates syntax, interpolation, and env wiring — strictly read-only. This skill never runs up, down, pull, or anything that mutates a stack or shared state.

When this applies

Editing a docker-compose*.yml / compose.ya?ml, or about to deploy one, or asked to "check / validate the compose stack." Cheap; run it whenever in doubt.

Check each stack

Find stacks — docker-compose.yml, docker-compose.*.yml, compose.yml, compose.yaml (skip dated backups like *.yml.<date>). If none, say so.
Validate structure, then classify — for each file:
```
docker compose -f <file> config -q
```
A fresh checkout usually has no .env (gitignored, present only on the deploy host), so separate "not ready" from "broken":
- exit 0 → structure + interpolation valid → PASS
- fails only with env file ... not found → the YAML is fine, the stack just needs an .env absent from this checkout → ENV-MISSING (warn, name the exact path). Not a defect.
- any other error (YAML parse, additional property, bad interpolation, required variable is missing) → FAIL — surface the message.
Undefined interpolation — grep for ${VAR} used without a default or required marker (${VAR:-default} / ${VAR:?msg}). Any bare ${VAR} not set in the environment or an .env becomes an empty string at runtime. List them.
Env readiness — collect every .env path the stacks declare (top-level --env-file, service env_file:) and report which exist vs are missing. When a stack is ENV-MISSING and a sibling .env.example exists, the fix is cp .env.example .env (then fill secrets) — say that explicitly.

Report

Show full command output; end with one line per stack: COMPOSE CHECK <stack>: PASS | ENV-MISSING | FAIL.
On FAIL, name the defect (the YAML error or the undefined ${VAR}), not just the exit code. On ENV-MISSING, name the .env to create and the .env.example to copy from.

Conventions this enforces

Read-only. Validation only. Bringing stacks up/down, pruning volumes (down -v), or pulling images is out of scope and each needs explicit human approval anyway.
Never commit .env. Secrets live in .env, which stays gitignored. If a stack needs new vars, document them in an .env.example, not the real file.
Run stacks in place. Don't copy composes out to a scratch dir to check them — validate them where they live so the right .env and relative paths resolve.

More from this repository

same repository

close-arc

chipi/agentic-ai-homelab

Close a work arc — write the next docs/history/NNNN-<arc>.md continuity entry, update the history index and mkdocs nav, strike completed items in docs/wip/NEXT_STEPS.md, append any D-NNNN operational decisions to 0002-decisions.md, and suggest the version tag. Use when wrapping up a multi-step session or a milestone. Keeps the strict docs build green.

2026-07-020

dgx-status

chipi/agentic-ai-homelab

One-shot read-only health snapshot of the DGX host — GPU mode, GPU utilization and compute-app count, nvidia-smi memory and processes, and running containers. Use to answer "what is the DGX doing right now" before deploying, switching GPU mode, or debugging a stuck endpoint. Strictly read-only; never changes state.

2026-07-020

docs-preflight

chipi/agentic-ai-homelab

Validate that the docs site builds cleanly in strict mode before committing or pushing docs changes. Detects the project's docs toolchain (Makefile docs target, MkDocs, Sphinx, Docusaurus, mdBook) and runs its strict build, then reports PASS/FAIL with the exact unresolved refs or warnings. Use when about to commit or push changes under docs/, mkdocs.yml, or docs config, or whenever asked to check or validate the docs build.

2026-07-020

fleet-stats

chipi/agentic-ai-homelab

Show per-subagent invocation counts and token/cost spread by model tier from the current Claude Code transcript — proves whether the model-tiered fleet (haiku/sonnet/opus) actually spreads token cost. Use to see who was invoked, how often, tokens per agent/model, and escalation rate. Local and read-only (no Grafana/OTEL needed).

2026-07-020

gpu-mode

chipi/agentic-ai-homelab

Coordinate which vLLM owns the single DGX GPU before using a local vLLM endpoint. Checks the active mode (code/research/idle/BROKEN-BOTH) read-only, and switches only on explicit request. Use before pointing any tool at a local vLLM (http://<dgx>:9000/v1 or :8003/v1), when a vLLM call fails to connect, or when asked to bring the coder-next or autoresearch vLLM up or down. Switching is shared-state — never switch without explicit approval.

2026-07-020

homelab-endpoint

chipi/agentic-ai-homelab

Resolve a homelab service name to its real endpoint URL and how to call it — DGX host, vLLM coder-next/autoresearch slots, Ollama, observability labels. Use when an agent or client needs to point at a homelab service, when writing config that consumes one, or when asked "what's the URL for X". Read-only.

2026-07-020

name	compose-check
description	Pre-deploy sanity check for Docker Compose stacks. Validates each compose file with `docker compose config` (read-only), then flags undefined interpolation variables and missing .env before the stack is brought up. Use before `docker compose up`, when editing a compose file, or whenever asked to validate or check a compose stack. Never brings stacks up or down.

compose-check

When this applies

Editing a docker-compose*.yml / compose.ya?ml, or about to deploy one, or asked to "check / validate the compose stack." Cheap; run it whenever in doubt.

Check each stack

Find stacks — docker-compose.yml, docker-compose.*.yml, compose.yml, compose.yaml (skip dated backups like *.yml.<date>). If none, say so.
Validate structure, then classify — for each file:
```
docker compose -f <file> config -q
```
A fresh checkout usually has no .env (gitignored, present only on the deploy host), so separate "not ready" from "broken":
- exit 0 → structure + interpolation valid → PASS
- fails only with env file ... not found → the YAML is fine, the stack just needs an .env absent from this checkout → ENV-MISSING (warn, name the exact path). Not a defect.
- any other error (YAML parse, additional property, bad interpolation, required variable is missing) → FAIL — surface the message.
Undefined interpolation — grep for ${VAR} used without a default or required marker (${VAR:-default} / ${VAR:?msg}). Any bare ${VAR} not set in the environment or an .env becomes an empty string at runtime. List them.
Env readiness — collect every .env path the stacks declare (top-level --env-file, service env_file:) and report which exist vs are missing. When a stack is ENV-MISSING and a sibling .env.example exists, the fix is cp .env.example .env (then fill secrets) — say that explicitly.

Report

Show full command output; end with one line per stack: COMPOSE CHECK <stack>: PASS | ENV-MISSING | FAIL.
On FAIL, name the defect (the YAML error or the undefined ${VAR}), not just the exit code. On ENV-MISSING, name the .env to create and the .env.example to copy from.

Conventions this enforces

Read-only. Validation only. Bringing stacks up/down, pruning volumes (down -v), or pulling images is out of scope and each needs explicit human approval anyway.
Never commit .env. Secrets live in .env, which stays gitignored. If a stack needs new vars, document them in an .env.example, not the real file.
Run stacks in place. Don't copy composes out to a scratch dir to check them — validate them where they live so the right .env and relative paths resolve.