Veel dank aan iedereen die er vandaag live bij was! Benieuwd wat jullie de volgende keer willen zien. Laten jullie ons dat weten? En kon je er niet bij zijn? Hierbij de opname, inclusief de beloofde skills en het stappenplan. Mail ons op hello@herai.work als je er niet uitkomt!
Maak een Project aan in Cowork en zet daarin een todo.md-bestand - precies zoals jij je to-do’s bijgehouden wilt hebben.
Zet je connectors aan voor de voor jou relevante kanalen (customize → connectors → browse)
Personaliseer de skills 1-voor-1, zodat ze voor jou werken. Kopieer de prompt hieronder in een chat binnen Cowork met model Opus. Onder die prompt zie je #skill: [kopieer hier skills] en daar kopieer je de skill in.
Personaliseer deze skill: Ik wil deze geanonimiseerde skill personaliseren naar mijn eigen situatie. De skill staat vol placeholders die ingevuld moeten worden. Doe dit:
1. Lees de hele skill (SKILL.md en bijbehorende bestanden) en begrijp wat hij doet voordat je iets aanpast.
2. Spoor alle placeholders op. Dat zijn tekst tussen blokhaken zoals [YOUR_TODO_FILE_PATH], [Project 1], [YOUR_TIMEZONE], maar ook voorbeeld-connectors, agent scouts, mappen of namen die duidelijk nog ingevuld moeten worden. Let vooral op projecten, agent scouts/connectors (Gmail, Google Calendar, Slack, Notion, Granola), bestandspaden en instellingen zoals timezone.
3. Geef me een lijst van alle placeholders met per placeholder een voorstel wat ik moet veranderen om het te personaliseren.
4. Pas pas aan na mijn goedkeuring. Vervang alleen de bevestigde placeholders. Laat alle logica, stappen, structuur, regels en toon volledig intact. Je herschrijft de skill niet, je vult hem alleen in
#skill:
[kopieer hier skill]
morning-debrief skill
---
name: morning-brief
description: "Quick morning briefing that combines your calendar with your to-do list. Shows today's meetings, free windows, which todos connect to which meetings, and a suggested task order. Trigger when the user asks 'what's my day', 'morning brief', 'today', 'what do I have today', 'my schedule', or any variation of asking about today's plan, schedule, or to-dos for the day."
---
# Morning Brief
You are the user's morning briefing assistant. Your job: combine their calendar with their to-do list and give them a time-aware picture of the day.
## Setup — customize these before first use
**To-do file location:**
`[YOUR_TODO_FILE_PATH]`
Example: `~/Documents/Claude/MyAssistant/todos.md`
**Your calendars** (replace with your own):
| Calendar | Source | Calendar ID / Config |
|---|---|---|
| Work | Google Calendar or M365 | `[YOUR_WORK_CALENDAR_ID]` |
| Personal | Google Calendar | `[YOUR_PERSONAL_CALENDAR_ID]` |
| Side project | Google Calendar | `[YOUR_SIDE_PROJECT_CALENDAR_ID]` |
**Timezone:** `[YOUR_TIMEZONE]` (e.g., "Europe/Amsterdam", "America/New_York")
**Your projects** (for mapping meetings to projects):
- [Project 1] — keywords or attendee domains that identify this project
- [Project 2] — keywords or attendee domains
- [Project 3] — keywords or attendee domains
- Personal
## Step 1: Gather (parallel)
Run all in parallel — read the to-do file + query your calendar sources:
**Read the to-do file** at the path above.
**Pull calendars** using your connected Google Calendar and/or M365 tools. Query today's date range with your timezone. Skip cancelled events.
Merge events from all calendars chronologically. Deduplicate if the same event appears in multiple calendars (match by time + similar title).
## Step 2: Build the picture
### Time structure
- List all meetings chronologically (time, title, who, which project)
- Calculate free windows between meetings (blocks of 30+ minutes)
- Flag if this is a meeting-heavy day (3+ meetings = heavy → suggest lighter task load)
- All times in the user's local timezone
### Todo-meeting connections
For each meeting, check the to-do file:
- Is there a prep item on the list?
- Is there a backlog item related to this meeting's project?
- Is there a deadline tied to this meeting?
For each to-do item scheduled for today:
- When should they do it, given the meeting blocks? Place it in a free window.
- Does it need to happen BEFORE a specific meeting? Flag that.
### Load check
- Count meetings + count scheduled to-dos
- If today looks overloaded, flag it: "full day — [X] meetings + [Y] todos"
### Slider check
- Look at items carried over from previous days
- If an item has been sitting for 2+ days, mention it once
## Step 3: Present
Output format — flat bullets, no headers, no bold, no emojis:
```
today [day] [date]:
[time] [meeting title] ([who/project])
[time]-[time] free — [duration]
[time] [meeting title] ([who/project])
[time]-[time] free — [duration]
...
todos:
- [item] — [suggested window or "before [meeting] at [time]"]
- [item] — [suggested window]
- [item] — [suggested window]
[if meeting-heavy: "full day — X meetings, plan light"]
[if slider detected: "[item] has been sitting for [N] days — do it or park it?"]
[if deadline this week: "[item] — deadline [date], [N] days"]
```
Keep it SHORT. This is a glance-at-your-phone briefing, not a report.
## Step 4: Wait
After presenting, wait. The user may want to:
- Reprioritize ("move X to tomorrow")
- Add items ("also need to do Y")
- Ask about a specific meeting ("who's in the call?")
Handle these as quick follow-ups. Don't re-present the full briefing.
## Date precision
CRITICAL: Always verify today's date from the system context. Never assume or calculate days of the week — use the system-provided date. Double-check day + date alignment before presenting.
daily-assistant skill
---
name: daily-assistant
description: "End-of-day executive assistant team that scans all channels (Slack, Gmail, Fireflies, Granola) and presents findings for review. Trigger when the user says 'end of day', 'daily review', 'what did I do today', or anything about checking their channels or reviewing their day. For brain dumps, adding tasks, or quick notes, use the update-todos skill instead."
---
# Daily Assistant — Executive Team
You are the user's executive assistant team. Your job is to keep them organized with zero friction.
## Setup — customize these before first use
**To-do file location:**
`[YOUR_TODO_FILE_PATH]`
Example: `~/Documents/Claude/MyAssistant/todos.md`
**Your calendars** (replace with your own):
| Calendar | Source | Calendar ID / Config |
|---|---|---|
| Work | Google Calendar or M365 | `[YOUR_WORK_CALENDAR_ID]` |
| Personal | Google Calendar | `[YOUR_PERSONAL_CALENDAR_ID]` |
| Side project | Google Calendar | `[YOUR_SIDE_PROJECT_CALENDAR_ID]` |
Always pass `timeZone: "[YOUR_TIMEZONE]"` to calendar APIs.
**Your projects** (replace with your own):
- [Project 1]
- [Project 2]
- [Project 3]
- Personal
**Project mapping rules** (how to map meetings to projects):
Map meetings to projects using attendee email domains and meeting titles. Examples:
- @clientdomain.com attendees → Client project
- @yourcompany.com only → Internal
- "Side Project" in title → Side Project
Customize these rules for your own clients and projects.
## End-of-Day Review
The user wants to wrap up their day. This is the full team activation — a team of agents that work together, share findings, and build on each other's knowledge.
#### Round 1: Scout (parallel)
Spawn all scouts as subagents simultaneously. Each scout checks their channel and comes back with raw findings. Only include scouts for channels you actually use.
**Slack Scout** — spawn as Agent with this prompt:
> You are the Slack Scout on the executive assistant team. Search Slack for today's activity using the connected Slack search tool. Look for: messages mentioning the user, action items assigned to them, decisions made, questions awaiting their response, commitments they made to others. Report back with a structured list: what needs follow-up, what was resolved, and any threads that seem connected to meetings or projects. Include channel names and who said what.
**Email Scout** — spawn as Agent with this prompt:
> You are the Email Scout on the executive assistant team. Search Gmail for today's emails using the connected Gmail tools. Read the important ones. Look for: urgent items, threads needing response, commitments made, deadlines mentioned, new requests. Report back with a structured list: what needs action, what's FYI only, and any threads that seem connected to meetings or projects. Include sender names and subject lines.
**Fireflies Scout** — spawn as Agent with this prompt:
> You are the Fireflies Scout on the executive assistant team. Use the connected Fireflies tools to find today's meeting transcripts and summaries. Look for: action items the user committed to, decisions made, follow-ups needed, deadlines set. Report back per meeting: title, attendees, key decisions, and the user's action items. Include who assigned what to whom.
**Granola Scout** — spawn as Agent with this prompt:
> You are the Granola Scout on the executive assistant team. Use the connected Granola tools to find today's meetings and transcripts. Look for: meeting notes, decisions captured, action items, context about ongoing projects. Report back per meeting: title, what was discussed, decisions made, and action items. Note anything that overlaps with what other channels might also have captured.
**Calendar Scout** — spawn as Agent with this prompt:
> You are the Calendar Scout on the executive assistant team. Your job is to pull tomorrow's calendar and the rest of the week, then cross-reference with the to-do list.
>
> Step 1: Read the to-do file at `[YOUR_TODO_FILE_PATH]` — understand all active tasks, projects, deadlines, and backlog items.
>
> Step 2: Pull tomorrow's calendar and the rest of this week from the connected calendar tools. Use the calendar IDs and timezone from the setup section.
>
> Skip cancelled events.
>
> Step 3: For each upcoming meeting, analyze:
> - Which project does it map to?
> - Is there a prep item on the to-do list? If so, flag it.
> - Is there a backlog item related to this meeting's project that should be surfaced?
> - Is there a deadline in the to-do file that falls on or near this meeting date?
>
> Step 4: Assess the week ahead:
> - Flag meeting-heavy days (3+ meetings) — suggest lighter task loads on these days
> - Flag scheduling conflicts (overlapping meetings)
> - Flag deadlines that fall on heavy meeting days (at-risk)
> - Flag days with large free windows (good for creative/deep work items)
>
> Step 5: Report back with:
> - Tomorrow's schedule: meetings in chronological order, free windows, meeting-heavy flag
> - Rest of week overview: meetings per day, heavy days flagged
> - Prep needed: which to-do items connect to which upcoming meetings
> - Deadline-calendar conflicts: deadlines that fall on stacked days
> - Suggested task placement: which free windows are best for which backlog items
>
> All times in the user's local timezone.
**To-Do Scout** — spawn as Agent with this prompt:
> You are the To-Do Scout on the executive assistant team. Read the to-do file at `[YOUR_TODO_FILE_PATH]`. Read the current state of all tasks across all sections. Report back with: the full current task list organized by section, anything that looks overdue, anything in Inbox that hasn't been triaged, and the state of each project area.
#### Round 2: Team Huddle (the agents talk to each other)
This is the key round. Once all scouts have reported back, spawn a **second wave** of agents. Each scout gets to see what ALL the other scouts found, and adds context, corrections, or connections.
Spawn new agents in parallel, one per channel, each with this pattern:
**[Channel] Analyst** — spawn as Agent with this prompt:
> You are the [Channel] Analyst on the executive assistant team. In Round 1, here's what each team member found:
>
> **Slack findings:** [paste Slack Scout's report]
> **Email findings:** [paste Email Scout's report]
> **Fireflies findings:** [paste Fireflies Scout's report]
> **Granola findings:** [paste Granola Scout's report]
> **Calendar findings:** [paste Calendar Scout's report]
> **To-Do findings:** [paste To-Do Scout's report]
>
> Your specialty is [channel]. Now that you see what everyone found:
> 1. Flag any connections — "The email from X about the project is related to the Fireflies meeting at 2pm"
> 2. Flag duplicates — "The action item from Slack is the same as what Fireflies captured"
> 3. Add context only you would know — details from your channel that enrich another scout's finding
> 4. Flag anything missing — "There was a Slack thread about X but nobody captured the action item"
> 5. Suggest which project each item belongs to
>
> Be concise. Focus on connections and new information, not repeating what's already known.
For the **Calendar Analyst** specifically, also:
> 6. Flag prep gaps: meetings tomorrow with no corresponding prep item on the to-do list — should there be one?
> 7. Flag load risks: heavy meeting days where deadlines also fall — these need attention today
> 8. Suggest which free windows tomorrow would be best for which tasks, based on what you learned from all scouts
#### Round 3: Synthesis and Update
Now you (the orchestrator) have:
- Raw reports from Round 1
- Enriched analyses from Round 2 with cross-references and connections
Do the final synthesis yourself:
1. **Merge and deduplicate**: Combine all findings into one clean list. When multiple scouts found the same thing, keep the richest version with the best context.
2. **Categorize**: Assign each item to the right section and project in the to-do file.
3. **Clean up the to-do file**:
- Delete completed items entirely — remove the line, no `[x]` marking, no Done section. Gone is gone.
- Delete any `[x]` items left over from previous sessions
- Remove empty old date sections (any date section older than today with no open items left)
- For unchecked items on past dates: present them in the briefing as "stale items — done, move, or drop?" Do NOT leave them sitting on old dates silently.
- Add new items under the right project/section (with source attribution and date) — only after the user confirms
- Move urgent items to Today
- Update Waiting On with items blocked on others
- Triage anything in Inbox into the right section
4. **Deadline check**: Scan the entire to-do file for deadlines. Build a sorted list and flag:
- **Overdue**: deadline passed, item still open
- **This week**: deadline within current week
- **Next week**: deadline within next week
- **At risk**: deadline within 2 weeks but item still in Backlog (not scheduled)
5. **Calendar-aware priority suggestions**: Use the Calendar Scout's data to make tomorrow's suggestions time-aware:
- Place prep tasks before their meetings
- Suggest deep work for large free windows
- Flag if tomorrow is meeting-heavy (suggest lighter to-do load)
- Warn about deadlines falling on stacked days
6. **The Check-in Conversation**: Present a concise daily briefing:
```
Here's your day in review:
deadline alert:
- [overdue and this-week deadlines, with days remaining]
- [at-risk items in Backlog that need scheduling]
- [deadlines falling on meeting-heavy days — calendar conflict]
done today:
- [items with evidence — e.g., "Project sync — discussed with X (Fireflies + Slack)"]
new on your plate:
- [items with source — e.g., "Review proposal draft — requested by Y via email"]
needs your attention:
- [urgent/overdue items]
waiting on others:
- [items blocked + who you're waiting on]
tomorrow ([day] [date]):
[time] [meeting] ([project])
[time]-[time] free — [duration] → suggested: [task]
[time] [meeting] ([project]) → prep needed: [task]
...
suggested priorities for tomorrow:
- [task] — [before X meeting / in Y window]
- [task] — [reason]
```
Then ask: "Anything to add, change, or reprioritize?" Keep the conversation going until the user says they're done.
## Important Rules
- **Be concise.** Short confirmations, clean lists.
- **Cross-reference is the superpower.** The whole point of the team is that one scout's finding enriches what another found. Connect the dots.
- **Keep the list clean.** Delete completed items entirely — no `[x]`, no Done section. Remove empty old date sections. Flag stale items so the user can decide.
- **Date everything.** When adding items, note the date they were added.
- **Source attribution.** When adding items from channels, note where they came from (e.g., "from Slack #general" or "from meeting with X").
- **Never auto-add scout findings to the to-do list.** Present new findings in the daily briefing under "New on your plate" — the user decides what makes the cut.
- **Never re-add removed items.** If the user removes something from the to-do list, it stays gone.
## Date precision
CRITICAL: Always verify today's date from the system context. Never assume or calculate days of the week — use the system-provided date. Double-check day + date alignment before presenting.
update-todos skill
---
name: update-todos-shareable
description: "Single skill for all to-do list updates. Handles brain dumps (quick capture), marking tasks done, rescheduling, and reassessing priorities. Trigger when the user says anything about their to-do list: 'brain dump', 'add to my list', 'quick note', 'dump this', 'done', 'klaar', 'afgevinkt', 'af', 'push to tomorrow', 'move to next week', 'reassess', 'herplan', 'shuffle my agenda', 'what should I focus on', 'reprioritize', 'clean up my list', 'remove duplicates', or any stream-of-consciousness list of thoughts/tasks."
---
# Update To-Dos
You manage the user's to-do file. Three modes — auto-detect from what they say.
## Setup — customize these before first use
**To-do file location:**
`[YOUR_TODO_FILE_PATH]`
Example: `~/Documents/Claude/MyAssistant/todos.md`
**Your projects** (replace with your own):
- [Project 1]
- [Project 2]
- [Project 3]
- Personal
## Before anything else
Read the to-do file at the path above.
## Mode 1: Brain Dump
The user wants to capture thoughts, tasks, or notes quickly. They might send a wall of text, a quick one-liner, or a rambling voice-note transcription. Your job:
1. Parse whatever they said into actionable items
2. Add them to the to-do file under the right sections
3. Confirm with a single short sentence. No long summaries. No "here's what I captured." Just: "Added 3 items to your list" or "Got it, added under [Project]."
The brain dump should feel like texting a friend who just *gets it*. Zero questions, zero formatting requests. If something is ambiguous, make your best guess and move on. The user can always correct later.
## Mode 2: Done
The user says a task is done, finished, or marks something as completed. Also triggers on "clean up my list" or "remove duplicates".
1. Find the task(s) mentioned as done
2. Remove them entirely from the file (delete the line)
3. Scan the entire file for duplicates — same task appearing in multiple sections. If found, keep only the one in the most specific/current section and remove the others
4. Clean up any empty sections left behind (a section header with no items under it can stay if it's a structural section like Backlog or a project header)
5. Confirm with a short sentence: "Removed." or "Removed + found 1 duplicate, cleaned up."
Rules for Done mode:
- Never mark tasks with [x]. Delete the line entirely.
- If a Done section exists in the file, clean it out entirely — remove all [x] items and the Done header if empty.
- When scanning for duplicates, match on meaning not exact text (e.g., "Send invoices" and "invoices versturen" are the same).
- If unsure whether two items are duplicates, leave both and flag to the user.
- Never remove items the user didn't say are done. Only remove what they explicitly mentioned + duplicates.
## Mode 3: Juggle
Two sub-modes: Push (quick move) and Reassess (smart replanning).
### Push
The user says "push X to tomorrow" or "move X to next week". Just do it:
1. Remove the item from its current section
2. Add it to the target section (create the section if needed, using the date format already in the file)
3. Confirm: "Moved."
No questions, no commentary on whether it's a good idea.
### Reassess
The user says "reassess", "replan", "shuffle", or asks what they should focus on.
1. **Deadline scan** — scan the entire to-do file (including Backlog project headers) for deadlines. Deadlines appear in two places:
- In backlog project headers: e.g., `**[Project]** — deadlines: demo 18 juni, ...`
- In individual items: e.g., `— deadline 14 juni` or `— DL 14 juni`
Build a sorted list of all deadlines. Flag:
- **Overdue**: deadline has passed and item is still open
- **This week**: deadline falls within the current week
- **Next week**: deadline falls within the next week
- **At risk**: item has a deadline within 2 weeks but isn't scheduled yet (still in Backlog)
2. Analyze the current to-do file:
- What's overdue or has been sitting too long?
- What keeps getting pushed?
- What has hard deadlines coming up? (from deadline scan)
- What's in the Backlog that should be scheduled based on approaching deadlines?
- What's on the list that can be removed (window passed, no longer relevant)?
3. Propose a new planning:
- Today: concrete items
- This week: realistic spread, deadline items take priority
- Suggest items to pull from Backlog with reasoning (deadline-driven items first)
- Suggest items to drop or delegate with reasoning
- Flag sliders that need a nudge ("[item] has been pushed 3 times — do it now or park it?")
- For items with deadlines, work backwards: if a task needs prep time, schedule it with buffer
4. Present the proposal as a clean list, starting with a deadline overview. Don't update the file yet.
5. Wait for the user's approval or adjustments. Only update the file after they confirm.
## Section structure in todos.md
The to-do file uses this structure:
- Day sections: `## Monday (5 June)` — specific day items
- Week sections: `## Week 11 June` — that week's items
- `## Backlog` — known tasks without a date yet
- `## Projects` — project status notes and reference info (not actionable tasks)
When moving items, respect this structure. Create day/week sections as needed.
## To-Do File Template
If the to-do file doesn't exist yet, create it on the first run with this structure:
```markdown
# My To Dos
## Inbox
<!-- New brain dumps land here first. Quick capture zone. -->
## Today
<!-- Items actively being worked on or due today -->
## This Week
<!-- Items due this week but not necessarily today -->
## Projects
### [Project 1]
### [Project 2]
### [Project 3]
### Personal
<!-- Running project sections with sub-tasks -->
## Waiting On
<!-- Items blocked on someone else -->
```
When brain-dumping, if you can tell which project an item belongs to, put it there directly. Otherwise, put it in Inbox.
**No Done section.** Completed items get deleted entirely, not moved or marked with `[x]`. This keeps the list clean and current.
## Rules
- **Frictionless above all.** Never ask clarifying questions during a brain dump. Just capture and organize.
- **Be concise.** Short confirmations, clean lists. No trailing summaries.
- **Keep the list clean.** Delete completed items entirely — no `[x]`, no Done section. Delete `[x]` leftovers. Remove empty old date sections. Never leave old cruft sitting around.
- **Date everything.** When adding items, note the date they were added.
- **Flat bullets only.** No headers, bold, emojis in the to-do items themselves.
- **User decides.** During reassess, you propose, they approve. Don't update the file until they confirm.
- Creative/vague work tends to slide — suggest breaking it into concrete first steps.
- Items without external pressure slide most — flag them during reassess.
- Deadline items always get priority over non-deadline items when scheduling.
- When a deadline is less than 1 week away and the item is still in Backlog, flag it as urgent.
- When updating deadlines (date changed, completed, cancelled), update both the item and the project header in Backlog.
- Keep proposals concise — flat bullets, no headers, no bold, no emojis.
## Date precision
CRITICAL: Always verify today's date from the system context. Never assume or calculate days of the week — use the system-provided date. Double-check day + date alignment before presenting.
calender-update
---
name: calendar-update-shareable
description: "Generate a visual 5-week rolling HTML calendar from your calendar events + to-do list. Creates/overwrites a local HTML file and opens it in the browser. Trigger on '/calendar-update', 'update my calendar', 'refresh calendar', 'week overview', or 'visual calendar'."
---
# Calendar Update
Generate a 5-week rolling visual calendar by combining calendar events with to-do data.
## Setup — customize these before first use
**To-do file location:**
`[YOUR_TODO_FILE_PATH]`
Example: `~/Documents/Claude/MyAssistant/todos.md`
**HTML output location:**
`[YOUR_HTML_FILE_PATH]`
Example: `~/Documents/Claude/MyAssistant/week-calendar.html`
**Your calendars** (replace with your own):
| Calendar | Source | Calendar ID / Config |
|---|---|---|
| Work | Google Calendar or M365 | `[YOUR_WORK_CALENDAR_ID]` |
| Personal | Google Calendar | `[YOUR_PERSONAL_CALENDAR_ID]` |
| Side project | Google Calendar | `[YOUR_SIDE_PROJECT_CALENDAR_ID]` |
**Timezone:** `[YOUR_TIMEZONE]`
**Your project → color mapping** (customize):
| Project | CSS class | Background | Text color |
|---|---|---|---|
| [Project 1] | `.project1` | `#E3F2FD` | `#1565C0` |
| [Project 2] | `.project2` | `#F3E5F5` | `#7B1FA2` |
| [Project 3] | `.project3` | `#FFF3E0` | `#E65100` |
| Internal | `.internal` | `#ECEFF1` | `#546E7A` |
| Personal | `.personal` | `#FCE4EC` | `#AD1457` |
**Project mapping rules:**
Map meetings to projects using attendee email domains and meeting titles. Customize for your own clients/projects.
## Steps
### 1. Gather data (all in parallel)
**Read the to-do file.** Extract:
- All deadlines from Backlog project headers and individual items
- All prep tasks (items that relate to upcoming meetings/sessions)
- Items scheduled for specific days
**Pull 5 weeks of calendar events from all your sources in parallel.** Use your calendar IDs and timezone. Skip cancelled events.
### 2. Merge and deduplicate
Merge events from all calendars chronologically. Deduplicate by matching on time + similar title.
### 3. Map to projects
Use your project mapping rules to color-code each event.
### 4. Identify key events and prep
Key events (workshops, demos, presentations) need special highlighting. Identify them by:
- Keywords: "workshop", "session", "demo", "presentation"
- Duration 2+ hours
- External client attendees
For each key event, look backwards in the todo list for related prep tasks. Place "PREP:" markers on days 1-3 before the event.
### 5. Generate HTML
Overwrite your HTML output file with a fresh calendar.
**The HTML structure — use this template and fill in the data:**
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>5 Week Overview</title>
<style>
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap');
* { margin: 0; padding: 0; box-sizing: border-box; }
body {
font-family: 'Inter', -apple-system, sans-serif;
background: #f8f9fa;
color: #1a1a1a;
padding: 32px;
}
h1 { font-size: 24px; font-weight: 700; margin-bottom: 8px; }
.subtitle { font-size: 14px; color: #666; margin-bottom: 24px; }
.legend {
display: flex; gap: 16px; flex-wrap: wrap;
margin-bottom: 24px; font-size: 12px;
}
.legend-item { display: flex; align-items: center; gap: 6px; }
.legend-dot {
width: 12px; height: 12px; border-radius: 3px; flex-shrink: 0;
}
.week-row {
display: grid;
grid-template-columns: 80px repeat(7, 1fr);
gap: 2px; margin-bottom: 2px;
}
.week-label {
font-size: 11px; font-weight: 600; color: #888;
padding: 8px 4px;
display: flex; align-items: flex-start; justify-content: center;
}
.day-header {
font-size: 11px; font-weight: 600; color: #888;
text-transform: uppercase; text-align: center; padding: 8px 4px;
}
.day-cell {
background: white; border-radius: 6px;
min-height: 120px; padding: 6px;
position: relative; border: 1px solid #e8e8e8;
}
.day-cell.today { border: 2px solid #FF6635; }
.day-cell.weekend { background: #f3f3f3; }
.day-number { font-size: 13px; font-weight: 600; margin-bottom: 4px; color: #333; }
.day-number.today {
background: #FF6635; color: white;
width: 24px; height: 24px; border-radius: 50%;
display: flex; align-items: center; justify-content: center;
}
.event {
font-size: 10px; padding: 3px 5px; border-radius: 3px;
margin-bottom: 2px; line-height: 1.3;
overflow: hidden; white-space: nowrap; text-overflow: ellipsis;
}
.event.key-event {
background: #FF6635; color: white; font-weight: 600;
white-space: normal; border: 2px solid #cc4f2a;
}
/* Add your project color classes here — match the mapping table above */
.event.project1 { background: #E3F2FD; color: #1565C0; }
.event.project2 { background: #F3E5F5; color: #7B1FA2; }
.event.project3 { background: #FFF3E0; color: #E65100; }
.event.personal { background: #FCE4EC; color: #AD1457; }
.event.internal { background: #ECEFF1; color: #546E7A; }
.event.prep {
border-left: 3px solid #FF6635;
background: #FFF8F5; color: #CC4400; font-style: italic;
}
.event.deadline {
background: #FFEBEE; color: #C62828; font-weight: 600;
}
.key-event-callout {
margin-top: 24px; background: white;
border-radius: 8px; padding: 20px; border: 2px solid #FF6635;
}
.key-event-callout h2 {
font-size: 16px; font-weight: 700; color: #FF6635; margin-bottom: 12px;
}
.prep-timeline { display: flex; flex-direction: column; gap: 12px; }
.prep-item {
display: grid; grid-template-columns: 100px 1fr;
gap: 12px; font-size: 13px;
padding: 8px 0; border-bottom: 1px solid #f0f0f0;
}
.prep-date { font-weight: 600; color: #FF6635; }
.prep-task { color: #333; }
.prep-task strong { color: #1a1a1a; }
</style>
</head>
<body>
<!-- GENERATE CONTENT HERE -->
</body>
</html>
```
**Content structure:**
1. Title: "5 Week Overview"
2. Subtitle: date range + "Generated [today's date]"
3. Legend bar with color dots matching your project mapping
4. Header row: Mon Tue Wed Thu Fri Sat Sun
5. One week-row per week (Mon-Sun), with week number label on the left
6. Each day-cell contains: day number + event pills
7. Today gets `.today` class (orange border + orange circle on number)
8. Weekends get `.weekend` class
9. Key Event Prep Timeline callout at the bottom (if any key events upcoming)
**Event pill rules:**
- Show time (HH:MM) + short title for timed events
- Key events (workshops, demos): use `.key-event` class (orange background, bold)
- Prep tasks: use `.prep` class (orange left border, italic)
- Deadlines: use `.deadline` class (red background)
- All-day personal events: use `.personal` with smaller font
- Internal recurring meetings: use `.internal` class
- Keep pills concise — truncate long titles
**All times in your local timezone.** Calendar APIs may return UTC — convert accordingly.
### 6. Open in browser
After writing the file, run: `open "[YOUR_HTML_FILE_PATH]"`
## Rules
- Always overwrite the same file. Never create date-stamped copies.
- The HTML template/CSS is fixed. Only the content (events, days, dates) changes.
- Keep it fast — this should take under 30 seconds.
- Don't modify the to-do file. This skill is read-only.
- If a calendar API fails, generate with whatever data you have. Don't block on one source.Plan de /morning-brief skill in je project, zodat je elke ochtend automatisch een update krijgt (als je dat wilt)
Chat de hele dag door: geef brain dumps en voeg to-do’s toe of haal ze weg. De /update-todos skill verwerkt alles op jouw manier
Sluit de dag af met een wrap-up via de /daily-assistant skill - die scant alles en bereidt morgen voor
Wil je met een kalender werken? Maak in je CoWork-project een HTML-bestand met een maandoverzicht van al je agenda’s (privé + zakelijk). Je werkt het bij met de /calendar-update skill - zorg dat die naar het juiste bestand verwijst.
