Professional Communication
Draft clearer emails, chat updates, and meeting notes for teammates and stakeholders without drowning them in jargon.
Overview
Professional Communication is a journey-wide agent skill that structures emails, chats, and meeting comms with What–Why–How—usable whenever a solo builder needs to be understood before committing to more work or scope.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill professional-communicationWhat is this skill?
- What–Why–How structure for any professional message
- Guidance for email, team chat, and meeting agendas or summaries
- Adapting technical detail for non-technical vs engineering audiences
- Status updates and reports with clarity-first framing
- Read/Glob/Grep-only tooling—no shell or network writes
Adoption & trust: 3.7k installs on skills.sh; 2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know the technical truth but your messages land as noise, ambiguity, or unnecessary jargon for the person who has to decide or unblock you.
Who is it for?
Solo builders who own both implementation and stakeholder updates across Claude Code, Cursor, or similar agents.
Skip if: Teams that already enforce a formal comms template and only need raw code generation with no human-facing prose.
When should I use this skill?
Drafting professional messages, preparing meeting communications, or improving written communication for technical vs non-technical audiences.
What do I get? / Deliverables
You leave with audience-appropriate drafts and outlines (email, chat, agenda, or summary) that state context, rationale, and next steps in one pass.
- Structured email or chat draft (What–Why–How)
- Meeting agenda or summary outline
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Email a concise scope change to a client using What–Why–How before you expand the prototype.
Post a daily async update that separates blockers, decisions needed, and done work.
Draft internal launch comms that explain risk, rollout steps, and rollback owners.
Reply to a confused user with plain-language steps while linking to technical detail for power users.
Summarize an incident timeline for leadership without burying the mitigation in stack traces.
How it compares
Use instead of dumping unstructured agent chat into Slack or email when you need repeatable professional structure.
Common Questions / FAQ
Who is professional-communication for?
Indie and solo developers who write to managers, clients, or teammates and want consistent, credible messages without a communications coach.
When should I use professional-communication?
Use it while validating (scope emails to a cofounder), building (async standups), shipping (release notes), launching (partner outreach), growing (support escalations), or operating (incident summaries)—any time written clarity matters.
Is professional-communication safe to install?
Review the Security Audits panel on this Prism page; the skill declares Read, Glob, and Grep only—no scripted installs or network calls in its allowed-tools list.
SKILL.md
READMESKILL.md - Professional Communication
# Professional Communication ## Overview This skill provides frameworks and guidance for effective professional communication in software development contexts. Whether you're writing an email to stakeholders, crafting a team chat message, or preparing meeting agendas, these principles help you communicate clearly and build professional credibility. **Core principle:** Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood. ## When to Use This Skill Use this skill when: - Writing emails to teammates, managers, or stakeholders - Crafting team chat messages or async communications - Preparing meeting agendas or summaries - Translating technical concepts for non-technical audiences - Structuring status updates or reports - Improving clarity of written communication **Keywords**: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report ## Core Frameworks ### The What-Why-How Structure Use this universal framework to organize any professional message: | Component | Purpose | Example | | --- | --- | --- | | **What** | State the topic/request clearly | "We need to delay the release by one week" | | **Why** | Explain the reasoning | "Critical bug found in payment processing" | | **How** | Outline next steps/action items | "QA will retest by Thursday; I'll update stakeholders Friday" | **Apply to**: Emails, status updates, meeting talking points, technical explanations ### Three Golden Rules for Written Communication 1. **Start with a clear subject/purpose** - Recipients should immediately grasp what your message is about 2. **Use bullets, headlines, and scannable formatting** - Nobody wants a wall of text 3. **Key messages first** - Busy people appreciate efficiency; state your main point upfront ### Audience Calibration Before communicating, ask yourself: 1. **Who** are you writing to? (Technical peers, managers, stakeholders, customers) 2. **What level of detail** do they need? (High-level overview vs implementation details) 3. **What's the value** for them? (How does this affect their work/decisions?) ## Email Best Practices ### Subject Line Formula | Instead of | Try | | --- | --- | | "Project updates" | "Project X: Status Update and Next Steps" | | "Question" | "Quick question: API rate limiting approach" | | "FYI" | "FYI: Deployment scheduled for Tuesday 3pm" | ### Email Structure Template ```markdown **Subject:** [Project/Topic]: [Specific Purpose] Hi [Name], [1-2 sentences stating the key point or request upfront] **Context/Background:** - [Bullet point 1] - [Bullet point 2] **What I need from you:** - [Specific action or decision needed] - [Timeline if applicable] [Optional: Brief next steps or follow-up plan] Best, [Your name] ``` ### Common Email Types | Type | Key Elements | | --- | --- | | **Status Update** | Progress summary, blockers, next steps, timeline | | **Request** | Clear ask, context, deadline, why it matters | | **Escalation** | Issue summary, impact, attempted solutions, needed decision | | **FYI/Announcement** | What changed, who's affected, any required action | **For templates**: See `references/email-templates.md` ## Team Messaging Etiquette > **Note:** Examples use Slack terminology, but these principles apply equally to Microsoft Teams, Discord, or any team messaging platform. ### When to Use Chat vs Email | Use Chat | Use Email | | --- | --- | | Quick questions with short answers | Detailed documentation needing records | | Real-time coordination | Formal communications to st