morning

Aggregate project health, handoffs, inbox, session history, and git activity into a daily briefing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill morning-jyhthegreat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morning
Source: https://github.com/JYHTHEGREAT/jyh-system/tree/main/skills/morning
Command: npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill morning-jyhthegreat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered per-project statuses, handoff summaries, second-brain inbox items, session history, and recent git activity into a single daily briefing so you no longer need to manually check multiple files and repositories each morning.

Core Features & Use Cases

  • Zero-Config operation: Runs without explicit user profiles and still produces a useful briefing.
  • Degraded Mode resilience: Reads each data source independently so failures in one source do not block the overall report.
  • Multi-source aggregation: Collects a projects registry, handoff files, second-brain inbox counts and aging, session synchronization stats, and per-project git summaries.
  • Variable Insight selection: Chooses a daily "variable reward" insight based on the date and inbox/execution metrics.
  • Local-only, audit-friendly: Appends execution entries to a local daily-log and is intended for desktop/local task execution only.

Quick Start

Invoke the morning skill by running /morning to generate a consolidated daily briefing summarizing projects, yesterday's summary, today's priorities, inbox status, git activity, and one variable insight.

Frequently Asked Questions about morning

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

FAQPage Schema
How do I get a consolidated daily briefing across multiple local git projects?

A daily briefing consolidates scattered project statuses, handoff notes, and recent git activity into a single report. It aggregates per-project git summaries and second-brain inbox items without requiring manual checks across multiple local repositories each morning.

What is the zero-config daily briefing mechanism for local developer environments?

The zero-config briefing mechanism runs without explicit user profiles to produce a useful daily report. It reads local project registries, handoff files, and session history independently, ensuring a failure in one data source does not block the overall aggregation.

How do I aggregate per-project handoff notes and second-brain inbox items?

You aggregate handoff notes and second-brain inbox items by invoking a consolidated morning briefing. It collects per-project handoff files alongside inbox counts and aging metrics, providing a unified view of local developer environment statuses.

Does the daily briefing work with local git repositories when offline or missing dependencies?

Yes, the daily briefing operates in a degraded mode that reads each data source independently. This resilience means missing local git repository data or failed source reads will not block the generation of the remaining project briefing.

Can I track execution logs for daily cross-project git summaries locally?

Yes, you can track execution logs locally because the briefing appends execution entries to a local daily-log file. This audit-friendly approach ensures desktop task execution and variable daily insight selections are recorded without external dependencies.

What is the best way to summarize project health and recent git activity for multiple Claude projects?

The best way to summarize project health is using a daily cross-project briefing that aggregates session synchronization stats and per-project git summaries. It selects a variable daily insight based on date and inbox metrics to provide a consolidated overview.