internal-comms 是内部沟通的”模板型纯指令”Skill——通过 SKILL.md 定义通用工作流，配合 4 个示例 .md 文件作为模板仓库，引导 Claude 为不同沟通场景生成符合公司格式的内容。
- 📋 多类型支持：3P 更新（Progress/Plans/Problems）、公司通讯、FAQ 回答、状态报告、领导层更新、项目更新、事故报告
- 📂 模板即示例：4 个示例文件对应不同沟通类型，既是规范也是参考——Claude 可直接遵循其格式
- 🔍 智能类型识别：根据用户请求自动识别沟通类型并加载对应模板
- 🎯 三步工作流：识别类型 → 加载模板 → 遵循指令，简洁高效
当用户请求编写内部沟通、状态报告、领导层更新、3P 更新、公司通讯、FAQ、事故报告、项目更新时触发。
One-Line Summary
Section titled “One-Line Summary”internal-comms is a “template-style pure-instruction” Skill for internal communications — using SKILL.md to define the general workflow, paired with 4 example .md files as template repositories, guiding Claude to generate company-format content for different communication scenarios.
Core Capabilities
Section titled “Core Capabilities”- 📋 Multi-type Support: 3P updates (Progress/Plans/Problems), company newsletters, FAQ responses, status reports, leadership updates, project updates, incident reports
- 📂 Examples as Templates: 4 example files covering different communication types — both specifications and references that Claude directly follows
- 🔍 Smart Type Recognition: Automatically identifies the communication type from user requests and loads the corresponding template
- 🎯 Three-Step Workflow: Identify type → Load template → Follow instructions, simple and efficient
Trigger Scenarios
Section titled “Trigger Scenarios”Triggers when users request internal communications, status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates.
File Inventory
Section titled “File Inventory”- internal-comms
目录结构分析
Section titled “目录结构分析”internal-comms 的结构属于**“分离式指令”（Split Instruction）** 型——主入口 SKILL.md 负责路由，示例文件承担格式规范。
internal-comms/├── SKILL.md ← 总入口（~32 行）：定义工作流 + 路由逻辑├── LICENSE.txt ← 许可证└── examples/ ← 模板仓库 ├── 3p-updates.md ← 3P（Progress/Plans/Problems）更新 ├── company-newsletter.md ← 公司全员通讯 ├── faq-answers.md ← FAQ 回答 └── general-comms.md ← 通用沟通（兜底模板）SKILL.md 结构解析
Section titled “SKILL.md 结构解析”仅约 32 行的 SKILL.md 承担了两个关键角色：
1. “何时使用”声明（~8 行）
列出 7 种内部沟通场景——既是触发判断条件，也告知用户可用范围。
2. “如何使用”工作流（~22 行）
定义了极其简洁的三步流程：
- 识别类型：从用户请求判断所需的沟通类型
- 加载模板：从
examples/读取对应的指南文件 - 遵循指令：按照模板中的格式、语气和内容指导生成输出
”示例即模板”模式分析
Section titled “”示例即模板”模式分析”这是 internal-comms 最核心的设计决策——不是用 SKILL.md 描述格式，而是用独立的示例文件展示格式。
这种分离的设计带来几个好处：
- 关注点分离：主文件管”流程”，示例文件管”格式”
- 易于扩展：添加新沟通类型只需在 examples/ 中新增文件，SKILL.md 几乎无需修改
- 示例即文档：示例文件本身就是最佳参考——Claude 可以直接学习格式而不需要额外的格式描述
- 低认知负荷：SKILL.md 只有 32 行，极其精简
Directory Structure Analysis
Section titled “Directory Structure Analysis”internal-comms follows a “Split Instruction” pattern — the main SKILL.md handles routing, while example files carry format specifications.
Overall Architecture
Section titled “Overall Architecture”internal-comms/├── SKILL.md ← Main entry (~32 lines): workflow + routing logic├── LICENSE.txt ← License└── examples/ ← Template repository ├── 3p-updates.md ← 3P (Progress/Plans/Problems) updates ├── company-newsletter.md ← Company-wide newsletters ├── faq-answers.md ← FAQ responses └── general-comms.md ← General communications (catch-all)SKILL.md Structure Analysis
Section titled “SKILL.md Structure Analysis”At only ~32 lines, SKILL.md handles two key roles:
1. “When to Use” Declaration (~8 lines)
Lists 7 internal communication scenarios — serving as both trigger conditions and a capability overview for users.
2. “How to Use” Workflow (~22 lines)
Defines an extremely concise three-step process:
- Identify type: Determine the required communication type from the user’s request
- Load template: Read the corresponding guideline file from
examples/ - Follow instructions: Generate output following the template’s format, tone, and content guidance
The “Examples as Templates” Pattern
Section titled “The “Examples as Templates” Pattern”This is internal-comms’s core design decision — using independent example files to showcase format rather than describing format in SKILL.md.
This separation brings several benefits:
- Separation of concerns: Main file handles “flow”, example files handle “format”
- Easy to extend: Adding a new communication type requires only adding a file to examples/, with minimal SKILL.md changes
- Examples as documentation: Example files serve as the best reference — Claude can learn format directly without additional format descriptions
- Low cognitive load: SKILL.md stays extremely lean at only 32 lines
| 示例文件 | 沟通类型 | 特征 |
|---|---|---|
3p-updates.md | 团队 3P 更新 | Progress/Plans/Problems 三栏结构，侧重事实和指标 |
company-newsletter.md | 公司全员通讯 | 叙事风格，含引言、主要章节、行动呼吁 |
faq-answers.md | FAQ 回答 | 问题-答案对格式，侧重清晰和简洁 |
general-comms.md | 通用沟通 | 灵活的兜底模板，覆盖其他未明确列出的类型 |
| Example File | Communication Type | Characteristics |
|---|---|---|
3p-updates.md | Team 3P Updates | Progress/Plans/Problems three-column structure, facts and metrics focused |
company-newsletter.md | Company Newsletters | Narrative style with introduction, main sections, call to action |
faq-answers.md | FAQ Responses | Question-answer pair format, clarity and conciseness focused |
general-comms.md | General Communications | Flexible catch-all template, covers types not explicitly listed |
internal-comms 不包含任何脚本、模板引擎或自动化工具。
“示例即模板”模式的深度分析
Section titled ““示例即模板”模式的深度分析”这是纯指令模式的一个变体——用示例文件替代模板引擎。在脚本驱动型的 skill 中，格式通常由 Python/JS 脚本或模板引擎（Jinja2、Handlebars 等）控制；在 internal-comms 中，格式规范直接写在 .md 文件中，Claude 通过阅读本身来理解并遵循格式。
四个示例文件的角色分析
Section titled “四个示例文件的角色分析”1. 3p-updates.md
3P 更新（Progress/Plans/Problems）是团队沟通的常见格式。该示例定义了：
- 三栏布局结构
- 每栏的内容类型（事实陈述 vs 数据分析 vs 风险评估）
- 更新频率和粒度
- 读者期望（领导层快速获取关键信息）
2. company-newsletter.md
公司通讯需要更具叙事性和人文色彩。该示例定义了：
- 引入/问候段落
- 按重要性排列的主要章节
- 数据/指标的视觉呈现方式
- 结尾的行动呼吁或联系信息
3. faq-answers.md
FAQ 回答追求最大的清晰度和可搜索性。该示例定义了：
- 问题-答案的直接配对结构
- 回答的层级（一句话总结 → 详细解释 → 关联问题）
- 术语一致性要求
4. general-comms.md
通用沟通是兜底模板，覆盖不属于以上三类的沟通场景。它定义了最少的结构约束——主要关注语气和内容组织原则。
“示例即模板” vs 传统模板引擎
Section titled ““示例即模板” vs 传统模板引擎”与 Jinja2/Handlebars 等模板引擎不同，.md 格式示例的优势在于：
- Claude 可以直接”阅读”并理解格式，无需解析模板语法
- 示例可以包含丰富的上下文和注释，指导”为何”而非”如何”
- 不需要额外的渲染步骤或依赖
Script Inventory
Section titled “Script Inventory”internal-comms contains no scripts, template engines, or automation tools.
Deep Analysis of the “Examples as Templates” Pattern
Section titled “Deep Analysis of the “Examples as Templates” Pattern”This is a variant of the pure instruction pattern — using example files to replace template engines. In script-driven skills, format is typically controlled by Python/JS scripts or template engines (Jinja2, Handlebars, etc.); in internal-comms, format specifications are written directly in .md files, and Claude understands and follows the format by reading them.
Role Analysis of the Four Example Files
Section titled “Role Analysis of the Four Example Files”1. 3p-updates.md
3P updates (Progress/Plans/Problems) are a common team communication format. This example defines:
- Three-column layout structure
- Content type per column (factual statements vs data analysis vs risk assessment)
- Update frequency and granularity
- Reader expectations (leadership quickly accessing key information)
2. company-newsletter.md
Company newsletters require a more narrative and human touch. This example defines:
- Introduction/greeting paragraph
- Major sections ordered by importance
- Visual presentation of data/metrics
- Ending call to action or contact information
3. faq-answers.md
FAQ responses pursue maximum clarity and searchability. This example defines:
- Direct question-answer pairing structure
- Answer hierarchy (one-line summary → detailed explanation → related questions)
- Terminology consistency requirements
4. general-comms.md
General communications is the catch-all template, covering scenarios not matching the above three. It defines minimal structural constraints — focusing primarily on tone and content organization principles.
”Examples as Templates” vs Traditional Template Engines
Section titled “”Examples as Templates” vs Traditional Template Engines”Unlike template engines like Jinja2/Handlebars, .md format examples offer advantages:
- Claude can “read” and understand the format directly, without parsing template syntax
- Examples can include rich context and annotations, guiding “why” rather than “how”
- No additional rendering steps or dependencies required
| 沟通类型 | 模板定位 | 格式特点 |
|---|---|---|
| 3P 更新 | 高结构化的团队更新 | 三栏布局、指标驱动、事实优先 |
| 公司通讯 | 叙事风格的全员沟通 | 段落式、故事线、行动呼吁 |
| FAQ 回答 | 最大化清晰度 | 问答对、层级结构、术语一致 |
| 通用沟通 | 兜底灵活模板 | 最少约束、语气和原则驱动 |
| Type | Template Role | Format Characteristics |
|---|---|---|
| 3P Updates | Highly structured team updates | Three-column layout, metrics-driven, facts first |
| Company Newsletter | Narrative-style all-hands communication | Paragraph-based, story arc, call to action |
| FAQ Responses | Maximum clarity | Q&A pairs, hierarchical structure, terminology consistency |
| General Comms | Flexible catch-all | Minimal constraints, tone and principle-driven |
- “示例即模板”模式：用真实示例文件而非模板语法定义格式——Claude 可以直接”阅读”格式规范，无需解析模板引擎
- 极简主入口：32 行 SKILL.md 只负责路由，格式细节全部委托给示例文件——关注点分离的典范
- 四类覆盖全面：从高结构化的 3P 更新到灵活的通用沟通，覆盖了企业内部沟通的主要场景
- 低扩展门槛：新增沟通类型只需在 examples/ 目录下加文件，SKILL.md 几乎无需修改——“热插拔”式扩展
- 示例即文档：示例文件同时承担”规范”和”参考”双重角色，减少了维护两套文档的成本
- 语义化路由：通过识别用户请求中的场景关键词自动路由到对应模板——用户无需了解文件位置
“如果你想为你的企业创建沟通模板 Skill…”
- 定义场景清单：列出团队常用的沟通类型和触发关键词
- 创建示例文件：每个场景一个 .md 文件，包含格式、语气和内容规范
- 编写路由规则：在 SKILL.md 中定义类型识别和模板加载逻辑
- 提供兜底模板：总有一个”通用”模板覆盖未明确列出的场景
- 定期更新示例：企业沟通格式会演变——示例文件需要保持最新
⚠️ 模板可能过时： 随着企业沟通风格演变，示例文件需要定期更新——否则 Claude 可能产出过时的格式
⚠️ 示例可能被误解： Claude 可能把示例的内容（示例文本本身）误认为是用户的实际内容——需要明确区分”这是示例格式”和”这是实际内容”
⚠️ 路由不够精准： “识别沟通类型”听起来简单，但用户的请求可能是模糊的”帮我写点东西”——需要更详细的触发规则和兜底机制
⚠️ 缺乏格式验证： 没有脚本驱动，Claude 可能偏离模板格式——纯指令模式在一致性方面较弱
⚠️ 模板数量膨胀： 随着时间推移，examples/ 目录可能积累过多模板——需要合理的分类和淘汰机制
Design Highlights
Section titled “Design Highlights”- “Examples as Templates” Pattern: Using real example files rather than template syntax to define format — Claude “reads” format specifications directly without parsing template engines
- Ultra-Minimal Main Entry: 32-line SKILL.md handles routing only, format details delegated to example files — exemplar of separation of concerns
- Comprehensive Coverage: From highly structured 3P updates to flexible general communications, covering major enterprise internal communication scenarios
- Low Extension Barrier: Adding a new communication type requires only adding a file to examples/ — “hot-pluggable” extension
- Examples as Documentation: Example files serve dual roles of “specification” and “reference”, reducing dual-documentation costs
- Semantic Routing: Auto-routes to the appropriate template by recognizing scenario keywords in user requests — users don’t need to know file locations
Reusable Patterns
Section titled “Reusable Patterns”Porting Guide
Section titled “Porting Guide”“If you want to create a communication template Skill for your enterprise…”
- Define scenario inventory: List commonly used communication types and trigger keywords for your team
- Create example files: One .md file per scenario, containing format, tone, and content specifications
- Write routing rules: Define type identification and template loading logic in SKILL.md
- Provide catch-all template: Always have a “general” template for unlisted scenarios
- Update examples regularly: Enterprise communication formats evolve — example files need to stay current
Common Pitfalls
Section titled “Common Pitfalls”⚠️ Templates can become outdated: As enterprise communication styles evolve, example files need regular updates — otherwise Claude may produce outdated formats
⚠️ Examples may be misinterpreted: Claude might mistake example content (sample text) for actual user content — need to clearly distinguish “this is example format” from “this is actual content”
⚠️ Routing imprecision: “Identify communication type” sounds simple, but user requests may be vague like “help me write something” — needs more detailed trigger rules and fallback mechanisms
⚠️ No format validation: Without scripts driving it, Claude may deviate from template format — pure instruction mode is weaker in consistency
⚠️ Template proliferation: Over time, examples/ directory may accumulate too many templates — needs reasonable categorization and retirement mechanisms
| 模式 | 说明 | 适用于... |
|---|---|---|
| 示例即模板 | 用真实 .md 示例文件定义格式规范 | 有明确格式要求但需要灵活性的沟通场景 |
| 分离式指令 | 主文件管流程，示例文件管格式 | 有多种变体且格式复杂度低的技能 |
| 语义化路由 | 根据用户请求自动识别场景并加载对应模板 | 有多种触发场景的纯指令型 skill |
| 兜底模板 | 为未明确列出的场景提供通用格式 | 覆盖范围广、用户请求多样的技能 |
| Pattern | Description | Applies to... |
|---|---|---|
| Examples as Templates | Use real .md example files to define format specifications | Communication scenarios with clear format requirements but need flexibility |
| Split Instruction | Main file handles flow, example files handle format | Skills with multiple variants and low format complexity |
| Semantic Routing | Auto-identify scenarios from user requests and load templates | Pure instruction skills with multiple trigger scenarios |
| Catch-all Template | Provide general format for unlisted scenarios | Skills with broad coverage and diverse user requests |