professional-communication
Frameworks and best practices for clear, professional communication across emails, team chat, meetings, and technical audiences.
- Covers four core areas: the What-Why-How structure for organizing messages, email templates with subject line formulas, team messaging etiquette including the "no hello" principle, and strategies for translating technical concepts to non-technical audiences
- Includes audience calibration guidance, jargon-to-plain-language translation examples, and clarity principles like active voice and eliminating filler words
- Provides meeting communication templates for agendas, action items, and post-meeting summaries with time-boxing tips
- Includes a pre-send communication checklist covering purpose clarity, audience fit, scannable formatting, and tone appropriateness
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
More from softaworks/agent-toolkit
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
4.0Khumanizer
|
3.9Kwriting-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
3.8Kqa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
3.7Kdatabase-schema-designer
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
3.7Kagent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
3.7K