c-briefing — Claude Code skill: your morning summary
Builds a morning briefing from the skills you already have installed: email, calendar, tasks, weather. Runs on demand or on a schedule via cron and launchd.
npx skills add daxaur/openpaw --skill c-briefing -a claude-codeWhat c-briefing does
The skill checks which other skills are present and pulls only from those. With c-email installed you get an unread count plus five recent subjects; c-calendar adds today's events and a look at tomorrow; c-tasks lists what is due and what is late. Sections for missing skills are skipped entirely.
Your name comes from SOUL.md or MEMORY.md. Output follows a fixed shape: date and weekday first, then emoji-headed blocks capped at five items each, with anything urgent pushed to the top. Ask for it in plain language whenever you want, or wire it to a schedule — a shell script calls claude --print and pipes the result into terminal-notifier, then cron or launchd fires it on weekday mornings at 8:00.
On macOS the scheduled path needs terminal-notifier present, otherwise the notification never appears even though the briefing itself is generated. The launchd example relies on lunchy-go, which you install separately.
What it helps with
- get one morning summary covering email and calendar
- spot overdue tasks before the workday starts
- check which PRs need review and where CI broke
- receive the briefing automatically on weekday mornings
- stop opening mail, calendar and issue tracker one by one
Example prompts for the agent
- Give me my daily briefing
- What's on my plate today?
- Run my morning briefing, urgent items first
How to install c-briefing
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-briefing -a claude-code2Manually: put the files in place
~/.claude/skills/c-briefing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/c-briefing/
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-briefing -a codex2Manually: put the files in place
.agents/skills/c-briefing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-briefing -a cursor2Manually: put the files in place
.cursor/skills/c-briefing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daxaur/openpaw c-briefing2Manually: put the files in place
.github/skills/c-briefing/SKILL.md1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-briefing -a gemini-cli2Platform CLI
gemini skills install https://github.com/daxaur/openpaw --path skills/c-briefingManually: put the files in place
.devin/skills/c-briefing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-briefing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about c-briefing
How do I install c-briefing in Claude Code?
Run npx skills add daxaur/openpaw --skill c-briefing -a claude-code; the skill file lands at ~/.claude/skills/c-briefing/SKILL.md.
What does c-briefing do?
It assembles a morning summary from the skills you have installed — unread mail, calendar events, tasks, notes, pull requests, deliveries. Only sections backed by an installed skill show up.
Can c-briefing run automatically every morning?
Yes. Point a script at claude --print with a briefing request, then schedule it with cron or launchd. The skill's example uses a weekday 8:00 cron entry and lunchy-go for launchd.
Source text
SKILL.md · MIT
---
name: c-briefing
description: Daily briefing — morning summary of email, calendar, tasks, weather. Can run on a schedule via launchd/cron.
tags: [briefing, daily, morning, summary, schedule]
---
# Daily Briefing
Compile a morning summary from your installed skills. Checks what's available and builds the briefing accordingly.
## What to Include
Check which skills are installed and pull from each:
| If installed | Include in briefing |
|---|---|
| c-email | Unread email count + top 5 subjects |
| c-calendar | Today's events + tomorrow preview |
| c-tasks | Due today + overdue items |
| c-notes | Recently modified notes |
| c-github | Open PRs, review requests, CI failures |
| c-slack | Unread DM count + mentions |
| c-tracking | Package delivery updates |
## Briefing Format
```
Good morning, {name}! Here's your briefing for {date}:
📧 Email: 12 unread — 3 flagged
→ "Q4 Budget Review" from Sarah
→ "Deploy approval needed" from CI Bot
→ "Lunch tomorrow?" from Mike
📅 Calendar:
→ 9:00 AM Team standup (30 min)
→ 11:00 AM 1:1 with Alex (45 min)
→ 2:00 PM Sprint review (1 hr)
✅ Tasks: 3 due today, 1 overdue
→ [overdue] Fix login bug
→ Write API docs
→ Review PR #234
🔔 Other:
→ 2 GitHub PRs need review
→ Package arriving today (Amazon)
```
## Scheduled Briefing
To run automatically each morning, set up a launchd job (macOS) or cron job:
```bash
# Create a briefing script
cat > ~/.claude/briefing.sh << 'SCRIPT'
#!/bin/bash
claude --print "Run my daily briefing using the c-briefing skill. Be concise." \
| terminal-notifier -title "Morning Briefing" -message "Ready" 2>/dev/null
SCRIPT
chmod +x ~/.claude/briefing.sh
# Schedule with cron (every weekday at 8:00 AM)
(crontab -l 2>/dev/null; echo "0 8 * * 1-5 ~/.claude/briefing.sh") | crontab -
# Or use lunchy-go for launchd (macOS)
lunchy-go install ~/.claude/briefing.plist
```
## Manual Briefing
Just ask Claude: "Give me my daily briefing" or "What's on my plate today?"
## Guidelines
- Read the user's name from SOUL.md or MEMORY.md
- Only include sections for skills that are actually installed
- Keep it concise — no section should exceed 5 items
- Flag urgent items at the top
- Include the date and day of week
© daxaur · MIT · daxaur/openpaw
