mcpField
I
internal-comms

internal-comms

github.com/moizibnyousafDocuments1.2k114 installsUpdated 6w ago
Repository

About internal-comms

internal-comms is a writing skill for internal documents such as status reports, leadership updates, incident reports, and all-hands announcements. It emphasizes clear takeaways, specific details, and action-oriented follow-up.

Key features

  1. 01Status report templates
  2. 02Leadership update templates
  3. 03Incident report templates
  4. 04All-hands announcement templates
  5. 05Audience-appropriate tone

Use cases

  1. 01Report project progress and risks
  2. 02Summarize team results for leaders
  3. 03Document incident impact and timeline
  4. 04Share announcements with the whole team

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/moizibnyousaf/ai-agent-skills --skill internal-comms

After installing, type/internal-commsin Claude Code to confirm it loaded.

Details

From the project README

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

  1. Lead with the bottom line - Busy readers skim
  2. Be specific - Numbers > adjectives
  3. Own problems - "We missed" not "It was missed"
  4. Action-oriented - Every problem has a next step
  5. Appropriate tone - Match urgency to content

Comments

Markdown supported