40 lines
1.5 KiB
Markdown
40 lines
1.5 KiB
Markdown
---
|
|
name: internal-comms-anthropic
|
|
description: "To write internal communications, use this skill for:"
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
## 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
|
|
|
|
## Limitations
|
|
- Use this skill only when the task clearly matches the scope described above.
|
|
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
|
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|