professional-communication
Write effective professional messages for software teams. Use when drafting emails, Slack/Teams messages, meeting agendas, status updates, or translating technical concepts for non-technical audiences. Triggers on email, slack, teams, message, meeting agenda, status update, stakeholder communication, escalation, jargon translation.
Why use this skill?
Optimize your technical emails, Slack messages, and status updates with the OpenClaw professional-communication skill. Improve clarity and team efficiency.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/professional-communicationWhat This Skill Does
The professional-communication skill for OpenClaw is a specialized framework designed to refine, structure, and optimize how technical teams interact. It functions as a communication coach, ensuring that your written outputs are concise, actionable, and appropriately tailored to your target audience. By enforcing a 'Key Message First' approach, the skill eliminates ambiguity and ensures that stakeholders, project managers, and cross-functional partners receive information that they can act upon immediately.
Installation
To integrate this skill into your environment, use the following command:
npx clawhub@latest install professional-communication
Alternatively, you can utilize the internal package manager:
clawhub install openclaw/skills/skills/wpank/professional-communication
Use Cases
This skill is indispensable in high-velocity software environments where clarity reduces technical debt and prevents bottlenecking. Key use cases include:
- Escalations: Drafting neutral, fact-based risk reports when projects fall behind schedule.
- Stakeholder Updates: Summarizing complex backend performance improvements for non-technical leadership.
- Async Collaboration: Crafting structured Slack threads that keep discussions organized without burying context.
- Meeting Governance: Generating agendas that list objectives rather than just topics, ensuring meetings are productive and time-boxed.
- Jargon Translation: Converting deep architectural discussions into plain language for product managers or customers.
Example Prompts
- "Rewrite this Slack message about the database migration latency to be more professional, add a clear ask for the infrastructure team, and ensure the tone is collaborative rather than accusatory."
- "Draft an email status update to stakeholders regarding the Alpha release delay. Use the core professional structure: state the impact, provide the root cause in bullets, and define the revised timeline with specific action items."
- "Translate this technical documentation about our API rate-limiting logic into a two-paragraph summary suitable for a non-technical client-facing email."
Tips & Limitations
To maximize the effectiveness of the professional-communication skill, prioritize 'Scannability' over 'Personality.' Use the built-in reference libraries (like references/email-templates.md) to maintain organizational consistency. A major limitation is that the skill cannot inherently understand the political nuances of every unique workplace, so always review the generated output for tone before hitting send. Avoid relying on the tool to resolve sensitive personnel issues; it is designed for technical and project-related communication. Remember: if a message is longer than three paragraphs, you are likely failing to use the bullet-point structure correctly. Always place your 'Call to Action' early to ensure high response rates.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-professional-communication": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.