Install
$ agentstack add skill-jmagar-claude-homelab-homelab-health ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Homelab Service Health Dashboard
Run the health check script and present results as a clean dashboard.
Run the Check
bash ~/claude-homelab/skills/health/scripts/check-health.sh
Or from the plugin cache (when installed via Claude Code):
bash "${CLAUDE_PLUGIN_ROOT}/skills/health/scripts/check-health.sh"
Present the Dashboard
Parse the JSON output and display as a formatted table:
Service Health Dashboard
========================
Category Service Status URL
-------- ------- ------ ---
Media plex ✓ reachable https://plex.example.com:32400
radarr ✓ reachable https://radarr.example.com
sonarr ⚠ unreachable https://sonarr.example.com
overseerr ○ not configured
prowlarr ✓ reachable https://prowlarr.example.com
tautulli ✓ reachable https://tautulli.example.com
Downloads qbittorrent ✓ reachable https://qbit.example.com
sabnzbd ✓ reachable https://sabnzbd.example.com
Infrastructure unraid-server1 ✓ reachable https://unraid1.example.com/graphql
unraid-server2 ○ not configured
unifi ✓ reachable https://unifi.example.com
tailscale ✓ reachable (API)
Utilities gotify ✓ reachable https://gotify.example.com
linkding ✓ reachable https://links.example.com
memos ⚠ unreachable https://memos.example.com
bytestash ○ not configured
paperless ✓ reachable https://paperless.example.com
radicale ✓ reachable https://cal.example.com
Summary: 12 reachable · 1 unreachable · 5 not configured
Status Icons
| Icon | Status | Meaning | |------|--------|---------| | ✓ | reachable | URL responded (any HTTP code except timeout) | | ⚠ | unreachable | URL configured but timed out or connection refused | | ○ | not configured | No URL set in ~/.claude-homelab/.env |
Follow-Up Actions
After showing the dashboard, offer context-sensitive help:
- Unreachable services: "Want me to help diagnose
sonarr? I can check if the URL is correct or test the connection." - Not configured services: "You have 5 services not configured. Want to set them up now?" → offer to run
/homelab-core:setup - All reachable: "Everything looks good! All configured services are responding."
Refresh
If the user asks to recheck a specific service, re-run the script and filter the output for that service. Don't run the full check for a single-service query.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jmagar
- Source: jmagar/claude-homelab
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.