본문으로 건너뛰기
cccskills
무료GitHub에 공개

internal-comms

Write consistent, high-quality internal communications (status reports, 3P updates, newsletters, FAQs, incident reports). Use company standards and formats for all internal messaging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(5)

  • SKILL.md5.8 KB
  • examples/3p-updates.md3.2 KB
  • examples/company-newsletter.md3.2 KB
  • examples/faq-answers.md2.3 KB
  • examples/general-comms.md602 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Internal Communications

Use This Skill When

  • Writing progress, plans, and problems (3P) team updates
  • Creating company-wide newsletters or announcements
  • Responding to FAQs or common questions
  • Drafting status reports for leadership
  • Documenting project updates or milestones
  • Writing incident reports or postmortems
  • Any internal company communication requiring consistent format

When NOT to Use

  • External communications (PR, customer-facing messaging)
  • Marketing copy or promotional content
  • Personal messages not following company standards
  • Highly sensitive legal/compliance matters

Context: Communication Standards Maturity

Undeveloped: Inconsistent formats, unclear messaging, no structure.

Target: Follow company templates, consistent tone, clear structure for each communication type.

Optimized: Automated formatting, tone consistency checking, cross-team alignment.

Core Principle

Consistency builds clarity. Using standardized formats for internal comms ensures information is where people expect it, leadership gets the signals they need, and team alignment increases.

Instructions

Step 1: Identify Communication Type

Determine which category your communication falls into:

TypePurposeFrequencyAudience
3P UpdateProgress, Plans, ProblemsWeeklyTeam + Manager
Company NewsletterBroad updates, announcementsMonthly/QuarterlyAll-hands
FAQ ResponseAnswer common questionsAs-neededPublic/Team
Status ReportLeadership summaryBi-weekly/MonthlyExecutives
Project UpdateSpecific project progressAs milestone reachedStakeholders
Incident ReportCritical issue documentationUrgent + PostmortemTeam + Leadership

Step 2: Load Appropriate Template

Reference the company's guideline file:

  • 3P Updates → examples/3p-updates.md

    • Format: Progress, Plans, Problems
    • Length: 3-5 paragraphs
    • Frequency: Weekly Monday
  • Company Newsletters → examples/company-newsletter.md

    • Format: Highlights, wins, upcoming events
    • Length: 2-3 pages
    • Audience: All employees
  • FAQ Responses → examples/faq-answers.md

    • Format: Question + answer + context
    • Length: Concise but complete
    • Searchability: Important for discovery
  • General Communications → examples/general-comms.md

    • Format: Flexible but structured
    • Use when type doesn't match above

Step 3: Follow Template Structure

Example: 3P Update Template

# 3P Update: [Your Name/Team] — [Week of DATE]

## Progress ✅
- [Completed milestone 1] — [brief context]
- [Completed milestone 2] — [brief context]
- [Progress on major item] — [% complete or status]

*Key win this week*: [Highlight one significant achievement]

## Plans 📋
- [Next priority 1] — starting [date]
- [Next priority 2] — starting [date]
- [Blocking item] — need [resource] by [date]

*Key upcoming milestone*: [Major deliverable date]

## Problems ⚠️
- [Issue 1] — impact: [X], resolution timeline: [Y]
- [Issue 2] — impact: [X], resolution timeline: [Y]

*How to help*: We need [specific ask] to unblock progress

Example: Company Newsletter Template

# Company Newsletter — [Month/Date]

## 🎉 This Month's Highlights

### Major Wins
- [Achievement 1] — [brief context]
- [Achievement 2] — [brief context]

### Customer Stories
- [Customer success 1]
- [Customer success 2]

## 📢 Announcements

### [Category]: [Announcement Title]
[Details and context]

### [Category]: [Announcement Title]
[Details and context]

## 🗓️ Upcoming Events
- [Event 1] — [date/time]
- [Event 2] — [date/time]

## 💡 Spotlight: [Team or Person]
[Recognition and context]

## 📊 By The Numbers
- [Metric 1]: [Value]
- [Metric 2]: [Value]

Step 4: Gather Required Information

Before drafting, collect:

Communication TypeKey Info Needed
3P UpdateLast week's progress, current blockers, next week's priorities
NewsletterWins from team, announcements, events, metrics
FAQCommon question, answer options, context
Status ReportMetrics, milestones, risks, budget status
Project UpdateCurrent status, next steps, dependencies
Incident ReportTimeline, impact, root cause, prevention

Step 5: Draft Following Guidelines

Tone guidelines by communication type:

  • 3P Update: Direct, factual, concise (assume reader is busy)
  • Newsletter: Warm, celebratory, engaging (build community feeling)
  • FAQ: Clear, helpful, jargon-minimized (assume reader is new)
  • Status Report: Professional, metrics-driven, executive-level summary
  • Project Update: Technical but accessible, clear next steps
  • Incident Report: Objective, blameless, focus on learning

Step 6: Quality Checklist

Before sending:

  • Matches company template structure
  • Tone consistent with communication type
  • Length appropriate (not overly verbose)
  • All key info included, no critical gaps
  • Names and dates spelled correctly
  • Links working and formatting clean
  • If sensitive, review with manager first
  • Proofread for grammar/typos

Output

Deliver:

  1. Draft communication using appropriate template
  2. Tone verification (consistent with type)
  3. Completeness check (all required info included)
  4. Ready-to-send version formatted per company standards

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

manu14357/zskills162026년 7월 24일 업데이트

manu14357의 스킬 모두 보기

이 스킬의 문제 신고