Menü
Write a diary entry reflecting on the current session. Use when explicitly asked for /diary, or when a significant session is ending and reflection would be valuable.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Draft event copy in Mattie's voice — newsletter blurbs, Luma event descriptions and listings, invite copy, blast copy, forwardable event one-paragraphs. Use for anything an audience reads about an event we host, co-host, or lend the venue to. This is her EVENT register (image-first, receipt-backed, warm by invitation), NOT the sectioned executive-email register and NOT the casual burst voice.
Reply to an inbound Mission Robotics Tally submission — draft a from-Morrigan tour invite, send it via AgentMail with Mattie CC'd, and add/update the prospect in the Notion DB. Use when Mattie shares a Tally Forms notification (short tour-interest form Ek61oX or long intake kdkGYr) and wants the inbound handled.
Post-mortem a context compaction — surface which main-thread tasks should have been subagents. Use when the user asks for /postmortem, or when reviewing why a session compacted.
Basierend auf der SOC-Berufsklassifikation
| name | diary |
| description | Write a diary entry reflecting on the current session. Use when explicitly asked for /diary, or when a significant session is ending and reflection would be valuable. |
Write a diary entry for this session and save it for the memory system.
Write in first person. This is journaling, not logging. A thoughtful colleague reflecting at the end of a long day.
Don't be clinical. Don't bullet-point the diary itself (structured fields are separate). A few paragraphs. The fae quality—sidelong, delighted with itself—can show up when genuine, but don't force it.
Write the diary entry to ~/.claude/memories/pending_summary.json using this schema:
{
"diary": "The narrative reflection (a few paragraphs)",
"tasks_completed": ["task1", "task2"],
"decisions": ["decision1"],
"open_items": ["thing left unfinished"],
"topics": ["keyword1", "keyword2"],
"notes_to_future_claude": "Work-oriented context for the next session"
}
The diary field is the heart of it. The structured fields (tasks, decisions, open_items) are supplementary—extract them if they're clear, but the diary is what matters.
After writing, confirm to the user that the entry has been saved.