Content
Share

Internal Communications

ByAnthropic·45.5k

Write professional internal communications: 3P updates, newsletters, FAQs, status reports, and project updates using company formats.

View on GitHub

How to Install

Using npx (recommended):

npx skills add github.com/anthropics/skills/tree/main/skills/internal-comms --skill internal-comms

This will automatically download and install the skill in your .cursor/skills/ directory.

Or install manually:

  1. Copy the skill content below
  2. Create folder: .cursor/skills/internal-comms/ in your project
  3. Save as SKILL.md
  4. Cursor auto-discovers skills when you start a chat

Or install globally to ~/.cursor/skills/internal-comms/SKILL.md

Official Cursor Skills Docs

SKILL.md

---
name: internal-comms
description: Write internal communications using company formats.
---

# Internal Communications Skill

## When to Use

Write internal communications for:
- 3P updates (Progress, Plans, Problems)
- Company newsletters
- FAQ responses
- Status reports
- Leadership updates
- Project updates
- Incident reports

## How to Use

1. **Identify the communication type** from the request
2. **Load the appropriate guideline** for the format
3. **Follow specific instructions** for formatting, tone, and content

## Communication Types

### 3P Updates (Progress, Plans, Problems)
Weekly team updates covering:
- **Progress**: What was accomplished
- **Plans**: What's coming next
- **Problems**: Blockers or challenges

### Company Newsletter
Organization-wide communications:
- Executive summary
- Key achievements
- Upcoming events
- Team spotlights

### FAQ Answers
Structured Q&A format:
- Clear, concise answers
- Links to resources
- Contact information

### Status Reports
Project or team status:
- Current state summary
- Metrics and KPIs
- Risks and mitigations
- Next steps

### Leadership Updates
Executive communications:
- Strategic context
- Key decisions
- Call to action

### Project Updates
Stakeholder communications:
- Milestone progress
- Timeline updates
- Resource needs
- Decisions required

### Incident Reports
Post-incident documentation:
- Timeline of events
- Impact assessment
- Root cause
- Remediation steps

## Best Practices

- **Know your audience**: Adjust tone and detail level
- **Lead with the key message**: Don't bury the lede
- **Be concise**: Respect readers' time
- **Use formatting**: Headers, bullets, bold for scanability
- **Include next steps**: Clear action items
- **Proofread**: Check for clarity and errors

Best For

content designersux-writer designersproduct designers

Skills, agents & workflow notes

Weekly SKILL.md-style workflows, Cursor and Claude Code tips, and AI interface craft on Substack - no spam, unsubscribe anytime.

Subscribe on Substack