Home / All Skills / Workflow & Core Tools / internal-comms
English (EN)简体中文 (ZH)日本語 (JA)
Workflow & Core Tools · anthropics/skills

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

L2 Local · Restricted workspaceV1 Commit-PinnedWrite FileDual-pass Audit
Author anthropicsGitHub anthropics/skills ↗Stars 175386License Apache-2.0（自带 LICENSE.txt；Copyright 2026 Anthropic, PBC.）Commit 41bbe19d1a
Control levels describe skill capabilities and suggested control measures; they do not represent quality or safety certifications, nor do they dictate usability. Usage decisions rest entirely with users and administrators. Different agent hosts apply varying constraints; do not assume hosts provide automatic protection. Third-party skill copyrights belong to their original authors. Use at your own risk.

1How It Works & Mechanism

The mechanism functions as a routing table of 'Type Identification → Load Corresponding Guide File': SKILL.md itself is only 32 lines long, with all substantive content offloaded to 4 categorized guides under examples/.

skills/internal-comms/SKILL.md
2. **Load the appropriate guideline file** from the `examples/` directory:
Mapping: 3p-updates.md → Progress/Plans/Problems team updates; company-newsletter.md → company-wide newsletters; faq-answers.md → FAQ responses; general-comms.md → everything else (status/leadership/project/incident updates all fall here).

Each guide has built-in sections for 'Audience Definition + Sourcing + Strict Formatting': it first defines the reader and reading time, then directs retrieval from company data sources as much as possible, and finally provides an immutable format.

skills/internal-comms/examples/3p-updates.md
The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less.
The 3P guide specifies that each of the three sections (Progress/Plans/Problems) must be 1-3 sentences, data-driven, and include metrics, enforcing a rigid format header: '[pick an emoji] [Team Name] (Dates Covered, usually a week)'.

Material sourcing prioritizes host tools (Slack/Google Drive/Email/Calendar) and only falls back to asking the user when permissions are missing—the skill carries no connectors itself and relies entirely on existing host integrations.

skills/internal-comms/examples/company-newsletter.md
If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.
Retrieval signals are also concrete (looking for posts with high reactions/replies in major channels, executive all-hands emails, meetings with high attendance, etc.)—aiming to replace random information gathering with 'internal organizational popularity signals'.

Explicitly requests clarification rather than forcing a fit when types do not match: SKILL.md's fallback rules prevent shoehorning new communication types into existing templates.

skills/internal-comms/SKILL.md
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
general-comms.md provides a minimal workflow for 'non-matching but draftable' general scenarios: ask about audience/purpose/tone/format before starting to write.

2Core Capabilities

013P (Progress/Plans/Problems) weekly update writing: rigid format with emoji + team name + date range, 1-3 sentences per section, data-driven
02Company-wide newsletter drafting: ~20-25 bullet points, abundant links, written in 'we' voice, tailored for Slack/email distribution
03FAQ responses: synthesize consensus questions from high-frequency organizational queries and provide concise, unified answers
04General internal communications writing (status/leadership/project/incident updates): prior inquiry into audience, purpose, tone, and format
05Guidance on gathering internal organizational signals: high-engagement Slack posts, frequently viewed Drive docs, executive emails, and all-hands meetings

4Recommended Governance & Evidence

Suggested Controls for Safe Operation
For Agent Runtime
Restrict working directory
For Administrators
Retain operation logs
Evidence & Triggers (File Paths & Excerpts)
  • 本地文件: Manipulate local project files or workspace artifacts
Audit Notes: Pure Markdown guide skill: contains no scripts, no external network requests, no credential reading, and no write operations. Its behavior consists of reading the included examples/ guides and, following their instructions, reading internal company data sources (Slack/GDrive/Email/Calendar) via host tools to draft communications. Data exposure is strictly determined by host permissions (the skill itself touches zero code). Key considerations are the propagation risk of fabricated or inaccurate internal communication content and the need to adapt what are essentially Anthropic's internal example styles.

5Second-Pass Verification

  • [ok] examples 路由映射完整 — SKILL.md 列的 4 个文件名与目录 4 个文件一一对应；general-comms.md 覆盖兜底场景。
  • [ok] 无脚本无网络无凭证 — 全目录仅 6 个 md/txt 文件；token 扫描零命中。
  • [ok] 公司数据源=宿主工具而非 skill 自带 — 三份指南提到的 Slack/Drive/Email/Calendar 均为『tools available』式提示，skill 无 connector/API 代码——与 external_deps 空一致。
  • [ok] 描述与能力相符 — description 说 'formats that my company likes to use'——指南确实给出严格格式；但注意这些是 Anthropic 的示例风格，非用户公司定制（已在 fits/risks 提示适配）。
  • [ok] 承诺的通讯类型覆盖 — status/leadership/project/incident reports 由 general-comms 承接（SKILL.md 列表 + 'anything else' 兜底）——无夸大。
  • [ok] 元数据 — 本地 HEAD==pin 41bbe19；Apache-2.0 LICENSE.txt。

6Verdict & Scenarios

  • Extensible router architecture: adding a new communication format only requires adding a file under examples/, leaving SKILL.md untouched.
  • Strict formatting discipline to prevent drift: 3P fixed format + 'Never use any formatting other than this.' ensures consistent cross-session output.
  • Concrete material sourcing: guides the model to gather content using organizational heat signals (reactions, view counts, attendee numbers) rather than vague 'research'.
  • Lightweight with zero dependencies: pure Markdown guides that can be used directly by any host without introducing extra toolchains.
    • Best for: Suitable for small teams or companies that need high-frequency internal communications (3P weekly updates for product/engineering teams, company-wide newsletters from HR/Marketing, FAQ curation); ideal for organizations that have connected host tools like Slack/Drive/Email to maximize the value of 'automated sourcing'.
    Not for: Not suitable for scenarios lacking internal tool integrations where users also have no time to supply raw materials (which devolves into drafting from thin air); not suitable for creative internal communications requiring high formatting flexibility; not suitable for teams that copy the example style directly as company standards without any adaptation.
    Install Agent-Ready
    ① Verified Mirror 2026-09-09
    Option A · Direct DownloadDownload internal-comms.tar.gz
    sha256: 4202bcfb5ea09c32…
    Option B · Copy Guide for Agent
    install.json
    Agents automatically download and verify mirrors from this JSON guide.
    ② Upstream GitHub
    GitHub Repo ↗
    Pinned to commit 41bbe19d1a.