Morning Brief

Generate a priority-ranked daily brief from memory, logs, and cron-state signals.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill morning-brief-anajuliabit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Morning Brief
Source: https://github.com/anajuliabit/aeon/tree/main/skills/morning-brief
Command: npx skills add https://github.com/anajuliabit/aeon --skill morning-brief-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the time-consuming task of manually collecting context and deciding what matters today by producing a priority-driven briefing with clear “why now” rationales.

Core Features & Use Cases

  • Ranks focus items (max 3) using leverage × urgency from your memory, logs, open PRs/issues, cron failures, and scheduled skill triggers.
  • Adds only meaningful headlines from web search when they update priorities, introduce risks, or imply an action.
  • Sends and logs an audit trail by notifying via ./notify and appending a structured entry to memory/logs for continuity tomorrow.

Quick Start

Ask Aeon to run the Morning Brief for today and emphasize a specific area by setting var.

Frequently Asked Questions about Morning Brief

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

FAQPage Schema
How do I generate an autonomous daily morning brief for engineering and research tasks?

To generate a daily morning brief, the Skill reads MEMORY.md, log files, cron-state.json, and aeon.yml to select and score actionable focus items by leverage and urgency. It formats concise daily priorities and notifies you via ./notify.

How does priority ranking work for unattended agent workflows?

Priority ranking works by scoring focus items using leverage multiplied by urgency derived from repository work queues, cron failures, and scheduled skill triggers. It selects a maximum of three focus items to ensure decisions-ready context.

What is the best way to automate daily context collection from logs and repository monitoring?

Automating daily context collection involves parsing prior log files, open PRs, issues, and cron-state signals to produce priority-driven briefings. This eliminates manual context gathering by appending structured audit trails to memory/logs for continuity.

Do I need specific files like MEMORY.md and aeon.yml to run a scheduled skill trigger?

Yes, you need MEMORY.md, aeon.yml, prior log files, and cron-state.json to provide the necessary context for autonomous updates. The Skill reads these files to rank focus items and format the daily morning brief.

Can I emphasize a specific area when generating a priority-driven briefing?

Yes, you can emphasize a specific area by setting a variable when asking the agent to run the Morning Brief. This guides the priority ranking and selection of actionable focus items for that day.

Why does the daily brief include web search headlines alongside repository work queues?

The daily brief includes web search headlines only when they update priorities, introduce risks, or imply an action. This adds meaningful context to the priority-driven briefing derived from ongoing engineering and research activities.