Professional Communication

👤 wpank 📦 v0.1.0 ⭐ 4.4 ⬇️ 2.5K 下載
📄 辦公效率 免費

📖 技能介紹

Professional Communication

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)

    想要更強大的技能外掛,就來小蔥技能站7w4.net看看吧。

  • 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")

🤖 AI 評測

這是一套幫助軟體開發者寫好專業訊息的技能工具,提供了實用的溝通規則和可直接套用的模板,容易上手。整體質量不錯,結構清晰、覆蓋場景廣,術語翻譯和會議模板特別實用。不足之處是部分內容深度一般,缺少測試保障質量,細節打磨還有提升空間。對於日常需要寫郵件、開會的開發者來說,這是一款值得一試的工具。

📊 多維度評分

適應性4
規範性4.6
有效性4.7
可靠性3.9
可信度4.4

📁 包含檔案 (7 個)

📄 README.md 1.9 KB
📄 SKILL.md 2.8 KB
📄 _meta.json 145 B
📄 references/email-templates.md 5.6 KB
📄 references/jargon-simplification.md 7.9 KB
📄 references/meeting-structures.md 8.6 KB
📄 references/remote-async-communication.md 7.9 KB