homelab-health-check
Skill0 starsChanged 21 days agoMITView on GitHub
Run a read-only sweep of the homelab across Homelab modules, containers, certificates, uptime monitors and DNS filtering, and report the results as one table. Use when the user asks for a health check, a status sweep, a morning check, or whether anything in the homelab needs attention. This skill never changes anything.
In this repository13 other files it gives its agents.
- architecture-diagramSkill
- cloudflare-oneSkill
- cloudflareSkill
- containersSkill
- dashmotionSkill
- diagramSkill
- expose-a-service-safelySkill
- fix-and-deploySkill
- getting-startedSkill
- homelab-troubleshootingSkill
- network-diagramSkill
- runbookSkill
- systematic-debuggingSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Run these in order. Skip any step whose module is off, and record the skip in the table.
- Very specific: line 17
Modules: Call homelab_modules. Note which modules are on.
- Very specific: line 18
Connectivity: Call homelab_health. Record each enabled module's result.
- Very specific: line 19
Overview: Call infrastructure_overview.
- Very specific: line 20
Containers: Call docker_containers with action set to list.
- Very specific: line 21
Certificates: Call proxy_certificates with action set to list.
- Very specific: line 22
Uptime monitors: When the uptime module is on, call uptime_monitors with action set to list.
- Very specific: line 23
DNS filtering: When the dns_filter module is on, call dns_filter_status.
- Distinctive: line 44
If nothing needs attention, say so in one line under the table.
- Distinctive: line 48
Never change a container, proxy host, certificate, DNS record, monitor or filter rule during this sweep.
- Distinctive: line 50
Never print a secret value.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Homelab health check
This sweep reads state and changes nothing. Every call below is a read or a list. Do not pass dry_run, and do not call any tool that changes a resource. If a problem needs a change, name the skill that fixes it and stop.
Steps
Run these in order. Skip any step whose module is off, and record the skip in the table.
- Modules. Call
homelab_modules. Note which modules are on. - Connectivity. Call
homelab_health. Record each enabled module's result. - Overview. Call
infrastructure_overview. Record the counts it returns across Docker, the proxy and DNS. - Containers. Call
docker_containerswithactionset tolist. Read every page: repeat the call withoffsetuntil a page is shorter thanlimit. Flag each container that is restarting, unhealthy, or exited. - Certificates. Call
proxy_certificateswithactionset tolist. Flag each certificate that expires within 14 days of today. Give the domain and the number of days left. - Uptime monitors. When the
uptimemodule is on, calluptime_monitorswithactionset tolist. Flag each monitor that is down or paused. Read every page. - DNS filtering. When the
dns_filtermodule is on, calldns_filter_status. Record whether filtering is on and the query and block totals it returns.
Report
Lead with one table. One row per check.
| Check | Result | Notes |
| Modules | 3 on, 5 off | Off: home_assistant, uptime, tunnel, dns_filter, sso |
| Connectivity | 3 of 3 reachable | docker reports the socket is reachable |
| Containers | 22 running, 1 restarting | wiki-app restarting |
| Certificates | 4 valid, 1 expires in 9 days | photos.example.com, 9 days |
| Uptime | 0 down | Skipped: module off |
| DNS filtering | Skipped | Module off |
Below the table, list the items that need attention, most severe first. For each item give the one next step and the skill that handles it:
- A container that is restarting or unhealthy:
homelab-troubleshooting, thencontainers. - A certificate that expires within 14 days:
homelab-troubleshooting. Renewal isproxy_certificateswithactionset torequest, which needs approval. - A down uptime monitor:
homelab-troubleshootingfor the service behind it.
If nothing needs attention, say so in one line under the table. Give the counts. Do not add advice the sweep did not find.
Rules
- Never change a container, proxy host, certificate, DNS record, monitor or filter rule during this sweep.
- Report a module that returns an error by its
homelab.<module>.<code>message and itsFix:line, and continue with the other checks. - Never print a secret value. Settings appear by name only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

