team-communications
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseInternal Comms
内部沟通
Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.
Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.
最初由maximcoding贡献——经claude-skills团队优化整合。
通过加载合适的参考文件、收集上下文信息，并严格按照公司格式输出，撰写专业规范的内部沟通内容。
Routing
分类匹配
Identify the communication type from the user's request, then read the matching reference file before writing anything:
| Type | Trigger phrases | Reference file |
|---|---|---|
| 3P Update | "3P", "progress plans problems", "weekly team update", "what did we ship" | |
| Newsletter | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | |
| FAQ | "FAQ", "common questions", "what people are asking", "confusion around" | |
| General | anything internal that doesn't match above | |
If the type is ambiguous, ask one clarifying question — don't guess.
从用户的请求中识别沟通类型，然后在撰写前读取对应的参考文件：
| 类型 | 触发短语 | 参考文件 |
|---|---|---|
| 3P更新 | "3P"、"进展/计划/问题"、"每周团队更新"、"我们交付了什么" | |
| 通讯 | "通讯"、"公司更新"、"每周/每月汇总"、"全员会议总结" | |
| FAQ | "FAQ"、"常见问题"、"大家的疑问"、"关于...的困惑" | |
| 通用类 | 所有不匹配上述类型的内部沟通内容 | |
若类型不明确，请提出一个澄清问题——切勿猜测。
Workflow
工作流程
- Read the reference file for the matched type. Follow its formatting exactly.
- Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
- Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
- Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
- Present the draft and ask if anything needs to be added, removed, or reworded.
- 读取对应类型的参考文件。严格遵循其格式要求。
- 收集输入信息。使用可用的MCP工具（Slack、Gmail、Google Drive、Calendar）获取真实数据。若未连接任何工具，请用户提供要点或原始上下文信息。
- 明确范围。确认：团队名称（针对3P更新）、时间周期、受众群体，以及用户要求包含或排除的具体内容。
- 撰写草稿。严格遵循参考文件中的格式、语气和篇幅限制。不得自创格式。
- 提交草稿并询问是否需要添加、删除或修改内容。
Tone & Style (applies to all types)
语气与风格（适用于所有类型）
- Use "we" — you are part of the company.
- Active voice, present tense for progress, future tense for plans.
- Concise. Every sentence should carry information. Cut filler.
- Include metrics and links wherever possible.
- Professional but approachable — not corporate-speak.
- Put the most important information first.
- 使用“我们”——你是公司的一员。
- 主动语态，进展用现在时，计划用将来时。
- 简洁凝练。每句话都应传递有效信息，删除冗余内容。
- 尽可能包含指标和链接。
- 专业且亲和——避免生硬的官话。
- 重要信息前置。
When tools are unavailable
工具不可用时的处理
If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.
若用户未连接Slack、Gmail、Drive或Calendar，无需停滞。请用户粘贴或描述需要涵盖的内容。你的工作是格式化和优化内容——这依然具有价值。同时告知用户哪些工具可以提升未来的撰写效率，以便他们后续连接。
Anti-Patterns
反模式
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |
| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |
| Using passive voice for accomplishments | "The feature was shipped" hides who did the work | "Team X shipped the feature" — active voice credits the team |
| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |
| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |
| 反模式 | 失败原因 | 改进方案 |
|---|---|---|
| 未先阅读参考模板就撰写更新内容 | 输出不符合公司格式——用户需重新排版 | 撰写前务必加载匹配的参考文件 |
| 编造指标或成果 | 内部沟通必须真实可靠——造假会破坏信任 | 仅包含用户提供或MCP工具获取的数据 |
| 用被动语态描述成果 | "功能已交付"掩盖了执行者 | "X团队交付了该功能"——主动语态明确团队贡献 |
| 状态更新写成长篇大段 | 领导层只会浏览而非通读——关键信息被埋没 | 先给出核心要点，再用3-5个要点展开 |
| 未确认受众就发送内容 | 团队更新与全公司通讯的表述方式截然不同 | 务必确认：这份内容的阅读对象是谁？ |
Related Skills
相关Skill
| Skill | Relationship |
|---|---|
| Broader PM scope — status reports feed into PM reporting |
| Meeting insights can feed into 3P updates and status reports |
| Publish comms as Confluence pages for permanent record |
| External comms — use for public-facing content, not internal |
| Skill | 关联关系 |
|---|---|
| 更广泛的PM范畴——状态报告是PM汇报的组成部分 |
| 会议洞察可用于3P更新和状态报告 |
| 将沟通内容发布为Confluence页面，形成永久记录 |
| 外部沟通——适用于面向公众的内容，而非内部内容 |