daily-brief

Generates daily or weekly briefs synthesizing email, calendar, chat, and vault notes.

Updated May 22, 2026
One-click install
npx skills add https://github.com/fbureau/second-brain --skill daily-brief-fbureau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily-brief
Source: https://github.com/fbureau/second-brain/tree/main/.claude/skills/daily-brief
Command: npx skills add https://github.com/fbureau/second-brain --skill daily-brief-fbureau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping track of everything that happened across email, calendar, chat, and documents each day is overwhelming, and important decisions, commitments, and weak signals get lost. This Skill automatically synthesizes all connected sources plus your Obsidian vault into a single actionable daily or weekly brief note. ## Core Features & Use Cases - Multi-source synthesis: Collects and triages email, calendar events, shared drive docs, and Slack/Teams chat, then distills them into a top-3-to-5 topic brief with linked sources. - Auto-orchestration: Automatically ingests whitelisted meeting transcripts, updates people notes with interaction logs, reconciles tasks with TODO.md, and triggers postmortems for reversed decisions. - Weekly review mode: Produces a synthesis-focused weekly note with cross-cutting themes, knowledge garden health checks, and an implicit plan for the next week. - Use Case: Schedule it as an end-of-day task so every evening you get a 01-daily/YYYY-MM-DD.md note with a TL;DR, decisions and commitments, pending follow-ups, and people touched — all linked back to source notes in your vault. ## Quick Start Ask Claude to generate my daily brief for today, pulling together my email, calendar, Slack, and vault activity into a daily note.

Frequently Asked Questions about daily-brief

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

FAQPage Schema
How do I generate a daily brief from email, calendar, and Slack?▼

Run the skill manually by saying "daily brief" or schedule it as an end-of-day task. It collects from connected sources via MCP tools, triages items into decisions, weak signals, and follow-ups, then writes a synthesized note to 01-daily/YYYY-MM-DD.md.

How does the daily brief handle meeting transcripts automatically?▼

Transcripts matching a calendar event with 2+ participants and 15+ minutes duration are auto-ingested with a needs-review flag, capped at 5 per run. Sensitive or unmatched transcripts are flagged for manual validation instead of being ingested.

Can the daily brief work with Slack as a primary communication channel?▼

Yes. Set primary-communication-channels in 00-inbox/MY-PROFILE.md to include slack or teams. Chat then gets broad collection and its own "Themes from Slack" section, aggregated by topic rather than individual messages.

What happens if the daily note already exists when the brief runs?▼

The skill appends rather than overwrites. It adds the brief at the top under a Daily brief heading while preserving existing sections like braindumps and ingested meetings written by other skills during the day.

What are the limitations of the daily brief on a first use?▼

With an empty vault, the brief runs in degraded mode using only external sources without vault cross-referencing. Value grows as the vault fills with people, project, and decision notes that the brief can link and synthesize.