القائمة
Query homelab infrastructure status — check UptimeKuma monitor uptime, get monitor summaries, and read ntfy topic messages (e.g., homelab-watchdog alerts). Use proactively when the user asks about server status, uptime, alerts, or infrastructure health.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full audit of the claude-remote project — fix OpenAPI schemas (t.Any → typed), align CLAUDE.md with reality, trim duplication from watchdog instructions, validate and deploy
Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).
Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.
Query GitHub — list repos, check notifications, view open PRs and issues, get recent activity. Calls the GitHub API via the claude-remote-api passthrough proxy (PAT is injected server-side). Use when the user asks about GitHub repos, PRs, issues, notifications, or code activity.
| name | homelab |
| description | Query homelab infrastructure status — check UptimeKuma monitor uptime, get monitor summaries, and read ntfy topic messages (e.g., homelab-watchdog alerts). Use proactively when the user asks about server status, uptime, alerts, or infrastructure health. |
| allowed-tools | Bash(curl:*) |
Queries the claude-remote-api which proxies UptimeKuma and ntfy. All requests go to $CLAUDE_REMOTE_API_URL with Authorization: Bearer $CLAUDE_REMOTE_API_SECRET.
curl -s -H "Authorization: Bearer $CLAUDE_REMOTE_API_SECRET" \
"$CLAUDE_REMOTE_API_URL/homelab/uptime-kuma/status"
# → { "up": 12, "down": 1, "paused": 2, "total": 15 }
curl -s -H "Authorization: Bearer $CLAUDE_REMOTE_API_SECRET" \
"$CLAUDE_REMOTE_API_URL/homelab/uptime-kuma/monitors"
# → UptimeKuma monitorList with heartbeat data
Always discover topics first, then fetch messages for each one:
# Step 1: list all subscribed topics
curl -s -H "Authorization: Bearer $CLAUDE_REMOTE_API_SECRET" \
"$CLAUDE_REMOTE_API_URL/homelab/ntfy/topics"
# → ["homelab-watchdog", "homelab-watchtower", "vps-watchtower", "uptime-alerts", "claude-remote", ...]
# Step 2: fetch messages for each topic
curl -s -H "Authorization: Bearer $CLAUDE_REMOTE_API_SECRET" \
"$CLAUDE_REMOTE_API_URL/homelab/ntfy/messages?topic=<topic>"
# → JSON array of recent messages on that topic
Never assume which topics exist — always call /homelab/ntfy/topics first.
1 = up, 0 = downactive: false means the monitor is paused (not a failure)id, time (Unix timestamp), event, topic, title, message, priority, tags