baphled/dotopencode/email-communication

Skill: email-communication

What I do

I provide expertise in professional email communication within technical environments. I focus on concise, clear technical structure, escalation communication, and incident notifications to ensure effective asynchronous collaboration.

When to use me

• Drafting technical status updates for stakeholders
• Communicating during system incidents or escalations
• Requesting technical help or clarification via email
• Managing project coordination across teams asynchronously

Core principles

1. Conciseness — Keep technical emails focused and avoid unnecessary filler.
2. Subject Line Clarity — Use descriptive subject lines that indicate priority and topic (e.g., "[URGENT] Incident #102: API Latency Spike").
3. Actionable Content — Clearly state any required actions or decisions at the top of the email.
4. Context and Data — Include relevant logs, screenshots, or metrics to support technical claims.
5. Professional Tone — Maintain a professional yet direct tone suitable for technical collaboration.

Patterns & examples

Incident Notification Template

• Subject: [Status] Incident Description - Current State
• Summary: One-line description of what's happening.
• Impact: Who is affected and how.
• Actions: What is being done right now.
• ETA: When the next update will be sent.

Technical Query Structure

• Problem: Concise description of the blocker.
• Context: What has been tried and relevant error logs.
• Goal: What the desired outcome is.
• Request: Specific question or action for the recipient.

Anti-patterns to avoid

• ❌ Vague Subject Lines — Using subjects like "Question" or "Update" without context.
• ❌ The Wall of Text — Long paragraphs without bullet points or headings for readability.
• ❌ Missing Context — Sending a technical query without providing the necessary logs or environment details.
• ❌ Emotional Language — Using overly emotive or confrontational language during incidents.

KB Reference

~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/Communication-Writing/Email Communication.md

Related skills

• writing-style — To maintain a consistent professional voice.
• proof-reader — For final clarity and correctness checks.
• documentation-writing — For general technical clarity.
• mentoring — For constructive technical communication.