meeting prep

Use the calendar or the user’s explicit meeting choice to identify the event and start time. A booking email alone is not proof of the next meeting. If neither source is available, ask which meeting. Resolve participants by the exact calendar identity, never a shared first name. Search Screenpipe for the last relevant meeting and unresolved decisions. Separate verified facts, hypotheses, and missing context. Return a short brief: meeting and time, prior commitments, likely purpose, and two useful questions. Link supporting sources. Do not change the calendar or send messages.

<!--kit-footer-->

---

Like this skill? It is part of second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.