بنقرة واحدة
calendar-prep
Prepare for upcoming calendar events - identify prep needs, research attendees, create briefings
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Prepare for upcoming calendar events - identify prep needs, research attendees, create briefings
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Daily review workflow - process completed work, roll over unfinished items, prepare for tomorrow
Prune and consolidate state files, surface important items from journal to core state
Weekly review for pattern recognition, commitment hygiene, and identity refinement
Guide for setting up Innie from scratch - global config, memory repo, MCP servers, and scheduler
How Matt creates pull requests - branch naming, commit style, PR workflow
Send alerts and notifications using AppleScript - banners, modals, and text-to-speech
| name | calendar-prep |
| description | Prepare for upcoming calendar events - identify prep needs, research attendees, create briefings |
Run this daily (morning) or when asked to prepare for upcoming meetings. Ensures you're never caught off-guard in meetings.
This skill requires calendar access. If not available yet, note the limitation and skip calendar-dependent steps.
Get calendar events for the next 24-48 hours. Focus on:
Skip:
For each relevant event, determine:
| Category | Prep needed |
|---|---|
| 1:1 internal | Check for context in people file, recent interactions |
| 1:1 external | Research attendee, create/update people file, prepare briefing |
| Team meeting | Review agenda if available, check for action items from last time |
| External meeting | Research company/attendees, prepare briefing, check for shared context |
| Interview | Research candidate thoroughly, prepare questions |
| Presentation | Ensure materials ready, rehearsal notes |
For any external person not already in state/people/:
state/people/[name-slug].mdFor each event, ask:
Add any prep tasks to state/today.md with the meeting time as deadline.
Only create a meeting folder when the meeting needs artifacts (briefings, prep docs, notes). Don't create folders for routine meetings.
Structure: state/meetings/[date]-[meeting-slug]/
Create a folder when:
Don't create a folder for:
Folder contents (as needed):
state/meetings/2026-01-07-acme-intro/
├── briefing.md # Pre-meeting research and talking points
├── prep.md # Specific preparation tasks or documents
└── notes.md # Meeting notes (created during/after)
Briefing template (briefing.md):
---
date: 2026-01-07T14:00:00
attendees:
- alice@example.com
- bob@example.com
type: external
status: upcoming
---
# [Meeting name]
## Context
[Why this meeting is happening, what we hope to achieve]
## About [External person/company]
[Key facts from research]
## Email & Chat Context
[Recent email threads, DMs, decisions, or action items related to this meeting]
## Talking points
- [Point 1]
- [Point 2]
## Questions to ask
- [Question 1]
- [Question 2]
The frontmatter enables queries like "find all upcoming external meetings" or "meetings with Alice in the last month".
For each meeting, search Gmail and Google Chat for relevant context:
Search for email threads related to the meeting:
Search for recent DMs with meeting attendees:
google-workspace_chat_search_messages to find recent direct messages from each attendeeSurface insights in the prep doc/briefing:
Add context to the briefing under "Email & Chat Context" section:
## Email & Chat Context
- [Date] (email): [Brief summary of relevant email thread or decision]
- [Date] (chat): [Recent DM context - why meeting scheduled, topics to cover]
- [Date]: [Action items or commitments]
Focus on communications that provide context the meeting organizer or attendees might reference.
Add calendar-related items to today's priorities:
When creating a new person file at state/people/[name].md:
---
email: alice@example.com
company: Acme Corp
role: Product Manager
relationship: external
last_contact: 2026-01-07
---
# Alice Smith
## Context
[How we know them, relationship context]
## Notes
[Key things to remember - communication style, interests, previous discussions]
## Interactions
- 2026-01-07: [Brief note on interaction]
The frontmatter makes the file queryable (find external contacts, people not contacted recently), while the body stays human-readable.
After completing the workflow, summarize: