evening-recap

Solid

End-of-day operational summary — what Aeon shipped, what failed, what needs follow-up

AI & Automation 508 stars 166 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- autoresearch: variation B — reframe recap around tomorrow's decisions, lead with a TL;DR verdict, mandate links, cap to top items; folds in A's cron-state cross-check for silent failures and C's parser fix + source-health awareness --> > **${var}** — Optional date override (YYYY-MM-DD). If empty, recaps today (UTC). Read memory/MEMORY.md for context and `memory/issues/INDEX.md` for open issues. ## Goal The recap is not a log dump — the operator can read the log themselves. Its job is to deliver a verdict on the shape of the day and surface the calls that need a human. Lead with a one-sentence TL;DR; cap headlines; demand a URL on every shipped item; and never print empty sections. ## Steps 1. **Determine the date.** ```bash TODAY=${var:-$(date -u +%Y-%m-%d)} ``` 2. **Read today's activity log.** Open `memory/logs/${TODAY}.md`. - Treat **both** `## ` and `### ` as skill-entry headers (existing logs use both styles — `### autoresearch`, `## Changelog Skill`). Capture each heading text as the skill name and the body until the next heading. - If the file is missing or whitespace-only, mark `log=missing` and continue to step 3 — silent failures may still need reporting before exiting. 3. **Cross-check `memory/cron-state.json` for silent failures.** Load it as JSON. For each skill present: - `consecutive_failures ≥ 1` and `last_status != "success"` → silent failure (force into Blockers regardless of log content). - `last_success` date == TODAY but n...

Details

Author
aaronjmars
Repository
aaronjmars/aeon
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category