nightly-audit

Verifies logged agent actions against current home state and reports silent failures.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/moistalgia/hermes-tools --skill nightly-audit-moistalgia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nightly-audit
Source: https://github.com/moistalgia/hermes-tools/tree/main/skills-audited/skills/nightly-audit
Command: npx skills add https://github.com/moistalgia/hermes-tools --skill nightly-audit-moistalgia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Home automation agents can fail quietly — a light drops off the mesh, a thermostat setpoint gets reverted by another automation, a notification never arrives. This Skill catches those silent failures by re-reading the day's activity journal and verifying that every change the agent claimed to make still holds. ## Core Features & Use Cases - Journal Review: Reads the day's activity log via journal_review to enumerate every action the agent took. - State Re-Verification: Re-checks each logged house change with room_status and re-tests anything marked partial or failed. - Capture Inbox Check: Flags unfiled items sitting in capture_pending for more than a day as a system-level problem. - Quiet-by-Default Reporting: Sends nothing on a clean night; notifies through notify at low priority only when something is actually wrong, and never silently re-applies reverted changes. - Use Case: At 11pm the audit finds the kitchen under-cabinet light has been unavailable since 6pm and the upstairs setpoint drifted from 68 back to 64 — it sends one factual low-priority message instead of waking anyone. ## Quick Start Run the nightly audit to review today's journal, verify every house change still holds, and notify me only if something is wrong.

Frequently Asked Questions about nightly-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my home automation agent actually did what it claimed?▼

Run the nightly audit routine: read the day's activity journal, then re-check each logged house change against current room status. Any mismatch between the logged action and present state is reported as a finding.

How to detect silent failures in Home Assistant automations?▼

Compare the agent's journal entries against live device state with room_status, and re-test anything logged as partial or failed. Devices that dropped off the mesh or setpoints reverted by other automations surface as discrepancies.

Does the nightly audit send a notification every night?▼

No. It sends nothing on a clean night to avoid notification fatigue. It only notifies through the notify channel when something is actually wrong, and always at low priority so it waits until morning.

Will the audit automatically fix state that has drifted?▼

No. The audit reports drifted state but never re-applies changes, because a reverted setting may have been changed by a person. It states what changed and offers to act instead.

Can I use the journal to answer why a light or thermostat is in a certain state?▼

Yes. Check journal_review before answering and quote the logged entry with its time. If there is no record, say so plainly rather than reconstructing a plausible story, since the change came from someone or something else.