Service Containers
Public Unreviewedby John Lauer
One dashboard for every Adom service container: what is healthy, what is down, why, and a restart button that runs the watchdog's own start command. Reads the watchdog's verdicts off disk, so it costs no extra probes and no vendor API quota.
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install john/svcwatchdev-skills/ or publish-skills/, so a contributor (or their AI) has no in-repo guide to build, debug, or publish it. Consider adding them; they stay source-only and never ship in the tarball.The Services dashboard for Adom service containers: which are healthy, which are down, why, and a restart that runs the watchdog's own start command. Reads the watchdog's on-disk verdicts, so it never re-probes a vendor API or spends quota. Use when someone asks whether their services are up, which one is down, why a service went down, or wants one restarted. Trigger words: are my services up, service containers, service dashboard, is mouser down, is digikey down, is jlcpcb down, service health, restart a service, why is my service down, svcwatch.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.