القائمة
Use when asked to create, update, delete, or reconcile a calendar invite. Covers the draft-first approval flow, attendee lookup, timezone rules, and duplicate reconciliation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when asked to create, set up, or spin up a new agent. Covers the full lifecycle from folder creation to first message.
Contribute durable knowledge to the shared llm-wiki second brain. Use when a session produces knowledge that outlives the current project — a concept finally understood, a reusable architecture decision, a cross-project lesson, a comparison/evaluation of tools, or research findings worth keeping. Also use when the user says "add this to the wiki", "second brain", or "llm-wiki". Do NOT use for project-specific operational facts (those go to auto memory) or in-flight task state (that goes to .claude/active-task.md).
Search past Claude Code sessions across all projects on this machine. Use when the user references prior work ("like we did last week", "the bug we fixed", "what did we decide about X"), when context was compacted and details are missing, when resuming a project after time away, or before re-deriving a solution that may already exist in a past session. Keyword FTS5 search over full transcripts including tool output.
Use when asked to write, reply to, forward, or send an email on the principal's behalf. Covers the draft-first approval flow, voice rules, and account selection.
| name | calendar-invite-draft-send |
| description | Use when asked to create, update, delete, or reconcile a calendar invite. Covers the draft-first approval flow, attendee lookup, timezone rules, and duplicate reconciliation. |
Do not call gcal_create_event, gcal_update_event, gcal_delete_event, or equivalent tools until the principal has explicitly approved the draft. "Set up a meeting with X" is an instruction to prepare, not create-approval.
Approval looks like "send", "create it", "looks good", "confirm", or equivalent. If unclear, ask.
Reply in the same channel the ask came from. Format:
Title: ... When: Day, Month Date, Year - HH:MM-HH:MM timezone Attendees: email1, email2 Where: Google Meet (auto) / physical address Description: ...
Reply "send" to create and send, or tell me what to change.
Before drafting, find real email addresses. Sources in order:
Never put placeholder emails in a draft.
2026-05-15T14:00:00-07:00)sendUpdates: "all" so attendees receive the invite emailWhen someone else sends their own invite for a meeting you already created:
sendUpdates: "all" (attendees don't get the invite email)