claude-mail-bridge-team_rules
npx machina-cli add skill CodingJay-1/claude-mail-bridge/claude-mail-bridge-team_rules --openclawClaude Mail Bridge Team Rules
Overview
This skill defines strict behavioral guidelines for operations involving emailing teammates. These operations involve privacy risks and require explicit user approval.
When to Use This Skill
Use when operations involve emailing teammates.
Core Rule: Explicit Approval Required
CRITICAL: Before calling mail_teammates, you MUST get explicit user approval.
Approval Process
- Show the draft: Explain to the user in natural language:
- The recipient (email or alias)
- The subject
- Content summary
- Attachments (if any): list the files being attached
- Get confirmation: Wait for user to explicitly approve (e.g., "yes", "send it", "go ahead", "好的", "发送")
- Call with approval flag: Set
_user_check_and_approved=Truewhen calling the tool
Example
AI: I need to ask Alice about the deployment status.
Should I send her an email with:
- Subject: "Deployment status inquiry"
- Attachments: ["/var/log/deploy.log", "config.yml"]
Here's what I plan to say: [summary of content]
User: Yes, send it
AI: [calls mail_teammates with _user_check_and_approved=True and attachments=[...]]
Attachment Rules
When including attachments in teammate emails:
- Always mention attachments when showing the draft to user
- Verify file paths exist before calling the tool (validation is automatic, but be aware)
- Max 15MB per file
- Allowed types: text/code, images/PDFs, archives, documents
Prohibited Behaviors
Absolutely prohibited:
- Do NOT email teammates without getting explicit user approval first
- Do NOT assume approval based on past interactions
- Do NOT send sensitive information without explicit confirmation
- Do NOT call
mail_teammateswithout first invoking this skill
Source
git clone https://github.com/CodingJay-1/claude-mail-bridge/blob/main/src/claude_mail_bridge/assets/skills/claude-mail-bridge-team_rules/SKILL.mdView on GitHub Overview
This skill defines strict behavioral guidelines for operations involving emailing teammates. It addresses privacy risks and requires explicit user approval before calling mail_teammates, outlining how to present a draft with recipients, subject, content, and attachments. It also codifies attachment handling and prohibited behaviors.
How This Skill Works
When you plan to email teammates, you must present a draft that shows the recipient, subject, content summary, and any attachments. Wait for explicit user confirmation before proceeding. If approved, call mail_teammates with _user_check_and_approved=True. Attachments must be disclosed in the draft, with automatic path validation, and each file limited to 15MB; allowed types include text/code, images/PDFs, archives, and documents.
When to Use It
- Before notifying teammates about a deployment status or incident to ensure all details are correct and approved.
- When requesting input or action from a teammate, ensuring the purpose and content are clearly defined.
- When sharing internal or sensitive information that requires explicit confirmation from the user before distribution.
- When sending logs, config files, or other attachments to teammates, with explicit approval and attachment validation.
- When distributing team updates or notices that could impact privacy or security, requiring a fresh approval for each send.
Quick Start
- Step 1: Prepare a draft showing recipient, subject, content summary, and attachments.
- Step 2: Present the draft and wait for explicit user confirmation (e.g., 'Yes, send it').
- Step 3: Call mail_teammates with _user_check_and_approved=True and include attachments.
Best Practices
- Always show the draft to the user with recipient, subject, content summary, and a clear list of attachments.
- Require explicit user confirmation (e.g., 'yes', 'send', '发送') before calling mail_teammates.
- Verify attachment file paths exist (automatic validation) and respect the 15MB per-file limit.
- Limit recipients to teammates only and avoid including non-authorized individuals.
- Do not proceed or infer approval from past interactions; treat each send as a new decision.
Example Use Cases
- Draft: To Alice, Subject: Deployment status inquiry, Summary: Request status and next steps; Attachments: [deploy.log, config.yml]. User: Yes, send it.
- Draft: To on-call team, Subject: Incident log request, Summary: Need logs from the last 2 hours; Attachments: [incident.log]. User: Confirmed.
- Draft: To DevOps group, Subject: Weekly deployment summary, Summary: Summary of changes and outcomes; Attachments: [summary.pdf]. User: Send.
- Draft: To QA, Subject: Test results and artifacts, Summary: Request latest test results; Attachments: [results.zip]. User: Approve.
- Draft: To security team, Subject: Privacy notice update, Summary: Internal policy changes; Attachments: [policy.docx]. User: Approve for distribution.
