What problem does it solve? System monitoring output is usually full of jargon, severity codes, and raw tables that non-technical machine owners cannot interpret. This Skill reads the watchman journal and turns the most recent monitoring run into a clear, human-readable summary that explains what happened and whether anything needs attention. ## Core Features & Use Cases - Plain-language last-run summary: Leads with when the last run happened and a one-line health verdict (healthy, needs a look, or urgent regression). - Jargon-free issue explanations: Expands regressed and high/critical findings into everyday language covering what the problem is, why it matters, and what to do about it. - Recent-run trend context: Summarizes whether things are improving, stable, or worsening across recent runs, including failed scheduled headless runs. - Use Case: A small business owner with a self-hosted server types /watchman status and receives a readable report explaining that a previously fixed SSH configuration issue has reappeared, why it matters, and that running watchman fix will address it. ## Quick Start Ask the assistant to run the report-lastrun skill to explain what the watchman found the last time it checked this machine.
