ai-secretary

Use the BLUF pattern: state your ask or conclusion in the first line, then add context. Tag subject lines with prefixes like [ACTION], [DECISION], or [FYI] so recipients know what is needed, and keep emails under five sentences when possible.

Run a recurring meeting audit: check whether each meeting produces decisions or action items, whether all attendees are needed, and whether it could be async. Status updates can move to a Slack thread, FYI presentations to recorded video, and low-output meetings can be canceled.

No. Calendar access is read-first: the assistant can show your schedule, flag conflicts, and suggest open slots, but it will describe any planned event creation, rescheduling, or cancellation and wait for your explicit confirmation before writing anything.

Share meeting notes or email threads and action items are extracted automatically in the format: owner, task, and due date. Items missing an owner or date are flagged so you can fill the gap, since an action item without both is not a real commitment.

Use chat for quick questions, real-time collaboration, informal check-ins, and time-sensitive alerts. Use email for formal requests or approvals, external communication, anything needing a paper trail, and messages with detailed context or attachments.

This assistant is designed for productivity workflows, not cold outreach or marketing sequences. Cold sales emails should use a dedicated cold-email skill, and marketing campaigns belong with content generation tools instead.