# Internal Comms

> Use when writing internal status reports or team updates.

- Skill: `loopyluci/internal-comms` (Agent Skill)
- Install (CLI): `npx skillmds@latest add loopyluci/internal-comms`
- Raw SKILL.md: https://api.skillmd.com/api/skills/loopyluci/internal-comms/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: LoopyLuci (https://skillmd.com/u/loopyluci)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/loopyluci/internal-comms

---


# Internal Communications

Write professional internal communications using established formats.

## Supported Communication Types

| Type | Description | Template File |
|------|-------------|---------------|
| 3P Updates | Progress, Plans, Problems | `examples/3p-updates.md` |
| Company Newsletter | Company-wide announcements | `examples/company-newsletter.md` |
| FAQ Responses | Answering common questions | `examples/faq-answers.md` |
| General Comms | Other internal messages | `examples/general-comms.md` |

## How to Use

1. **Identify the communication type** from the request
2. **Load the appropriate guideline file** from `examples/` directory
3. **Follow the specific instructions** for formatting, tone, and content

## Writing Guidelines

### 3P Updates (Progress, Plans, Problems)
- Progress: What was accomplished since last update
- Plans: What's planned for next period
- Problems: Blockers, risks, and mitigations

### Company Newsletters
- Opening with key wins or announcements
- Department highlights
- Culture and people section
- Upcoming events

### FAQ Responses
- Direct, empathetic answers
- Link to additional resources
- Clear next steps

## Common Pitfalls

- ❌ **Wrong format for the message type** — Always match format to intent
- ❌ **Too verbose** — Internal comms should be concise
- ❌ **Missing context** — Assume reader may have limited background
- ❌ **Generic tone** — Match company culture and audience

## Verification Checklist

- [ ] Communication type correctly identified
- [ ] Correct template loaded and followed
- [ ] Formatting matches company standards
- [ ] Tone appropriate for audience
- [ ] Key actions and next steps are clear
- [ ] Review for typos and clarity