
This is a surprisingly practical guide for writing emails, Slack messages, and meeting agendas that don't waste people's time. It covers the What-Why-How structure for organizing any message, when to use chat versus email, and how to translate technical jargon for non-technical stakeholders. The "No Hello" principle alone will save you from awkward waiting periods in chat. Use it when you're drafting status updates, preparing meeting communications, or need to explain a database migration without saying "database migration." The jargon translation table and email templates are genuinely useful references to keep handy.
npx -y skills add pedronauck/skills --skill professional-communication --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.