connection-monitorlisted

Put a watch on your always-on agent so silence can never masquerade as success. Checks that the connections an unattended run depends on — MCP logins, the API/CLI it calls, the session itself — are actually alive, and pings you the moment one drops instead of letting you discover it hours later. Ships a runnable checker, a tiny local status page, and a quiet-until-it-matters watch loop with bounded escalation. Use when you've put an agent on a schedule and need to trust that it's still running, when a login silently expired mid-run, when a job "finished" but nothing actually happened, or when you want to be told the instant a connection breaks.
search-atlas-group/amm-founding-circle · ★ 0 · AI & Automation · score 72

Install: claude install-skill search-atlas-group/amm-founding-circle

# connection-monitor **The problem this solves:** you scheduled an agent to run overnight. In the morning the terminal is quiet, no errors, nothing red. You assume it worked. It didn't — one of its logins expired at 2am, every step after that did nothing, and you only find out at noon when the work you expected isn't there. That quiet terminal wasn't success. It was failure you couldn't see. An always-on agent is only "on" if it can *prove* it's still connected. The instant it loses a connection it depends on — an MCP login, the API key it calls, the model CLI, the session itself — it should tell you. Not tomorrow. Now. This skill is the **watch**. It does three things: 1. **Ground-truth liveness check** — it doesn't ask the agent "are you ok?" (a broken agent will happily say yes). It checks the real signals: is the login still valid, is the process still alive, has the run actually made progress. Silence is treated as *unknown*, never as success. 2. **A ping the moment something drops** — a desktop notification the second a connection breaks or a run stalls, so you learn it in real time instead of hours later. 3. **A tiny local status page** — one HTML file you can glance at that says, in plain colors, which connections are green and which are down, refreshed each check. It runs quiet. It only pings you when something actually changed or broke — never a stream of "still fine" noise. > This skill is a **companion to `night-shift`**. `night-shift` is the *contract* for