Daily Routine

To automate a morning briefing, this skill orchestrates sub-skills to aggregate GitHub issues, HN digests, token movers, and papers into a single consolidated summary. It operates standalone or within a chain, reading memory context to format and deliver the briefing.

An automated briefing avoids repetition by reading memory context from MEMORY.md and reviewing the last two days of memory logs. This historical context prevents the aggregation process from surfacing duplicate GitHub issues or HN digests in the current morning summary.

Yes, you can use this morning briefing skill as part of an automation chain by sharing prior step outputs via the chain context. It also supports standalone mode by invoking sub-skills inline, making it flexible for different orchestration workflows.

Generating an automated daily briefing requires token-movers, paper-pick, github-issues, and hn-digest sub-skills. It also requires access to memory context files like MEMORY.md and memory logs from the last two days to function properly and avoid content repetition.

The best way to consolidate token movers and academic papers is through automated orchestration. This skill aggregates multiple data streams, including GitHub issues and HN digests, reading memory context to filter duplicates and format a unified daily briefing.