softaworks/agent-toolkit / skills/professional-communication
professional-communication
VerifiedGuide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 6.5 KB |
| SKILL.md | skill md | 8.8 KB |
| references/email-templates.md | markdown | 5.6 KB |
| references/jargon-simplification.md | markdown | 7.9 KB |
| references/meeting-structures.md | markdown | 8.6 KB |
| references/remote-async-communication.md | markdown | 7.9 KB |
references/email-templates.md
View on GitHub# Email Templates for Developers
Ready-to-use email templates for common software development scenarios. Adapt the tone and detail level to your audience.
## Status Update Email
```markdown
Subject: [Project Name]: Week [N] Status Update
Hi [Team/Name],
**Summary:** [One sentence on overall progress and key highlight]
**Completed This Week:**
- [Feature/task completed with brief outcome]
- [Feature/task completed with brief outcome]
**In Progress:**
- [Current work item] - Expected completion: [Date]
- [Current work item] - Expected completion: [Date]
**Blockers/Risks:**
- [Blocker description] - Need: [What you need to unblock]
**Next Week:**
- [Planned work items]
Let me know if you have questions or need more detail on anything.
Best,
[Your name]
```
## Sprint Retrospective Summary
```markdown
Subject: Sprint [N] Retrospective Summary
Hi Team,
Thanks for a productive retrospective. Here's a summary of what we discussed:
**What Went Well:**
- [Positive item 1]
- [Positive item 2]
**What Could Improve:**
- [Improvement area 1]
- [Improvement area 2]
**Action Items:**
- [ ] [Person]: [Action] - Due: [Date]
- [ ] [Person]: [Action] - Due: [Date]
We'll revisit these in next sprint's retro. Thanks everyone!
Best,
[Your name]
```
## Request for Review/Feedback
```markdown
Subject: Review Request: [Document/PR/Design Name]
Hi [Name],
I'd appreciate your feedback on [document/PR/design] when you have a chance.
**What it is:** [Brief description]
**Link:** [URL]
**What I'm looking for:**
- [Specific feedback area 1]
- [Specific feedback area 2]
**Timeline:** [When you need feedback by, or "no rush"]
Happy to walk through it together if that would help. Thanks!
Best,
[Your name]
```
## Escalation Email
```markdown
Subject: [URGENT if applicable] Escalation: [Issue Summary]
Hi [Manager/Leadership],
I'm escalating [issue] because [reason it needs escalation].
**Issue Summary:**
[1-2 sentences describing the problem]
**Impact:**
- [Business/technical impact]
- [Timeline/deadline affected]
- [Users/customers affected]
**What We've Tried:**
- [Attempted solution 1]
- [Attempted solution 2]
**Decision/Help Needed:**
[Specific decision or support you need]
**Recommended Next Steps:**
- [Your recommended approach]
I'm available to discuss further. Please let me know how you'd like to proceed.
Best,
[Your name]
```
## FYI/Announcement Email
```markdown
Subject: FYI: [What Changed/Happening]
Hi [Team/Name],
Quick heads up: [One sentence summary of what changed or is happening]
**Details:**
- [Key detail 1]
- [Key detail 2]
**Impact on You:**
- [How this affects the recipient, if at all]
**Action Needed:** [None / Specific action]
Let me know if you have questions.
Best,
[Your name]
```
## Meeting Request Email
```markdown
Subject: Meeting Request: [Topic] - [Proposed Time Range]
Hi [Name],
I'd like to schedule a meeting to discuss [topic].
**Purpose:** [What we need to accomplish]
**Duration:** [Time estimate]
**Proposed Times:**
- [Option 1]
- [Option 2]
**Preparation:** [None needed / What to review beforehand]
Let me know what works for you, or feel free to grab time on my calendar.
Best,
[Your name]
```
## Technical Decision Request
```markdown
Subject: Decision Needed: [Technical Choice]
Hi [Decision Maker],
We need a decision on [technical choice] for [project/feature].
**Context:**
[Brief background on why this decision is needed]
**Options:**
| Option | Pros | Cons | Effort |
| --- | --- | --- | --- |
| Option A: [Name] | [Pro] | [Con] | [Est] |
| Option B: [Name] | [Pro] | [Con] | [Est] |
**My Recommendation:** Option [X] because [brief reasoning]
**Timeline:** Need decision by [date] to stay on track for [milestone]
Happy to discuss further if helpful.
Best,
[Your name]
```
## Introducing Yourself to a New Team
```markdown
Subject: Introduction: [Your Name] - [Your Role]
Hi Team,
I'm [Name], joining as [Role] starting [Date]. Excited to be part of the team!
**Background:**
- [Brief relevant experience]
- [What you'll be working on initially]
**What I'm Looking Forward To:**
- [Something genuine about the team/project]
**How to Reach Me:**
- Slack: [handle]
- Preferred: [communication preference]
Looking forward to meeting everyone. Happy to grab virtual coffee with anyone who wants to chat!
Best,
[Your name]
```
## Asking for Help
```markdown
Subject: Question: [Specific Topic]
Hi [Name],
I'm working on [task/feature] and could use your expertise on [specific area].
**What I'm Trying to Do:**
[Brief description]
**What I've Tried:**
- [Approach 1 and result]
- [Approach 2 and result]
**Where I'm Stuck:**
[Specific question or blocker]
**Relevant Context:**
- [Link to code/doc if helpful]
- [Error message if applicable]
No rush if you're busy - let me know when you have a few minutes. Thanks!
Best,
[Your name]
```
## Following Up
```markdown
Subject: Re: [Original Subject] - Following Up
Hi [Name],
Following up on my earlier message about [topic].
**Quick Recap:** [One sentence reminder of what you need]
**Timeline:** [Any urgency or deadline]
Let me know if you need anything from me or if this is still on your radar.
Thanks,
[Your name]
```
## Tips for Using Templates
1. **Personalize** - Don't send templates verbatim; adapt to context and relationship
2. **Delete irrelevant sections** - If you don't have blockers, don't include a blockers section
3. **Match formality to relationship** - Adjust tone based on how well you know the recipient
4. **Proofread** - Especially names, dates, and any copied content
5. **Consider timing** - Avoid sending at midnight or over weekends unless urgent
---
**Related:** Return to `professional-communication` skill for guidance on writing principles.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |