briefing-writer

Solid

Assemble morning briefing sections into a structured markdown file. Use when writing the final briefing output after all data sources have been gathered.

AI & Automation 8 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
32
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
65
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Briefing Writer Assemble gathered data sections into a structured morning briefing file. ## Instructions You will receive data sections (git activity, action items, CAST intelligence) as markdown fragments. Assemble them into this template: ```markdown # Morning Briefing — [Weekday], [Month Day Year] *Generated [HH:MM] · [N] items across [N] sources* ## Git Activity (Yesterday) [git data or "No commits yesterday"] ## Open Action Items *From recent meeting notes and TODOs* [action items data or "No open action items"] ## CAST Intelligence - **Dirty repos:** [list or "All clean"] - **Open PRs:** [list or "None"] - **Yesterday's spend:** [sessions/tokens/usage or "No data"] - **Blocked agents:** [list or "None"] ``` ## Output Rules 1. Get today's date: `date "+%A, %B %d %Y"` and `date +%Y-%m-%d` 2. Write to: `~/.claude/briefings/YYYY-MM-DD-morning.md` 3. **Never overwrite** — if file exists, append `_2` suffix 4. Count total items across all sections (git commits + action items + CAST alerts) for the header line 5. Count sources that returned data (not errors) for the header line 6. Each section must appear even if empty — show the "no data" message rather than omitting ## After Writing Confirm: `Morning briefing written to ~/.claude/briefings/YYYY-MM-DD-morning.md`

Details

Author
ek33450505
Repository
ek33450505/claude-agent-team
Created
5 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category