Content & Marketing · IN-DEPTH PROFILE

internal-comms

Format-aware drafting for status reports, leadership updates, newsletters, FAQs, and incident reports.

Best for

Team leads and program managers writing recurring updates

What you get

Route by communication type + Reuse company patterns

Main limitation

The included examples reflect Anthropic's preferred formats and must be adapted to another organization.

First risk

Confidential information in broad-audience drafts. Status and incident reports can contain customer, employee, operational, or security-sensitive details. Confirm audience and classification before drafting or distributing.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 0a64e398

Open pinned commit
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Internal Comms is Anthropic's format router for recurring company communication. It identifies whether a request is a 3P update, newsletter, FAQ, status report, leadership update, project update, or incident report, then loads the matching example guidance before drafting.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.claude/skills/internal-comms/
Personal scope~/.claude/skills/internal-comms/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add anthropics/skills --skill internal-comms --agent claude-code
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence

TYPICAL WORKFLOW

A practical workflow

01

Route by communication type

Select the matching format before writing.

02

Reuse company patterns

Ground the draft in dedicated examples for updates, newsletters, or FAQs.

03

Standardize recurring updates

Keep common internal messages consistent across authors.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. A small routing layer keeps format guidance separate and reusable.
  2. Covers several recurring internal communication patterns without pretending they are identical.

Limitations

  1. The included examples reflect Anthropic's preferred formats and must be adapted to another organization.
  2. It improves structure and consistency but cannot verify confidential facts or organizational tone by itself.

BEST FIT

Who it is for

Team leads and program managers writing recurring updates

Internal communications and operations teams

BEFORE YOU USE IT

Risks to review before use

High

Confidential information in broad-audience drafts

Status and incident reports can contain customer, employee, operational, or security-sensitive details. Confirm audience and classification before drafting or distributing.

SECURITY

What the permission profile means

  • Confirm the intended audience before including incident or leadership details.
  • Use placeholders for unverified metrics and names until an owner approves them.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked
examples/Upstream package contentSource-linked

TAGS

internal-commsstatus-updatesincident-reports

Original SkillSignal editorial profile grounded in the current SKILL.md and linked files at pinned Anthropic commit 0a64e398, checked 2026-08-20; not independently executed or security-certified.