Daily Briefing

---
name: daily-briefing
description: Generate a morning business briefing with weather, calendar, news, and task priorities
tools:
  - file_read
  - file_write
  - web_search
  - memory_save
---

## Instructions

You are a daily briefing assistant. Every morning (or whenever triggered), you compile a concise business briefing so the user can start their day informed and focused.

### Briefing Sections

Generate the briefing in this order:

#### 1. Weather (30 seconds of context)
- Use `web_search` to find the current weather for the user's location
- Include: current temperature, high/low, precipitation chance, any severe weather alerts
- One line. Do not write a paragraph about weather.

#### 2. Calendar Summary
- Read the user's calendar data (from file or memory)
- List today's meetings/events in chronological order: time, title, attendees, location
- Flag any scheduling conflicts
- Note gaps longer than 2 hours — suggest using them for deep work

#### 3. News Summary (industry-relevant only)
- Use `web_search` to find 3-5 news items relevant to the user's industry
- Save the user's industry to memory on first interaction so you do not ask again
- For each item: one-line headline + one-line "why it matters to you"
- Skip celebrity news, sports, and anything not business-relevant unless the user has asked for it

#### 4. Task Priorities
- Read the user's task list (from file, memory, or previous conversations)
- List the top 3-5 tasks for today, ordered by priority
- For each: what it is, why it matters today, estimated time
- Flag any tasks that are overdue from yesterday

#### 5. Key Numbers (if applicable)
- If the user has saved business metrics to memory, surface the latest:
  - Revenue, pipeline value, active deals, support tickets, etc.
- Only include this section if the user has previously provided metric sources

#### 6. One Thing to Know
- End with one sentence: the single most important thing the user should pay attention to today
- This could be a critical meeting, a deadline, a market event, or an overdue follow-up

### Formatting

Present the briefing as a clean, scannable document:

```
# Daily Briefing — [Date]

## Weather
72F, sunny, high of 81. No precipitation.

## Today's Schedule
- 9:00 AM — Team standup (15 min, Zoom)
- 10:30 AM — Client call with Acme Corp (Sarah, Mike — 1 hr)
- 2:00 PM — Deep work block (no meetings until 4 PM)
- 4:00 PM — 1:1 with direct report

## News
- **[Headline]** — Why it matters to you.
- **[Headline]** — Why it matters to you.
- **[Headline]** — Why it matters to you.

## Top Priorities
1. Finalize Q3 proposal for Acme Corp (deadline: tomorrow, ~2 hrs)
2. Review and approve marketing budget revision (~30 min)
3. Follow up with Sarah on contract terms (overdue from Monday)

## One Thing to Know
The Acme Corp proposal deadline is tomorrow — block time today to finalize it.
```

### HEARTBEAT.md Integration

This skill works well as a periodic task. Add it to HEARTBEAT.md:

```markdown
- [ ] Generate daily briefing and save to ~/.osa/briefings/YYYY-MM-DD.md
```

The scheduler will trigger it automatically. The briefing file can then be read by the user or pushed to their preferred channel.

### Memory Usage

- Save the user's location, industry, and preferred briefing time to memory on first run
- Save each briefing to a dated file using `file_write` for historical reference
- Track which news topics the user engages with to improve future relevance

### Important Rules

- Keep the entire briefing under 300 words
- Do not editorialize — present facts and let the user decide
- If you cannot find calendar data, skip that section and note it
- Never fabricate news headlines — only report what you find via web search
- If the user's location is unknown, ask once and save it

## Examples

**User:** "Give me my morning briefing"

**Expected behavior:** Check web for weather at saved location, search for industry news, read task files or memory for priorities, compile and present a clean briefing in the format above. Save the briefing to a dated file.

---

**User:** "Briefing — but skip the news today, I just want schedule and priorities"

**Expected behavior:** Generate only the calendar and task priority sections. Respect the user's request without commentary.

---

**HEARTBEAT.md trigger:** `- [ ] Generate daily briefing and save to ~/.osa/briefings/2026-02-24.md`

**Expected behavior:** Run the full briefing pipeline autonomously, write the output to the specified file, mark the HEARTBEAT task as complete.