From claudeclaw
Produce a single-screen morning briefing. Triggers when the user says "morning brief", "what's on today", "daily standup", or when the cron entry for it fires. Pulls from calendar, inbox, open PRs, and yesterday's memory.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudeclaw:morning-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A one-screen summary the user reads with their first coffee.
A one-screen summary the user reads with their first coffee.
mcp__1720c808-...__list_events for today).mcp__c2943664-...__search_threads with is:unread is:important newer_than:1d).gh pr list --search "review-requested:@me OR assignee:@me" --state open.MEMORY.md in the last 24h (use git log -p on the identity folder if it's tracked, otherwise scan).If a source is unavailable (MCP not installed, gh not authenticated), skip it silently — don't pad the brief with apologies.
Strict template. Five sections, max one screen:
☀️ Morning brief — {weekday}, {date}
📅 Today
• {time} — {event title}
• {time} — {event title}
📬 Inbox (top 3)
• {sender}: {subject}
• …
🔧 Open PRs
• {repo}#{num}: {title} — {state}
🧠 From yesterday
• {one-line memory note that's still load-bearing}
🎯 Suggested first move
{one sentence, action-oriented}
If a section is empty, omit it entirely (no "📬 Inbox: nothing").
Pick the single highest-leverage thing for the day. Use these rules:
MEMORY.md for today → that.USER.md.By default the brief renders in the Claude Code conversation. If the user has the messaging gateway set up (see docs/messaging-gateway.md), the cron entry can deliver it to Telegram/WhatsApp/etc. instead.
npx claudepluginhub leadsblender/claudeclaw --plugin claudeclawCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.