Write internal communications using company formats. Use when writing status reports, leadership updates, company newsletters, FAQs, incident reports, project updates, or any internal communications.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: internal-comms description: Write internal communications using company formats. Use when writing status reports, leadership updates, company newsletters, FAQs, incident reports, project updates, or any internal communications. source: anthropics/skills license: Apache-2.0
Internal Communications
Document Types
Status Report
# [Project Name] Status Report
**Date:** [Date]
**Author:** [Name]
**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked
## Summary
[2-3 sentence overview]
## Progress This Week
- Completed: [items]
- In Progress: [items]
- Blocked: [items with owners]
## Key Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric] | [Target] | [Actual] | ⬆️/➡️/⬇️ |
## Next Week
- [Planned items]
## Risks & Mitigations
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| [Risk] | H/M/L | [Action] | [Name] |
## Asks
- [Any blockers needing escalation]
Leadership Update
# [Team] Update - [Date]
## TL;DR
[One paragraph executive summary - the only thing busy execs will read]
## Wins
- [Key accomplishment with impact]
- [Key accomplishment with impact]
## Challenges
- [Challenge]: [What we're doing about it]
## Key Decisions Needed
1. [Decision]: [Context, options, recommendation]
## Metrics Dashboard
[Include 3-5 key metrics with trends]
Incident Report
# Incident Report: [Title]
**Severity:** P0/P1/P2/P3
**Duration:** [Start] - [End]
**Impact:** [User/revenue impact]
**Status:** Resolved/Monitoring/Active
## Timeline
| Time (UTC) | Event |
|------------|-------|
| [Time] | [What happened] |
## Root Cause
[Clear explanation of what went wrong]
## Resolution
[What was done to fix it]
## Action Items
| Item | Owner | Due Date | Status |
|------|-------|----------|--------|
| [Action] | [Name] | [Date] | ⬜/✅ |
## Lessons Learned
- [What we learned]
- [What we'll do differently]
All-Hands Announcement
# [Announcement Title]
Hey team,
[Opening that sets context]
**What's happening:** [Clear, simple explanation]
**Why it matters:** [Impact and benefits]
**What you need to do:** [Specific actions if any]
**Timeline:**
- [Date]: [Milestone]
- [Date]: [Milestone]
**Questions?** [Where to ask]
[Sign-off]
Writing Principles
- Lead with the bottom line - Busy readers skim
- Be specific - Numbers > adjectives
- Own problems - "We missed" not "It was missed"
- Action-oriented - Every problem has a next step
- Appropriate tone - Match urgency to content
More by skillcreatorai
View allCreate, update, and manage Jira issues from natural language. Use when the user wants to log bugs, create tickets, update issue status, or manage their Jira backlog.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for creating new documents, modifying content, working with tracked changes, or adding comments.
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.