agentleFS
seayniclabsseayniclabs/homelab-infra-mcp/skills/homelab-health-check/SKILL.md

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.

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
  1. Distinctive:

    Run these in order. Skip any step whose module is off, and record the skip in the table.

    line 15
  2. Very specific:

    Modules: Call homelab_modules. Note which modules are on.

    line 17
  3. Very specific:

    Connectivity: Call homelab_health. Record each enabled module's result.

    line 18
  4. Very specific:

    Overview: Call infrastructure_overview.

    line 19
  5. Very specific:

    Containers: Call docker_containers with action set to list.

    line 20
  6. Very specific:

    Certificates: Call proxy_certificates with action set to list.

    line 21
  7. Very specific:

    Uptime monitors: When the uptime module is on, call uptime_monitors with action set to list.

    line 22
  8. Very specific:

    DNS filtering: When the dns_filter module is on, call dns_filter_status.

    line 23
  9. Distinctive:

    If nothing needs attention, say so in one line under the table.

    line 44
  10. Distinctive:

    Never change a container, proxy host, certificate, DNS record, monitor or filter rule during this sweep.

    line 48
  11. Distinctive:

    Never print a secret value.

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

  1. Modules. Call homelab_modules. Note which modules are on.
  2. Connectivity. Call homelab_health. Record each enabled module's result.
  3. Overview. Call infrastructure_overview. Record the counts it returns across Docker, the proxy and DNS.
  4. Containers. Call docker_containers with action set to list. Read every page: repeat the call with offset until a page is shorter than limit. Flag each container that is restarting, unhealthy, or exited.
  5. Certificates. Call proxy_certificates with action set to list. Flag each certificate that expires within 14 days of today. Give the domain and the number of days left.
  6. Uptime monitors. When the uptime module is on, call uptime_monitors with action set to list. Flag each monitor that is down or paused. Read every page.
  7. DNS filtering. When the dns_filter module is on, call dns_filter_status. Record whether filtering is on and the query and block totals it returns.

Report

Lead with one table. One row per check.

CheckResultNotes
Modules3 on, 5 offOff: home_assistant, uptime, tunnel, dns_filter, sso
Connectivity3 of 3 reachabledocker reports the socket is reachable
Containers22 running, 1 restartingwiki-app restarting
Certificates4 valid, 1 expires in 9 daysphotos.example.com, 9 days
Uptime0 downSkipped: module off
DNS filteringSkippedModule 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, then containers.
  • A certificate that expires within 14 days: homelab-troubleshooting. Renewal is proxy_certificates with action set to request, which needs approval.
  • A down uptime monitor: homelab-troubleshooting for 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 its Fix: line, and continue with the other checks.
  • Never print a secret value. Settings appear by name only.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.