# internal comms
## Metadata

- Canonical URL: https://6ducklearn.com/skills/internal-comms/
- Markdown URL: https://6ducklearn.com/skills/internal-comms/index.md
- Product: skills
- Category: collaboration
- Tags: anthropic, collaboration
- Updated: 2026-04-05T16:48:50.396208+00:00
## Summary
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
## Content
## 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

## Related Skills

- [doc coauthoring](https://6ducklearn.com/skills/doc-coauthoring/index.md): Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
- [brainstorming](https://6ducklearn.com/skills/brainstorming/index.md): You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- [dispatching parallel agents](https://6ducklearn.com/skills/dispatching-parallel-agents/index.md): Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- [executing plans](https://6ducklearn.com/skills/executing-plans/index.md): Use when you have a written implementation plan to execute in a separate session with review checkpoints
- [finishing a development branch](https://6ducklearn.com/skills/finishing-a-development-branch/index.md): Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- [receiving code review](https://6ducklearn.com/skills/receiving-code-review/index.md): Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation