Daily Routine

Aggregate token movers, papers, GitHub issues, and HN digests into a morning briefing.

Updated Jun 2, 2026

Search Tags:#automation #orchestration #briefing #daily #github-issues #memory-context #hn-digest

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill daily-routine-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Daily Routine
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/daily-routine
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill daily-routine-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling a daily briefing from multiple data sources (token movers, tweets, papers, GitHub issues, and HN digests) is time-consuming and error-prone; this skill automates the aggregation and summarization to save time and reduce cognitive load.

Core Features & Use Cases

Orchestrates the token-movers, paper-pick, github-issues, and hn-digest sub-skills to produce a consolidated briefing.
Supports running as part of a chain (sharing prior step outputs via the chain context) or standalone by invoking sub-skills inline and reading memory for context.
Reads memory/MEMORY.md for context and reviews the last two days of memory/logs to avoid repetition, then formats and sends the briefing via a notification mechanism.

Quick Start

Run the Daily Routine skill in a chain or standalone to generate a morning briefing by executing token-movers, paper-pick, github-issues, and hn-digest.

Frequently Asked Questions about Daily Routine

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

FAQPage Schema

How do I automate a daily morning briefing from GitHub issues and HN digests?▼

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.

How does an automated briefing avoid repeating information from previous days?▼

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.

Can I use this morning briefing skill as part of an existing automation chain?▼

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.

What data sources are required to generate an automated daily briefing?▼

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.

What is the best way to consolidate crypto token movers and academic papers into one summary?▼

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.