AgentSkillsCN

Internal Comms

内部沟通

SKILL.md

Internal Comms

Write internal communications - status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports.

When to Use

Use this skill when:

  • •Writing status updates and progress reports
  • •Creating leadership and executive communications
  • •Drafting newsletters and company announcements
  • •Writing incident reports and post-mortems
  • •Creating FAQs and knowledge base articles
  • •Communicating with third-party partners (3P)
  • •Writing change management communications
  • •Documenting project milestones and achievements

Key Concepts

Communication Types

  • •Status Reports: Weekly, monthly, project-specific
  • •Leadership Updates: Executive summaries, strategic updates
  • •Newsletters: Company-wide, team-specific, industry news
  • •Incident Reports: Outage summaries, root cause, remediation
  • •FAQs: Common questions and answers
  • •3P Updates: Partner and vendor communications

Tone and Style

  • •Executive: High-level, strategic, concise
  • •Technical: Detailed, accurate, jargon-appropriate
  • •Incident: Timely, factual, transparent
  • •Announcement: Clear, enthusiastic, action-oriented

Structure Best Practices

  • •Executive summary first (BLUF - Bottom Line Up Front)
  • •Clear sections and headers
  • •Bulleted lists for readability
  • •Action items and next steps highlighted
  • •Metrics and data when relevant
  • •Timelines and deadlines specified

Templates

Weekly Status Report

code
Subject: Weekly Status Report - Week [X]

Executive Summary
[Brief overview of key achievements, blockers, and risks]

Key Accomplishments
- [Project/Task 1]: [Status/Milestone]
- [Project/Task 2]: [Status/Milestone]
- [Project/Task 3]: [Status/Milestone]

Blockers & Issues
- [Issue]: [Impact], [Owner], [ETA for resolution]

Next Week's Focus
- [Priority item 1]
- [Priority item 2]
- [Priority item 3]

Metrics/KPIs
- [Metric 1]: [Value] ([Change from last week])
- [Metric 2]: [Value] ([Change from last week])

Incident Report

code
Subject: Incident Report: [Service Name] Outage - [Date]

Overview
[Brief description of what happened]

Timeline
- [Time]: Incident detected
- [Time]: Incident declared
- [Time]: Mitigation applied
- [Time]: Service restored

Impact
- [Affected systems/services]
- [Number of users affected]
- [Duration of outage]
- [Business impact]

Root Cause Analysis
[What caused the incident, investigation findings]

Resolution Steps
[What was done to fix the issue]

Post-Incident Actions
- [Immediate remediation]
- [Long-term fixes]
- [Process improvements]
- [Testing and validation]

Leadership Update

code
Subject: [Topic] - Leadership Update

Executive Summary
[High-level overview of update, why it matters]

Background & Context
[Context setting, strategic alignment]

Key Points
- [Point 1]: [Details]
- [Point 2]: [Details]
- [Point 3]: [Details]

Implications
- [Strategic implications]
- [Operational changes]
- [Resource needs]

Next Steps & Timeline
- [Action 1]: [Owner], [Deadline]
- [Action 2]: [Owner], [Deadline]

Questions & Discussion
[Any open questions for leadership]

Newsletter

code
Subject: [Newsletter Name] - [Date]

Headlines
- [Announcement 1]
- [Announcement 2]
- [Announcement 3]

Feature Story
[Detailed story about a project, achievement, or person]

Team Spotlight
[Highlight a team member or team achievement]

Upcoming Events
- [Event 1]: [Date, Time, Location]
- [Event 2]: [Date, Time, Location]

Quick Updates
- [Update 1]
- [Update 2]

Resources
- [Link 1]
- [Link 2]

Patterns and Practices

Writing Process

  1. •Define Purpose: What's the goal of communication?
  2. •Identify Audience: Who are they? What do they need?
  3. •Determine Format: Report, email, presentation, document?
  4. •Draft Content: Start with BLUF, add details
  5. •Review for Clarity: Remove jargon, simplify language
  6. •Check Tone: Appropriate for audience?
  7. •Proofread: Check grammar, spelling, formatting
  8. •Get Approval: If needed for sensitive communications

Best Practices

  • •Start with the most important information (BLUF)
  • •Use clear, concise language
  • •Avoid unnecessary jargon and acronyms
  • •Include data and metrics to support claims
  • •Be honest about challenges and blockers
  • •Specify owners and deadlines for action items
  • •Use consistent formatting and structure
  • •Keep executive communications brief
  • •Provide context for technical updates

Tone Guidelines

  • •Status Reports: Objective, factual, professional
  • •Leadership Updates: Strategic, high-level, forward-looking
  • •Incident Reports: Transparent, accountable, learning-focused
  • •Announcements: Clear, enthusiastic, actionable
  • •FAQs: Helpful, clear, comprehensive

Common Formats

Email

code
Subject: [Clear, specific subject line]
[Recipient],

[BLUF - main point in first sentence]

[Details in paragraphs with clear headings]

[Call to action or next steps]

[Signature]

Document/Report

code
[Title Page]

Executive Summary
[High-level overview]

Table of Contents

1. Background
2. Current Status
3. Key Achievements
4. Challenges & Risks
5. Next Steps
6. Appendix

Presentation

code
Title Slide: [Topic]
Slide 1: Executive Summary
Slide 2: Background/Context
Slide 3-N: Key Points (one per slide)
Final Slide: Next Steps/Questions

File Patterns

Look for:

  • •**/docs/internal/**/*
  • •**/status-reports/**/*
  • •**/comms/**/*
  • •**/newsletters/**/*
  • •**/incident-reports/**/*
  • •**/faq/**/*

Keywords

Internal communications, status report, leadership update, newsletter, incident report, post-mortem, FAQ, 3P update, executive summary, business communication, company announcement, change management