Connor Rhodes
451b9459d2
Each skill is now a folder with a SKILL.md inside. Added skill-creator skill with full eval tooling. Updated skill index and cross-references. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
62 lines
1.9 KiB
Markdown
62 lines
1.9 KiB
Markdown
---
|
|
name: daily-briefing
|
|
description: Generate a morning briefing with your calendar, tasks, deadlines, and anything else you need to start the day.
|
|
triggers:
|
|
- run my briefing
|
|
- morning briefing
|
|
- what's my day look like
|
|
- what's on deck
|
|
---
|
|
|
|
# Daily Briefing
|
|
|
|
Produce a morning overview so you know what matters today.
|
|
|
|
## When to Use
|
|
|
|
Run this at the start of your day. One command, full daily picture.
|
|
|
|
## Instructions
|
|
|
|
1. Check today's calendar events (if calendar MCP is connected).
|
|
2. Review any active projects or tasks in the workspace.
|
|
3. Check for approaching deadlines (today, tomorrow, this week).
|
|
4. Note any items that are past due.
|
|
5. Produce a formatted briefing.
|
|
|
|
### Output Format
|
|
|
|
**Daily Briefing — [Date]**
|
|
|
|
**Today's Schedule**
|
|
[List of calendar events with times. If no calendar connected, note "Calendar not connected — add events manually or set up a calendar MCP connector."]
|
|
|
|
**Active Projects**
|
|
[List of current projects or tasks in progress, with brief status for each.]
|
|
|
|
**Deadlines**
|
|
[Anything due today, tomorrow, or this week. Flag overdue items.]
|
|
|
|
**Notes**
|
|
[Anything else worth knowing — reminders, follow-ups, items from yesterday that need attention.]
|
|
|
|
## Customization Ideas
|
|
|
|
This is a starter briefing. As you use it, consider adding:
|
|
- Weather (requires a web search or weather API)
|
|
- A motivational or reflective quote
|
|
- Specific data from connected tools (email summary, Slack highlights, etc.)
|
|
- Sections for specific roles or modes of work
|
|
|
|
The assembler in Video 7 will help you customize this to your actual needs.
|
|
|
|
## Rules
|
|
|
|
- Keep it scannable. Use short lines and clear sections.
|
|
- Flag anything overdue or time-sensitive at the top of its section.
|
|
- Don't editorialize. Present facts. Let the reader decide priorities.
|
|
- If a data source isn't connected, say so rather than skipping the section silently.
|
|
|
|
---
|
|
|
|
*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 7 via the assembler.*
|