{"id":"997f25f0-d617-42c9-a062-aae1e0be1497","shortId":"csNMtk","kind":"skill","title":"professional-communication","tagline":"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 writte","description":"# Professional Communication\n\n## Overview\n\nThis 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.\n\n**Core principle:** Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood.\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Writing emails to teammates, managers, or stakeholders\n- Crafting team chat messages or async communications\n- Preparing meeting agendas or summaries\n- Translating technical concepts for non-technical audiences\n- Structuring status updates or reports\n- Improving clarity of written communication\n\n**Keywords**: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report\n\n## Core Frameworks\n\n### The What-Why-How Structure\n\nUse this universal framework to organize any professional message:\n\n| Component | Purpose | Example |\n| --- | --- | --- |\n| **What** | State the topic/request clearly | \"We need to delay the release by one week\" |\n| **Why** | Explain the reasoning | \"Critical bug found in payment processing\" |\n| **How** | Outline next steps/action items | \"QA will retest by Thursday; I'll update stakeholders Friday\" |\n\n**Apply to**: Emails, status updates, meeting talking points, technical explanations\n\n### Three Golden Rules for Written Communication\n\n1. **Start with a clear subject/purpose** - Recipients should immediately grasp what your message is about\n2. **Use bullets, headlines, and scannable formatting** - Nobody wants a wall of text\n3. **Key messages first** - Busy people appreciate efficiency; state your main point upfront\n\n### Audience Calibration\n\nBefore communicating, ask yourself:\n\n1. **Who** are you writing to? (Technical peers, managers, stakeholders, customers)\n2. **What level of detail** do they need? (High-level overview vs implementation details)\n3. **What's the value** for them? (How does this affect their work/decisions?)\n\n## Email Best Practices\n\n### Subject Line Formula\n\n| Instead of | Try |\n| --- | --- |\n| \"Project updates\" | \"Project X: Status Update and Next Steps\" |\n| \"Question\" | \"Quick question: API rate limiting approach\" |\n| \"FYI\" | \"FYI: Deployment scheduled for Tuesday 3pm\" |\n\n### Email Structure Template\n\n```markdown\n**Subject:** [Project/Topic]: [Specific Purpose]\n\nHi [Name],\n\n[1-2 sentences stating the key point or request upfront]\n\n**Context/Background:**\n- [Bullet point 1]\n- [Bullet point 2]\n\n**What I need from you:**\n- [Specific action or decision needed]\n- [Timeline if applicable]\n\n[Optional: Brief next steps or follow-up plan]\n\nBest,\n[Your name]\n```\n\n### Common Email Types\n\n| Type | Key Elements |\n| --- | --- |\n| **Status Update** | Progress summary, blockers, next steps, timeline |\n| **Request** | Clear ask, context, deadline, why it matters |\n| **Escalation** | Issue summary, impact, attempted solutions, needed decision |\n| **FYI/Announcement** | What changed, who's affected, any required action |\n\n**For templates**: See `references/email-templates.md`\n\n## Team Messaging Etiquette\n\n> **Note:** Examples use Slack terminology, but these principles apply equally to Microsoft Teams, Discord, or any team messaging platform.\n\n### When to Use Chat vs Email\n\n| Use Chat | Use Email |\n| --- | --- |\n| Quick questions with short answers | Detailed documentation needing records |\n| Real-time coordination | Formal communications to stakeholders |\n| Informal team discussions | Messages requiring careful review |\n| Time-sensitive updates | Complex explanations with multiple parts |\n\n### Team Messaging Best Practices\n\n1. **Use threads** - Keep main channels scannable; follow-ups go in threads\n2. **@mention thoughtfully** - Don't notify people unnecessarily\n3. **Channel organization** - Right channel for right topic\n4. **Be direct** - \"Can you review my PR?\" beats \"Hey, are you busy?\"\n5. **Async-friendly** - Write messages that don't require immediate response\n\n### The \"No Hello\" Principle\n\nInstead of:\n\n```text\nYou: Hi\nYou: Are you there?\nYou: Can I ask you something?\n[waiting...]\n```\n\nTry:\n\n```text\nYou: Hi Sarah - quick question about the deployment script.\n     Getting a permission error on line 42. Have you seen this before?\n     Here's the error: [paste error]\n```\n\n## Technical vs Non-Technical Communication\n\n### When to Be Technical vs Accessible\n\n| Audience | Approach |\n| --- | --- |\n| **Engineering peers** | Technical details, code examples, architecture specifics |\n| **Technical managers** | Balance of detail and high-level impact |\n| **Non-technical stakeholders** | Business impact, analogies, outcomes over implementation |\n| **Customers** | Plain language, what it means for them, avoid jargon |\n\n### Three Strategies for Simplification\n\n1. **Start with the big picture before details** - People process \"why\" before \"how\"\n2. **Simplify without losing accuracy** - Use analogies; replace jargon with plain language\n3. **Know when to switch** - Read the room; adjust based on questions and engagement\n\n### Jargon Translation Examples\n\n| Technical | Plain Language |\n| --- | --- |\n| \"Microservices architecture\" | \"Our system is split into smaller, independent pieces that can scale separately\" |\n| \"Asynchronous message processing\" | \"Tasks are queued and processed in the background\" |\n| \"CI/CD pipeline\" | \"Automated process that tests and deploys our code\" |\n| \"Database migration\" | \"Updating how our data is organized and stored\" |\n\n**For more examples**: See `references/jargon-simplification.md`\n\n## Writing Clarity Principles\n\n### Active Voice Over Passive Voice\n\nActive voice is clearer, more direct, and conveys authority:\n\n| Passive (avoid) | Active (prefer) |\n| --- | --- |\n| \"A bug was identified by the team\" | \"The team identified a bug\" |\n| \"The feature will be implemented\" | \"We will implement the feature\" |\n| \"Errors were found during testing\" | \"Testing revealed errors\" |\n\n### Eliminate Filler Words\n\n| Instead of | Use |\n| --- | --- |\n| \"At this point in time\" | \"Now\" |\n| \"In the event that\" | \"If\" |\n| \"Due to the fact that\" | \"Because\" |\n| \"In order to\" | \"To\" |\n| \"I just wanted to check if\" | \"Can you\" |\n\n### The \"So What?\" Test\n\nAfter writing, ask: \"So what? Why does this matter to the reader?\"\n\nIf you can't answer clearly, restructure your message to lead with the value/impact.\n\n## Meeting Communication\n\n### Before: Agenda Best Practices\n\nEvery meeting invite should include:\n\n1. **Clear objective** - What will be accomplished?\n2. **Agenda items** - Topics to cover with time estimates\n3. **Preparation required** - What should attendees bring/review?\n4. **Expected outcome** - Decision needed? Information sharing? Brainstorm?\n\n### During: Facilitation Tips\n\n- **Time-box discussions** - \"Let's spend 5 minutes on this, then move on\"\n- **Capture action items live** - Who does what by when\n- **Parking lot** - Note off-topic items for later\n\n### After: Summary Format\n\n```markdown\n**Meeting: [Topic] - [Date]**\n\n**Attendees:** [Names]\n\n**Key Decisions:**\n- [Decision 1]\n- [Decision 2]\n\n**Action Items:**\n- [ ] [Person]: [Task] - Due [Date]\n- [ ] [Person]: [Task] - Due [Date]\n\n**Next Steps:**\n- [Follow-up meeting if needed]\n- [Documents to share]\n```\n\n**For structures by meeting type**: See `references/meeting-structures.md`\n\n## Quick Reference: Communication Checklist\n\nBefore sending any professional communication:\n\n- [ ] **Clear purpose** - Can the recipient understand intent in 5 seconds?\n- [ ] **Right audience** - Is this the appropriate person/channel?\n- [ ] **Key message first** - Is the main point upfront?\n- [ ] **Scannable** - Are there bullets, headers, short paragraphs?\n- [ ] **Action clear** - Does the recipient know what (if anything) they need to do?\n- [ ] **Jargon check** - Will the audience understand all terminology?\n- [ ] **Tone appropriate** - Is it professional but not cold?\n- [ ] **Proofread** - Any typos or unclear phrasing?\n\n## Additional Tools\n\n- `references/email-templates.md` - Ready-to-use email templates by type\n- `references/meeting-structures.md` - Structures for standups, retros, reviews\n- `references/jargon-simplification.md` - Technical-to-plain-language translations\n\n## Companion Skills\n\n- `feedback-mastery` - For difficult conversations and feedback delivery\n- `/draft-email` - Generate emails using these frameworks\n\n---\n\n**Last Updated:** 2025-12-22\n\n## Version History\n\n- **v1.0.0** (2025-12-26): Initial release\n\n---","tags":["professional","communication","agent","toolkit","softaworks","agent-skills","automation","claude","claude-code","coding-agent","development"],"capabilities":["skill","source-softaworks","skill-professional-communication","topic-agent-skills","topic-automation","topic-claude","topic-claude-code","topic-coding-agent","topic-development"],"categories":["agent-toolkit"],"synonyms":[],"warnings":[],"endpointUrl":"https://skills.sh/softaworks/agent-toolkit/professional-communication","protocol":"skill","transport":"skills-sh","auth":{"type":"none","details":{"cli":"npx skills add softaworks/agent-toolkit","source_repo":"https://github.com/softaworks/agent-toolkit","install_from":"skills.sh"}},"qualityScore":"0.700","qualityRationale":"deterministic score 0.70 from registry signals: · indexed on github topic:agent-skills · 1847 github stars · SKILL.md body (8,623 chars)","verified":false,"liveness":"unknown","lastLivenessCheck":null,"agentReviews":{"count":0,"score_avg":null,"cost_usd_avg":null,"success_rate":null,"latency_p50_ms":null,"narrative_summary":null,"summary_updated_at":null},"enrichmentModel":"deterministic:skill-github:v1","enrichmentVersion":1,"enrichedAt":"2026-05-18T18:52:58.697Z","embedding":null,"createdAt":"2026-04-18T20:27:51.310Z","updatedAt":"2026-05-18T18:52:58.697Z","lastSeenAt":"2026-05-18T18:52:58.697Z","tsv":"'-12':1132,1138 '-2':369 '-22':1133 '-26':1139 '/draft-email':1123 '1':240,287,368,381,522,681,903,981 '2':255,298,384,535,694,910,983 '2025':1131,1137 '3':268,313,543,706,919 '3pm':357 '4':551,926 '42':613 '5':564,944,1029 'access':636 'accomplish':909 'accuraci':698 'action':391,448,952,984,1053 'activ':779,784,795 'adapt':19 'addit':1088 'adjust':714 'affect':323,445 'agenda':17,72,130,161,895,911 'analog':663,700 'answer':489,882 'anyth':1061 'api':347 'appli':224,464 'applic':397 'appreci':274 'approach':350,638 'appropri':1036,1075 'architectur':645,727 'ask':285,426,592,868 'async':126,566 'async-friend':565 'asynchron':740 'attempt':436 'attende':924,976 'audienc':27,140,281,637,1032,1070 'author':792 'autom':753 'avoid':675,794 'background':750 'balanc':649 'base':715 'beat':559 'best':327,407,520,896 'big':685 'blocker':420 'box':939 'brainstorm':933 'brief':399 'bring/review':925 'bug':204,798,808 'build':80 'bullet':257,379,382,1049 'busi':272,563,661 'calibr':282 'captur':951 'care':507 'chang':442 'channel':527,544,547 'chat':67,123,153,478,482 'check':858,1067 'checklist':1015 'ci/cd':751 'clariti':147,777 'clear':78,189,244,425,883,904,1021,1054 'clearer':787 'code':643,760 'cold':1081 'common':410 'communic':3,6,35,40,51,77,86,127,150,159,239,284,499,630,893,1014,1020 'companion':1112 'complex':513 'compon':182 'concept':135 'context':55,427 'context/background':378 'convers':1119 'convey':791 'coordin':497 'core':83,165 'cover':10,915 'craft':64,121 'credibl':82 'critic':203 'custom':297,667 'data':766 'databas':761 'date':975,989,993 'deadlin':428 'decis':393,439,929,979,980,982 'delay':193 'deliveri':1122 'deploy':353,605,758 'detail':302,312,490,642,651,688 'develop':9,54 'difficult':1118 'direct':553,789 'discord':156,469 'discuss':504,940 'document':491,1002 'draft':30 'due':844,988,992 'effect':49,85 'effici':275 'element':415 'elimin':827 'email':11,61,115,152,226,326,358,411,480,484,1095,1125 'engag':719 'engin':639 'ensur':98 'equal':465 'error':610,622,624,819,826 'escal':432 'estim':918 'etiquett':15,455 'event':841 'everi':898 'exampl':184,457,644,722,773 'expect':927 'explain':200 'explan':233,514 'facilit':935 'fact':847 'featur':810,818 'feedback':1115,1121 'feedback-masteri':1114 'filler':828 'first':271,1040 'follow':404,530,997 'follow-up':403,529,996 'formal':498 'format':261,971 'formula':331 'found':205,821 'framework':45,166,176,1128 'friday':223 'friend':567 'fyi':351,352 'fyi/announcement':440 'generat':1124 'get':607 'go':532 'golden':235 'grasp':249 'guid':4 'guidanc':47 'header':1050 'headlin':258 'hello':578 'help':75 'hey':560 'hi':366,584,599 'high':307,654 'high-level':306,653 'histori':1135 'identifi':800,806 'immedi':248,574 'impact':435,656,662 'implement':311,666,813,816 'improv':37,146 'includ':902 'independ':734 'inform':502,931 'initi':1140 'instead':332,580,830 'intent':1027 'invit':900 'isn':87 'issu':433 'item':213,912,953,966,985 'jargon':676,702,720,1066 'keep':525 'key':269,373,414,978,1038 'keyword':151 'know':94,707,1058 'languag':669,705,725,1110 'last':1129 'later':968 'lead':888 'let':941 'level':300,308,655 'limit':349 'line':330,612 'live':954 'll':220 'lose':697 'lot':961 'main':278,526,1043 'manag':118,295,648 'markdown':361,972 'masteri':1116 'matter':431,874 'mean':672 'meet':16,34,71,129,160,229,892,899,973,999,1008 'mention':536 'messag':14,20,32,68,100,124,157,181,252,270,454,473,505,519,569,741,886,1039 'microservic':726 'microsoft':467 'migrat':762 'minut':945 'move':949 'much':92 'multipl':516 'name':367,409,977 'need':191,305,387,394,438,492,930,1001,1063 'next':211,342,400,421,994 'nobodi':262 'non':25,138,628,658 'non-techn':24,137,627,657 'note':456,962 'notifi':540 'object':905 'off-top':963 'one':197 'option':398 'order':851 'organ':178,545,768 'outcom':664,928 'outlin':210 'overview':41,309 'paragraph':1052 'park':960 'part':517 'passiv':782,793 'past':623 'payment':207 'peer':294,640 'peopl':273,541,689 'permiss':609 'person':986,990 'person/channel':1037 'phrase':1087 'pictur':686 'piec':735 'pipelin':752 'plain':668,704,724,1109 'plan':406 'platform':474 'point':231,279,374,380,383,835,1044 'pr':558 'practic':328,521,897 'prefer':796 'prepar':33,70,128,920 'principl':74,84,463,579,778 'process':208,690,742,747,754 'profession':2,31,39,50,81,180,1019,1078 'professional-commun':1 'progress':418 'project':335,337 'project/topic':363 'proofread':1082 'prove':90 'provid':44 'purpos':183,365,1022 'qa':214 'question':344,346,486,602,717 'queu':745 'quick':345,485,601,1012 'rate':348 're':58 'read':711 'reader':877 'readi':1092 'ready-to-us':1091 'real':495 'real-tim':494 'reason':202 'receiv':102 'recipi':246,1025,1057 'record':493 'refer':1013 'references/email-templates.md':452,1090 'references/jargon-simplification.md':775,1105 'references/meeting-structures.md':1011,1099 'releas':195,1141 'replac':701 'report':145,164 'request':376,424 'requir':447,506,573,921 'respons':575 'restructur':884 'retest':216 'retro':1103 'reveal':825 'review':508,556,1104 'right':546,549,1031 'room':713 'rule':236 'sarah':600 'scale':738 'scannabl':260,528,1046 'schedul':354 'script':606 'second':1030 'see':451,774,1010 'seen':616 'send':1017 'sensit':511 'sentenc':370 'separ':739 'share':932,1004 'short':488,1051 'simplif':680 'simplifi':695 'skill':43,109,112,1113 'skill-professional-communication' 'slack':155,459 'smaller':733 'softwar':8,53 'solut':437 'someth':594 'source-softaworks' 'specif':364,390,646 'spend':943 'split':731 'stakehold':63,120,222,296,501,660 'standup':1102 'start':241,682 'state':186,276,371 'status':142,162,227,339,416 'step':343,401,422,995 'steps/action':212 'store':770 'strategi':678 'structur':12,141,172,359,1006,1100 'subject':329,362 'subject/purpose':245 'summari':132,419,434,970 'switch':710 'system':729 'talk':230 'task':743,987,991 'team':13,66,122,154,453,468,472,503,518,803,805 'teammat':117 'technic':5,22,26,134,139,232,293,625,629,634,641,647,659,723,1107 'technical-to-plain-languag':1106 'templat':360,450,1096 'terminolog':460,1073 'test':756,823,824,865 'text':267,582,597 'thought':537 'thread':524,534 'three':234,677 'thursday':218 'time':496,510,837,917,938 'time-box':937 'time-sensit':509 'timelin':395,423 'tip':936 'tone':1074 'tool':1089 'topic':550,913,965,974 'topic-agent-skills' 'topic-automation' 'topic-claude' 'topic-claude-code' 'topic-coding-agent' 'topic-development' 'topic/request':188 'translat':133,721,1111 'tri':334,596 'tuesday':356 'type':412,413,1009,1098 'typo':1084 'unclear':1086 'understand':1026,1071 'understood':104 'univers':175 'unnecessarili':542 'up':531 'updat':143,163,221,228,336,340,417,512,763,1130 'upfront':280,377,1045 'use':28,107,110,173,256,458,477,481,483,523,699,832,1094,1126 'v1.0.0':1136 'valu':317 'value/impact':891 'version':1134 'voic':780,783,785 'vs':23,310,479,626,635 'wait':595 'wall':265 'want':263,856 'week':198 'what-why-how':168 'whether':56 'without':696 'word':829 'work/decisions':325 'write':59,114,158,291,568,776,867 'writt':38 'written':149,238 'x':338","prices":[{"id":"8a62e121-8ade-4484-b23a-e5888c290ff1","listingId":"997f25f0-d617-42c9-a062-aae1e0be1497","amountUsd":"0","unit":"free","nativeCurrency":null,"nativeAmount":null,"chain":null,"payTo":null,"paymentMethod":"skill-free","isPrimary":true,"details":{"org":"softaworks","category":"agent-toolkit","install_from":"skills.sh"},"createdAt":"2026-04-18T20:27:51.310Z"}],"sources":[{"listingId":"997f25f0-d617-42c9-a062-aae1e0be1497","source":"github","sourceId":"softaworks/agent-toolkit/professional-communication","sourceUrl":"https://github.com/softaworks/agent-toolkit/tree/main/skills/professional-communication","isPrimary":false,"firstSeenAt":"2026-04-18T21:54:42.369Z","lastSeenAt":"2026-05-18T18:52:58.697Z"},{"listingId":"997f25f0-d617-42c9-a062-aae1e0be1497","source":"skills_sh","sourceId":"softaworks/agent-toolkit/professional-communication","sourceUrl":"https://skills.sh/softaworks/agent-toolkit/professional-communication","isPrimary":true,"firstSeenAt":"2026-04-18T20:27:51.310Z","lastSeenAt":"2026-05-07T22:40:50.804Z"}],"details":{"listingId":"997f25f0-d617-42c9-a062-aae1e0be1497","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"softaworks","slug":"professional-communication","github":{"repo":"softaworks/agent-toolkit","stars":1847,"topics":["agent-skills","ai","automation","claude","claude-code","coding-agent","development"],"license":"mit","html_url":"https://github.com/softaworks/agent-toolkit","pushed_at":"2026-03-05T16:46:24Z","description":"A curated collection of skills for AI coding agents. Skills are packaged instructions and scripts that extend agent capabilities across development, documentation, planning, and professional workflows.","skill_md_sha":"d8b50a2d9d28afb2a567db5dcd68ce4f35446044","skill_md_path":"skills/professional-communication/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/softaworks/agent-toolkit/tree/main/skills/professional-communication"},"layout":"multi","source":"github","category":"agent-toolkit","frontmatter":{"name":"professional-communication","description":"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."},"skills_sh_url":"https://skills.sh/softaworks/agent-toolkit/professional-communication"},"updatedAt":"2026-05-18T18:52:58.697Z"}}