internal-comms

Internal Communications Skill

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "internal-comms" with this command: npx skills add vamseeachanta/workspace-hub/vamseeachanta-workspace-hub-internal-comms

Internal Communications Skill

Overview

This skill guides creation of professional internal communications that effectively inform, engage, and align employees with organizational goals and updates.

When to Use

  • Announcing company-wide policy changes

  • Creating team newsletters and updates

  • Writing executive communications

  • Drafting crisis communications

  • Sending policy memos

  • Any employee-facing messaging

Quick Start

  • Identify communication type (announcement, newsletter, memo, executive, crisis)

  • Select appropriate tone (professional, warm, formal, calm)

  • Use template structure for the type

  • Lead with important information (inverted pyramid)

  • Include clear next steps or call to action

Subject: [Action]: [Topic] Effective [Date]

Hi team,

[One sentence summary of what's changing]

Key Details:

  • [Detail 1]
  • [Detail 2]
  • [Detail 3]

Timeline: [When this takes effect]

Action Needed: [What people need to do]

Questions? [Contact info]

Thanks, [Name]

Communication Types

  1. Company-Wide Announcements

Use for: Major news, policy changes, organizational updates

Structure:

Subject: [Clear, Action-Oriented Subject Line]

[Opening - Why this matters to employees]

[Key Information - The what]

  • Bullet points for clarity
  • Specific dates and deadlines
  • Who is affected

[Context - The why]

[Action Required / Next Steps]

[Resources / Questions]

  • Contact information
  • Links to additional details

Example:

Subject: New Hybrid Work Policy Effective March 1

Team,

We're excited to announce our new hybrid work policy, developed based on your feedback from the recent employee survey.

What's Changing:

  • Flexible in-office days: Choose 2-3 days per week
  • Core collaboration hours: Tuesday-Thursday, 10am-3pm
  • Home office stipend: $500 one-time allowance

Why This Change: Based on 18 months of data showing maintained productivity and your feedback requesting more flexibility, we're making hybrid work permanent.

Next Steps:

  1. Discuss schedules with your manager by February 15
  2. Submit your preferred days via WorkDay by February 20
  3. Order equipment through the new home office portal

Questions? Reach out to HR at hybrid@company.com or join our FAQ session on February 10 at 2pm.

[Leadership Name]

  1. Team Updates / Newsletters

Use for: Regular team communications, project updates, wins

Structure:

[Team/Department] Update - [Date]

Highlights This Week/Month

  • Key accomplishment 1
  • Key accomplishment 2
  • Key accomplishment 3

In Progress

Brief updates on ongoing initiatives

Upcoming

  • Important dates
  • Deadlines
  • Events

Team Spotlight

Recognition of individual or team achievements

Resources & Reminders

  • Links to important docs
  • Policy reminders
  1. Policy Memos

Use for: New policies, procedure changes, compliance updates

Structure:

MEMORANDUM

TO: [Audience] FROM: [Sender/Department] DATE: [Date] RE: [Subject - Policy Name/Number]

PURPOSE Brief statement of why this memo is being issued.

POLICY STATEMENT Clear, concise statement of the policy.

SCOPE Who this policy applies to.

EFFECTIVE DATE When the policy takes effect.

KEY PROVISIONS

  1. Provision one with clear explanation
  2. Provision two with clear explanation
  3. Provision three with clear explanation

COMPLIANCE What employees need to do to comply.

QUESTIONS Contact information for questions.

ATTACHMENTS (if applicable)

  • Full policy document
  • FAQ
  • Training materials
  1. Executive Communications

Use for: CEO/leadership messages, company direction, culture

Tone: Personal, authentic, forward-looking

Structure:

[Personal greeting]

[Context/Current situation]

[Key message - the main point]

[Supporting details - why this matters]

[Call to action or ask]

[Expression of confidence/gratitude]

[Personal closing]

  1. Crisis Communications

Use for: Urgent situations, incidents, rapid response

Principles:

  • Speed over perfection (but be accurate)

  • Lead with facts known

  • Acknowledge what's unknown

  • Provide clear next steps

  • Commit to updates

Structure:

Subject: [URGENT/IMPORTANT] [Brief Description]

[What happened - facts only]

[What we're doing about it]

[What you need to do / don't need to do]

[When we'll update you next]

[How to get help if needed]

Writing Guidelines

Tone by Communication Type

Type Tone Example Phrase

Announcements Professional, clear "We're pleased to announce..."

Newsletters Warm, engaging "Great progress this month!"

Policy Formal, precise "Effective immediately, all employees must..."

Executive Authentic, inspiring "I want to share my perspective on..."

Crisis Calm, direct "Here's what we know..."

Best Practices

DO:

  • Lead with the most important information

  • Use bullet points for scanability

  • Include specific dates, names, and actions

  • Provide context for decisions

  • End with clear next steps

  • Keep paragraphs short (2-3 sentences)

DON'T:

  • Bury important information

  • Use jargon without explanation

  • Send without proofreading

  • Forget mobile readers (keep formatting simple)

  • Assume prior knowledge

  • Be vague about deadlines or responsibilities

Subject Line Formulas

Announcements:

  • "[Action]: [Topic] Effective [Date]"

  • "Introducing: [New Thing]"

  • "Update: [Topic] Changes"

Newsletters:

  • "[Team] Weekly: [Date Range]"

  • "[Month] Update: [Key Theme]"

Urgent:

  • "[URGENT] [Brief Description]"

  • "[ACTION REQUIRED] [Topic] by [Date]"

Templates

Quick Announcement Template

Subject: [Topic] - [Key Point]

Hi team,

[One sentence summary of what's changing/happening]

Key Details:

  • [Detail 1]
  • [Detail 2]
  • [Detail 3]

Timeline: [When this takes effect]

Action Needed: [What people need to do, if anything]

Questions? [Contact info]

Thanks, [Name]

Weekly Team Update Template

[Team] Update - Week of [Date]

Wins

  • [Achievement 1]
  • [Achievement 2]

Metrics

In Progress

  • [Project 1] - [Status]
  • [Project 2] - [Status]

Coming Up

  • [Event/Deadline 1] - [Date]
  • [Event/Deadline 2] - [Date]

FYI

  • [Important info]
  • [Reminder]

Distribution Considerations

Channel Selection

Content Type Best Channel

Urgent/Crisis Email + Slack + SMS

Company-wide announcements Email + All-hands

Team updates Slack/Teams channel

Policy changes Email + Intranet

Recognition Email + Slack + Newsletter

Timing

  • Avoid: Friday afternoons, Monday mornings (8-9am)

  • Best: Tuesday-Thursday, 10am-2pm

  • Urgent: Immediately, regardless of timing

  • Consider: Time zones for global teams

Execution Checklist

  • Identified correct communication type

  • Selected appropriate tone

  • Used relevant template

  • Led with most important information

  • Included specific dates and actions

  • Added clear next steps

  • Proofread for errors

  • Considered mobile formatting

  • Selected appropriate distribution channel

  • Scheduled for optimal timing

Error Handling

Common Issues

Issue: Low engagement/open rates

  • Cause: Unclear subject line or wrong timing

  • Solution: A/B test subject lines, send Tuesday-Thursday 10am-2pm

Issue: Confusion after announcement

  • Cause: Missing context or unclear next steps

  • Solution: Add "Why" section and explicit action items

Issue: Message feels impersonal

  • Cause: Overly formal or template-heavy

  • Solution: Add personal anecdotes, use "we" and "you"

Issue: Important info buried

  • Cause: Not using inverted pyramid structure

  • Solution: Lead with key point, details after

Metrics

Metric Target How to Measure

Email Open Rate

60% Email platform analytics

Click-through Rate

20% Email platform analytics

Read Time

30 seconds Intranet analytics

Questions Received Minimal Support ticket count

Action Completion

80% Survey or system tracking

Related Skills

  • doc-coauthoring - Collaborative editing

  • brand-guidelines - Brand voice consistency

  • slack-gif-creator - Celebration GIFs

Version History

  • 2.0.0 (2026-01-02): Upgraded to v2 template - added Quick Start, When to Use, Execution Checklist, Error Handling, Metrics sections

  • 1.0.0 (2024-10-15): Initial release with announcement, newsletter, memo, executive, and crisis communication templates

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

echarts

No summary provided by upstream source.

Repository SourceNeeds Review
General

pandoc

No summary provided by upstream source.

Repository SourceNeeds Review
General

mkdocs

No summary provided by upstream source.

Repository SourceNeeds Review
General

gis

No summary provided by upstream source.

Repository SourceNeeds Review