internal-comms
- 作者仓库星标 0
- 许可证 Complete terms in LICENSE.txt
- 作者更新于 2026年8月22日 01:10
- 作者仓库 skills
When to use this skill
To write internal communications, use this skill for:
- 3P updates (Progress, Plans, Problems)
- Company newsletters
- FAQ responses
- Status reports
- Leadership updates
- Project updates
- Incident reports
How to use this skill
To write any internal communication:
- Identify the communication type from the request
- Load the appropriate guideline file from the
examples/directory:examples/3p-updates.md- For Progress/Plans/Problems team updatesexamples/company-newsletter.md- For company-wide newslettersexamples/faq-answers.md- For answering frequently asked questionsexamples/general-comms.md- For anything else that doesn't explicitly match one of the above
- Follow the specific instructions in that file for formatting, tone, and content gathering
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
Keywords
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
- 流狐分类
- 通用
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @anthropics · Complete terms in LICENSE.txt
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。To write internal communications, use this skill for: 3P updates (Progress, Plans, Problems) Company newsletters
To write any internal communication: Identify the communication type from the request Load the appropriate guideline file from the examples/ directory:
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
## When to use this skill
To write internal communications, use this skill for:
- 3P updates (Progress, Plans, Problems)
- Company newsletters
- FAQ responses
- Status reports
- Leadership updates
- Project updates
- Incident reports
## How to use this skill
To write any internal communication:
1. **Identify the communication type** from the request
2. **Load the appropriate guideline file** from the `examples/` directory:
- `examples/3p-updates.md` - For Progress/Plans/Problems team updates
- `examples/company-newsletter.md` - For company-wide newsletters
- `examples/faq-answers.md` - For answering frequently asked questions
- `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
## Keywords
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> When to use this skill → How to use this skill → Keywords
要点 -> Identify the communication type · Load the appropriate guideline file · Follow the specific instructions · 1. Identify the communication type from the request 2. · If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
文件/命令 -> examples/ · examples/3p-updates.md · examples/company-newsletter.md · examples/faq-answers.md · examples/general-comms.md
内容 SHA-256 -> 744e31abd29b
设计思路
internal-comms是 Anthropic 出品的「内部沟通文案统一入口」——把日常常见的几类内部沟通（3P 进展、公司 newsletter、FAQ、leadership update、incident report 等）做了模板分流：你说要写哪类，skill 加载对应的examples/*.md指南，按模板走。它本身不写文字，写文字这一步交给具体模板。适用场景（按作者原文）
工作流
examples/：examples/3p-updates.md— 团队 3P 周报examples/company-newsletter.md— 全员通讯examples/faq-answers.md— FAQ 答复examples/general-comms.md— 都不匹配时的通用兜底类型不匹配任何模板时，问清楚或要更多上下文，不要硬猜。
关键词
3P updates / company newsletter / company comms / weekly update / faqs / common questions / updates / internal comms
适合谁
不适合
配套
doc-coauthoring（更系统的写作 SOP）、landing-report（事件总结）、document-release（发布相关沟通）。