Evening Recap

Condense daily Aeon activity into an evening recap of shipped items, failures, and follow-ups.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill evening-recap-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Evening Recap
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/evening-recap
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill evening-recap-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Evening Recap synthesizes daily Aeon activity into a clear, actionable summary that highlights deployments, failures, and follow-up tasks for operators and stakeholders.

Core Features & Use Cases

  • Generate a TL;DR verdict of the day.
  • List shipped artifacts, blockers, and decisions for tomorrow.
  • Cross-check logs, cron-state, and memory artifacts to surface silent failures and ensure traceability across runs.

Quick Start

Ingest memory/logs and cron-state to produce today's recap.

Frequently Asked Questions about Evening Recap

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

FAQPage Schema
How do I generate an end-of-day operational recap from memory logs and cron-state files?

Generate an end-of-day operational recap by ingesting memory logs and cron-state.json to produce a concise summary of shipped artifacts, failures, and follow-up tasks. The recap cross-checks these sources to surface silent failures and ensure traceable accountability.

What is the best way to track daily blockers and decisions for tomorrow from automated runs?

Track daily blockers and decisions by cross-checking memory logs, cron-state checks, and memory artifacts to surface human-actionable decisions. This process validates data from memory/issues to ensure traceable accountability across runs.

How does an evening recap identify silent failures in cron-state and memory logs?

An evening recap identifies silent failures by cross-checking memory logs, cron-state.json, and memory artifacts. It reads and validates data from these sources to surface discrepancies and ensure traceable accountability for human-actionable decisions.

Can I use automated decision-tracking to condense daily activity into a TL;DR verdict?

Yes, automated decision-tracking condenses daily activity into a TL;DR verdict by highlighting what shipped, what failed, and what needs follow-up. It synthesizes memory logs and cron-state data into a clear, actionable summary for operators.

What data sources do I need to produce a daily summary of shipped artifacts and failures?

You need memory/logs, memory/cron-state.json, and memory/issues as data sources to produce a daily summary. The recap reads and validates these inputs to generate a concise overview of shipped artifacts, blockers, and decisions for tomorrow.