# Chenycl Claude Skills Collection Internal Comms > Internal Communications - Skill: `tomevault-io/chenycl-claude-skills-collection-internal-comms` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/chenycl-claude-skills-collection-internal-comms` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/chenycl-claude-skills-collection-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: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/chenycl-claude-skills-collection-internal-comms --- # Internal Communications Write professional internal communications using proven formats and best practices. ## Communication Types ### 1. Status Report ```markdown # [Project Name] Status Report **Period:** [Date Range] **Author:** [Name] **Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked ## Executive Summary [2-3 sentences summarizing overall status] ## Key Accomplishments - Completed [milestone] ahead of schedule - Resolved [issue] affecting [impact area] - Launched [feature/initiative] ## In Progress | Item | Owner | Target Date | Status | |------|-------|-------------|--------| | Task 1 | @person | MM/DD | 🟢 | | Task 2 | @person | MM/DD | 🟡 | ## Blockers & Risks | Issue | Impact | Mitigation | Owner | |-------|--------|------------|-------| | [Blocker] | [Impact] | [Plan] | @person | ## Next Week's Focus 1. Priority item 1 2. Priority item 2 ## Metrics - KPI 1: X → Y (+Z%) - KPI 2: X → Y (+Z%) ## Questions/Decisions Needed - [ ] Decision needed on [topic] by [date] ``` ### 2. Leadership Update ```markdown # Leadership Update: [Topic] **Date:** [Date] **From:** [Your Name/Team] ## TL;DR [One paragraph executive summary - the only thing busy execs might read] ## Context [Why this matters, background information] ## Current State [Where we are now] ## Recommendation [What we propose, with clear reasoning] ## Options Considered | Option | Pros | Cons | Recommendation | |--------|------|------|----------------| | A | ... | ... | ✓ Recommended | | B | ... | ... | | ## Timeline [Key milestones and dates] ## Resource Needs [What you need from leadership] ## Next Steps 1. [Action] - [Owner] - [Date] ``` ### 3. Incident Report ```markdown # Incident Report: [Brief Description] **Severity:** P1/P2/P3/P4 **Status:** Investigating / Mitigated / Resolved **Incident Commander:** [Name] ## Summary **What happened:** [1-2 sentences] **Impact:** [Who/what was affected] **Duration:** [Start time] - [End time] ([X] hours) ## Timeline (All times in UTC) | Time | Event | |------|-------| | HH:MM | Issue first detected | | HH:MM | Team alerted | | HH:MM | Root cause identified | | HH:MM | Mitigation deployed | | HH:MM | Full resolution confirmed | ## Root Cause [Technical explanation of what caused the incident] ## Impact Assessment - Users affected: [Number] - Revenue impact: [Estimate if applicable] - Data impact: [None / Details] ## Resolution [What was done to fix it] ## Follow-up Actions | Action | Owner | Priority | Due Date | |--------|-------|----------|----------| | [Preventive measure] | @person | P1 | [Date] | ## Lessons Learned - What went well: [...] - What could improve: [...] ``` ### 4. Project Update ```markdown # [Project Name] Update **Date:** [Date] **Phase:** Planning / Development / Testing / Launch ## Progress Snapshot - **Overall:** 65% complete - **On schedule:** Yes/No - **Budget:** On track / Over by X% ## Highlights ✅ Achieved [milestone] ✅ Completed [deliverable] ✅ Resolved [blocker] ## Challenges ⚠️ [Challenge 1] - Mitigation: [plan] ⚠️ [Challenge 2] - Mitigation: [plan] ## Upcoming Milestones | Milestone | Target Date | Confidence | |-----------|-------------|------------| | [Milestone 1] | [Date] | High/Medium/Low | ## Team Updates - [Person] joining/leaving team - [Resource change] ## Dependencies - Waiting on [team/person] for [item] ``` ### 5. Newsletter/Announcement ```markdown # [Company/Team] Update: [Month/Week] ## 🎉 Wins & Celebrations - [Achievement 1] - [Achievement 2] - Shoutout to @person for [contribution] ## 📢 Important Announcements ### [Announcement Title] [Details...] ## 📅 Upcoming Events | Date | Event | Details | |------|-------|---------| | [Date] | [Event] | [Link/Location] | ## 📚 Resources & Learning - [Article/Doc title](link) - [Training opportunity] ## 💡 Tips & Tricks [Helpful tip relevant to the team] ## 🗓️ Key Dates - [Date]: [What's happening] ``` ### 6. FAQ Document ```markdown # FAQ: [Topic] **Last Updated:** [Date] ## Overview [Brief context about what this FAQ covers] --- ### General Questions **Q: [Common question 1]?** A: [Clear, concise answer] --- **Q: [Common question 2]?** A: [Answer with details] Additional resources: - [Link 1] - [Link 2] --- ### Technical Questions **Q: [Technical question]?** A: [Technical answer] ```code example if applicable``` --- ## Still Have Questions? Contact: [email/channel] ``` ## Writing Guidelines ### Tone - **Professional** but approachable - **Concise** - respect reader's time - **Action-oriented** - clear next steps - **Honest** - acknowledge challenges openly ### Structure 1. **Lead with the bottom line** - TL;DR first 2. **Use visual hierarchy** - Headers, bullets, tables 3. **Keep paragraphs short** - 3-4 sentences max 4. **Include clear CTAs** - What do you need from readers? ### Email Subject Lines - ✅ `[Action Required] Q4 Budget Approval by Friday` - ✅ `[FYI] New PTO Policy Effective Jan 1` - ✅ `[Project X] Weekly Update - On Track` - ❌ `Update` (too vague) - ❌ `URGENT!!!` (overused) ### Best Practices 1. **Know your audience** - Adjust detail level 2. **One topic per message** - Don't bury important info 3. **Use formatting** - Bold key points, use lists 4. **Proofread** - Errors undermine credibility 5. **Include timeline** - When do you need response? --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/chenycl) — claim your Tome and manage your conversions.