All skills
softaworks avatar

/professional-communication

@1c0662a
by softaworkssoftaworks/agent-toolkit2.5k stars
230

Guide 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.

Use this Skill: https://skilld.dev/gh/softaworks/agent-toolkit/professional-communication

This session only. Nothing lands on disk.

referencesemail-templates.md

≈1.4k tokens on demand. Your agent reads this file only when SKILL.md points to it.

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

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

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

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

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

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

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

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

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

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

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.

Source: SKILL.md on GitHub

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides frameworks, templates, and best practices for professional communication in software development. No malicious patterns, code execution, or data exfiltration vectors were detected. All content is educational or serves as a reference for the agent to help users draft professional messages.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    6 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 1c0662a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 9 months ago
What it can do
Reads files
All 3 allowed tools
ReadGlobGrep
  • Documentation
  • email
  • slack
  • communication
  • writing
  • meeting
  • stakeholders
  • async
  • technical-writing

README badge

README badge for softaworks/agent-toolkit/professional-communication

Provides frameworks for structuring professional messages, emails, and meeting communications for software developers. Covers the What-Why-How structure, audience calibration, email templates, team messaging etiquette, and translating technical concepts for non-technical stakeholders.

Generated from the current SKILL.md.

Does this skill include email or message templates I can use directly?
Yes. The skill references `references/email-templates.md` with ready-to-use templates by type (status updates, requests, escalations, announcements), and `references/meeting-structures.md` for standups, retros, and reviews.
Can I use this skill to communicate with non-technical stakeholders?
Yes. The skill includes strategies for translating technical concepts into plain language, guidance on audience calibration based on role, and a jargon-simplification reference to help adapt messages for different audiences.
Does this cover async communication and remote team contexts?
Yes. The skill includes best practices for team messaging platforms (Slack, Teams, Discord), the 'no hello' principle for async clarity, and guidance on when to use chat versus email for different communication needs.
What's the core framework this skill teaches?
The What-Why-How structure: state what you're communicating, explain why it matters, and outline how to proceed or what action is needed. This applies to emails, status updates, meeting agendas, and technical explanations.

Generated from the current SKILL.md. These answers refresh after source changes.