playbooks

home / skills / nickcrew / claude-cortex / internal-comms

internal-comms skill

/skills/internal-comms

This skill helps craft internal communications like 3P updates, newsletters, and incident reports by following guided templates and tone.

npx playbooks add skill nickcrew/claude-cortex --skill internal-comms

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
1.4 KB
---
name: internal-comms
description: A set of resources to help write all kinds of internal communications, using company-specific formats. Use when asked to write internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
license: MIT License - Complete terms in LICENSE.txt
---

## 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

Overview

This skill is a toolkit for writing clear, company-specific internal communications across formats like 3P updates, newsletters, FAQs, status reports, leadership updates, project summaries, and incident reports. It applies consistent formatting and tone using ready-made guideline files so messages are fast to produce and easy to consume. The goal is reliable, audience-appropriate internal comms that reduce back-and-forth and align teams.

How this skill works

Identify the requested communication type and load the matching guideline from the examples directory. Each guideline prescribes structure, tone, and required fields (for example, Progress/Plans/Problems for 3P updates or audience callouts for newsletters). If the type is ambiguous, request clarification or additional context before drafting.

When to use it

  • Progress, Plans, Problems (3P) team updates
  • Company-wide newsletters and announcements
  • Status reports for projects or operations
  • Leadership updates and executive summaries
  • Incident reports and postmortems
  • FAQ answers and internal knowledge replies

Best practices

  • Choose the guideline that best fits the target audience and stick to its structure
  • Lead with the most important information and include clear action items
  • Use consistent headings, timestamps, and ownership fields to speed comprehension
  • Keep language concrete and avoid jargon unless the audience expects it
  • When missing details, ask for specific inputs (metrics, owners, deadlines) before finalizing

Example use cases

  • Weekly 3P update: concise Progress, Plans, Problems with owners and blockers
  • Monthly company newsletter: highlights, metrics, and upcoming milestones for all teams
  • Incident notification: impact summary, immediate actions taken, and next steps
  • Leadership briefing: scoped status, risks, escalation needs, and decision requests
  • FAQ response collection: canonical answers formatted for internal knowledge base

FAQ

What if the request doesn't match an existing guideline?

Ask the requester to specify the desired format or provide a sample. If still unclear, use the general comms guideline and confirm structure before finalizing.

Which fields should always be included?

Include date, author/owner, audience, summary, key points or actions, and any relevant links or attachments.