stable-daily-log

Reviews daily agent sessions and writes structured Obsidian daily log entries.

Updated May 28, 2026
One-click install
npx skills add https://github.com/patty-chow/the-stable --skill stable-daily-log-patty-chow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stable-daily-log
Source: https://github.com/patty-chow/the-stable/tree/main/skills/devops/stable-daily-log
Command: npx skills add https://github.com/patty-chow/the-stable --skill stable-daily-log-patty-chow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an agent system with multiple cron jobs and user sessions makes it hard to remember what actually changed each day. This Skill automates the nightly review of Hermes agent sessions, decides whether anything is worth recording, and writes a structured daily log to an Obsidian vault. ## Core Features & Use Cases - Session Review and Triage: Scans today's sessions via session_search, SQLite state.db queries, log files, and cron output directories to find what happened without reading full transcripts. - PROMOTE vs SILENT Decision Logic: Applies explicit criteria to decide whether the day merits a log entry (builds, decisions, bugs, real cron changes) or should be skipped silently. - Structured Obsidian Output: Writes or appends to ~/stable-memory/Daily/YYYY-MM-DD.md using a template with sections for what happened, decisions, things built, breakages, follow-ups, and context for tomorrow. - Use Case: A nightly 10 PM cron reviews the day's Bridge Keeper and Weekly Audit runs, detects that five bridge notes were updated, and appends a terse bulleted entry to today's daily log with wikilinks. ## Quick Start Run the daily log promoter to review today's sessions and write today's entry in ~/stable-memory/Daily/.

Frequently Asked Questions about stable-daily-log

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

FAQPage Schema
How do I automate a daily log from agent session history?▼

Schedule a nightly cron that lists today's sessions, inspects what changed using file modification timestamps and cron output files, then writes a templated Markdown entry to a daily notes folder. Sessions with no real changes are skipped silently.

How to query Hermes agent sessions with SQLite?▼

Query ~/.hermes/state.db with SELECT on the sessions table using columns id, title, source, started_at, and ended_at. Filter by Unix epoch boundaries computed with the correct local UTC offset, since SQLite strftime uses UTC midnight.

Why does session_search not show user sessions in browse mode?▼

Browse mode may return only the most recent cron sessions, omitting user sessions even when they exist. Fall back to querying state.db directly, scanning session filenames by date prefix, or grepping agent.log for today's activity.

How do I avoid reading large session transcripts over 100KB?▼

Check filesystem modification times on output directories first to see which files changed, then read only those files. If transcript reading is needed, use around_message_id scrolling with a small window instead of a full session dump.

Can execute_code be used in cron mode for this workflow?▼

No. execute_code is blocked by the cron approval policy, so all shell commands and data processing must run through terminal(). Use read_file plus shell pipelines for any file-based processing.