professional-communication

Guide technical communication for software developers across emails, team messages, and meetings.

567|82|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/pedronauck/skills --skill professional-communication-pedronauck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: professional-communication
Source: https://github.com/pedronauck/skills/tree/main/skills/professional-communication
Command: npx skills add https://github.com/pedronauck/skills --skill professional-communication-pedronauck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps software developers improve their written and verbal communication by providing frameworks and best practices for emails, team messages, and meetings, ensuring messages are clear, concise, and impactful.

Core Features & Use Cases

  • Email Structure: Learn to write effective subject lines and structure emails for clarity.
  • Team Messaging Etiquette: Master best practices for Slack, Teams, and other platforms, including the "No Hello" principle.
  • Audience Adaptation: Translate technical concepts for non-technical audiences.
  • Use Case: You need to write a status update email to stakeholders about a project delay. This Skill provides a template and guidance on how to clearly state the problem, impact, and next steps.

Quick Start

Use the professional-communication skill to draft a status update email about a project delay.

Frequently Asked Questions about professional-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a project status update email to stakeholders about a delay?

To write a project status update email, structure your message to clearly state the problem, its impact, and the next steps. Effective professional communication uses concise subject lines and logical structure to ensure stakeholders understand the delay and mitigation plan.

What is the "No Hello" principle for team messaging on Slack and Teams?

The "No Hello" principle in team messaging means skipping standalone greetings like "Hi" and immediately stating your request with full context. This messaging etiquette respects team bandwidth on platforms like Slack by enabling asynchronous responses without initial round-trip delays.

How do I adapt technical concepts for non-technical audiences in writing?

Adapting technical concepts for non-technical audiences requires translating jargon into business impact and clear outcomes. Professional communication frameworks guide you to restructure technical details into accessible language that stakeholders can easily act upon.

What's the best way to structure a meeting agenda for a software development team?

The best way to structure a meeting agenda is to define clear objectives, allocate specific time slots, and list required pre-reading. Following professional communication frameworks ensures technical meetings stay focused and produce actionable outcomes.

Can I use this to improve both written emails and verbal meeting communication?

Yes, you can use this framework to improve both written emails and verbal meeting communication. It provides best practices for structuring emails and planning meeting agendas, ensuring your technical communication is clear and impactful across different mediums.

Does this help with drafting messages for technical vs non-technical team members?

Yes, this helps draft messages by providing frameworks to adapt your writing for technical versus non-technical audiences. It guides software developers in adjusting message depth and terminology based on the recipient's background.