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.

Security Scan

The skill is an instruction-only collection of templates and guidance for professional messages; its requirements, instructions, and files align with that purpose and it does not request credentials, install code, or perform unexpected actions.

Purpose & Capability

Name/description (professional messaging) match the delivered artifacts: a SKILL.md and four reference documents with templates and guides. There are no unrelated environment variables, binaries, or permissions requested.

Instruction Scope

SKILL.md tells the agent to use local reference files and follow message templates/heuristics. It does not instruct reading system files, accessing secrets, contacting external endpoints, or doing anything beyond drafting/formatting communication.

Install Mechanism

No install spec is declared in registry metadata and there are no code files. README/SKILL.md mention optional npx/clawhub or manual copy commands to install the skill locally — these are typical distribution hints and not automatic downloads executed by the skill itself.

Credentials

The skill requires no environment variables, credentials, or configuration paths. Templates and guides are self-contained and do not justify any secret access.

Persistence & Privilege

Skill is not forced-always, is user-invocable, and allows model invocation (the platform default). It does not request persistent system modifications or alter other skills' configs.

Assessment

This is an instruction-only skill made of templates and writing guidance — generally low risk. Before installing or running any provided npx/clawhub commands, confirm the install command's source (npx may fetch packages). If you allow the agent to invoke skills autonomously, this particular skill has no extra privileges or credentials to expose. As a best practice, review templates before sending messages to ensure you don't accidentally include sensitive information (names, internal links, credentials) when using or auto-populating templates.

Write clear, effective professional messages that get read and acted upon.

Installation

OpenClaw / Moltbot / Clawbot

npx clawhub@latest install professional-communication

WHAT This Skill Does

Routes you to ready-to-use templates and translation guides for professional technical communication.

WHEN To Use

• Drafting emails (status updates, requests, escalations, introductions)
• Writing Slack/Teams messages
• Preparing meeting agendas or summaries
• Translating technical concepts for non-technical audiences
• Any written communication to teammates, managers, or stakeholders

Core Principle

Key message first. Scannable format. Clear action requested.

Every professional message answers: What do you need to know? Why does it matter? What action (if any) is needed?

Quick Reference: Message Structure

Subject: [Topic]: [Specific Purpose]

[1-2 sentences: key point or request upfront]

**Context:** (if needed)
- Bullet points, not paragraphs

**Action Needed:**
- Specific request with timeline

Route to References

Task	Load This Reference
Writing any email	MANDATORY: Load references/email-templates.md
Explaining technical concepts to non-technical people	MANDATORY: Load references/jargon-simplification.md
Running or preparing for meetings	MANDATORY: Load references/meeting-structures.md
Async/remote team communication	Load references/remote-async-communication.md

The Four Rules

1. Subject lines tell the story - "Project X: Decision Needed by Friday" beats "Question"
2. Bullets over paragraphs - Nobody reads walls of text
3. Specific asks - "Please review by Thursday" beats "Let me know"
4. Match the channel - Chat for quick/informal, Email for records/formal

NEVER

• Send a message without a clear purpose in the first sentence
• Use "Just checking in" without context (include what you're checking on)
• Write paragraphs when bullets would work
• Bury the ask at the bottom
• Use jargon with non-technical audiences
• Send walls of text in chat (use threads)
• Reply-all unnecessarily
• Use passive voice when active is clearer ("We decided" not "It was decided")