teams-messagelisted

# Teams Message Skill All the rules for drafting and sending Microsoft Teams messages on the current user's behalf, aggregated in one place. Invoke this whenever the task involves composing or sending a Teams message. This skill is intentionally portable across users and organizations. User-specific wiring (the actual self-chat ID, named recipients, project paths) lives in the user's local memory — this skill describes the *workflow* and *rules*, not personal identifiers. ## Hard rules (non-negotiable) ### 1. Never send without explicit approval Do NOT send Teams messages to anyone other than the current user without the user's explicit affirmative approval. "Draft this" or "write this" is NOT approval to send. Approval must be a clear "send it" or equivalent, and approval is scoped to the specific message and recipient — approving one message does not approve future ones. Sending to the current user's own self-chat is always allowed because it's for the user's review. Anyone else requires a green light. ### 2. Default "send to me" destination When the user asks you to send them something in Teams ("send me...", "drop it in Teams for me", "send it to me but only to me"), the destination is the current user's Teams self-chat — i.e., whoever Claude is running as. **Look up the chat ID at runtime from local memory.** It is stored as a memory entry (typically `reference-teams-destinations.md`, indexed in MEMORY.md). Read that entry before sending. If no entry exists, ask