Skip to main content

internal-comms

Write internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, and project updates using repeatable internal formats.

설치로 이동

소스 정보

저장소
AlperTuncOrtak/crypto-data-pipeline
최근 소스 활동
2026년 6월 3일 12:03
감지된 SKILL.md 언어
영어
스타
2
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
6 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
internal-comms
description
Write internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, and project updates using repeatable internal formats.
risk
unknown
source
https://github.com/anthropics/skills
date_added
2026-03-21
license
Complete terms in LICENSE.txt
## When to use this skill To write internal communications, use this skill for: - 3P updates (Progress, Plans, Problems) - Company newsletters - FAQ responses - Status reports - Leadership updates - Project updates - Incident reports ## How to use this skill To write any internal communication: 1. **Identify the communication type** from the request 2. **Load the appropriate guideline file** from the `examples/` directory: - `examples/3p-updates.md` - For Progress/Plans/Problems team updates - `examples/company-newsletter.md` - For company-wide newsletters - `examples/faq-answers.md` - For answering frequently asked questions - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above 3. **Follow the specific instructions** in that file for formatting, tone, and content gathering If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format. ## Keywords 3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
GitHub에서 보기