One-click install
npx skills add https://github.com/anajuliabit/aeon --skill evening-recap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Evening Recap
Source: https://github.com/anajuliabit/aeon/tree/main/skills/evening-recap
Command: npx skills add https://github.com/anajuliabit/aeon --skill evening-recap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It solves the problem of end-of-day operational ambiguity by turning raw run logs into a clear verdict about what was shipped, what failed, and what requires human follow-up.

Core Features & Use Cases

  • Actionable TL;DR verdict: Produces a single stance sentence summarizing the day’s net outcome (wins and regressions) so operators don’t have to interpret logs.
  • Log + cron-state cross-checking: Detects silent failures and “ran without logging” situations by combining memory/logs/... with memory/cron-state.json.
  • Decision-ready recap: Surfaces concrete tomorrow actions (merge pending PRs, investigate failing skills, resolve open issues) with artifact links for fast review.
  • Use Case: Morning/PM-style oversight for autonomous operations where you run many skills unattended and need a trustworthy operator summary without approval loops.

Quick Start

Use the Evening Recap skill to generate an end-of-day summary by setting the optional date override var to a specific UTC date if you want to recap a past day.

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 for autonomous agent runs?

A daily operational recap is generated by reading dated memory logs and cross-checking cron-state to report what shipped, what failed, and what needs follow-up, sending the verdict via notify and appending the summary back into memory.

What is the best way to detect silent failures in autonomous agent cron runs?

Detecting silent failures in autonomous agent cron runs is done by cross-checking memory logs against cron-state.json to identify situations where jobs ran without logging, preventing operational ambiguity.

How does an end-of-day summary help with failure triage and incident prevention?

An end-of-day summary helps with failure triage by scoring and tiering log results, surfacing repeated entries and PR-driven decision points, and producing concrete tomorrow actions with artifact links for fast review.

Can I generate an operational summary for a past UTC date instead of today?

Yes, you can generate an operational summary for a past UTC date by setting the optional date override variable to a specific target date, allowing you to recap historical autonomous agent runs.

Does the recap include GitHub PR review and issue-driven decision points?

Yes, the recap includes GitHub PR review and issue-driven decision points by extracting URLs and paths per log entry, surfacing concrete actions like merging pending PRs or resolving open issues.