Evening Recap

Generate end-of-day operational recaps from local activity logs and cron-state data.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill evening-recap-aaronjmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Evening Recap
Source: https://github.com/aaronjmars/aeon/tree/main/skills/evening-recap
Command: npx skills add https://github.com/aaronjmars/aeon --skill evening-recap-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents operators from having to manually sift through logs to understand what shipped, what failed, and what needs human follow-up.

Core Features & Use Cases

  • Verdict-first end-of-day recap: produces a TL;DR stance plus tiered Headline/Notable/Blockers sections capped to keep the output readable.
  • Log + cron-state cross-checking: detects silent failures and “ran without logging” conditions by combining memory/logs/${TODAY}.md with memory/cron-state.json.
  • Actionable decision prompts: identifies merge-waits, persistent failures, unresolved issues, and conflicts so the operator knows exactly what to do next.

Quick Start

Use the Evening Recap skill to summarize a specific date by running it with a date override like 2026-05-27 so it generates a capped recap with sources and queued decisions.

Frequently Asked Questions about Evening Recap

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

FAQPage Schema
How do I generate a daily operational recap from agent activity logs?▼

To generate a daily operational recap, the skill parses memory/logs/${TODAY}.md headings and bodies, cross-checks cron-state data, and outputs a tiered summary of shipped outcomes, failures, and tomorrow's decisions.

How do I detect silent failures in autonomous agent runs?▼

Detect silent failures in autonomous agent runs by cross-checking local activity logs against memory/cron-state.json to identify missing entries, empty logs, and processes that ran without logging.

What is the best way to summarize cron monitoring data for operator decisions?▼

Summarizing cron monitoring data for operator decisions requires tiering log entries by leverage, extracting artifact paths, and producing actionable prompts for merge-waits and persistent failures.

Can I generate an end-of-day status report for a specific past date?▼

Yes, you can generate an end-of-day status report for a specific past date by running the skill with a date override like 2026-05-27 to parse that day's local activity logs.

Does this daily recap tool require external dependencies or components?▼

No external dependencies or components are required; the skill operates entirely by parsing local memory logs and cron-state JSON files to produce its operational summary.

Why are my agent status reports missing unresolved issues and conflicts?▼

Agent status reports miss unresolved issues when logs are not cross-checked with cron-state data; this skill surfaces conflicts and persistent failures by enforcing strict output rules and appending structured log entries.