internal-comms
npx machina-cli add skill ECNU-ICALK/AutoSkill/internal-comms --openclawWhen 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:
- Identify the communication type from the request
- Load the appropriate guideline file from the
examples/directory:examples/3p-updates.md- For Progress/Plans/Problems team updatesexamples/company-newsletter.md- For company-wide newslettersexamples/faq-answers.md- For answering frequently asked questionsexamples/general-comms.md- For anything else that doesn't explicitly match one of the above
- 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
Source
git clone https://github.com/ECNU-ICALK/AutoSkill/blob/main/SkillBank/Common/AwesomeClaudeSkills/internal-comms/SKILL.mdView on GitHub Overview
Provides templates and guidelines for writing internal communications in company-approved formats. It covers 3P updates, newsletters, FAQs, status reports, incident reports, and more. It helps you identify the type, apply the right guidelines, and follow consistent formatting.
How This Skill Works
Identify the requested communication type. Load the matching guideline file from the examples directory (3p-updates.md, company-newsletter.md, faq-answers.md, or general-comms.md). Follow the formatting, tone, and content-capture instructions in that file; if no match is found, ask for clarification.
When to Use It
- 3P updates (Progress, Plans, Problems) for team dashboards.
- Company newsletters to share milestones and news.
- FAQ responses addressing common employee questions.
- Status reports to leadership or stakeholders.
- Incident reports documenting outages, causes, and fixes.
Quick Start
- Step 1: Identify the communication type from the request.
- Step 2: Load the appropriate guideline file from the examples directory (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md).
- Step 3: Follow the specific formatting and content-gathering instructions in that file.
Best Practices
- Identify the exact communication type from the request before drafting.
- Load and follow the matching guideline file from examples (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md).
- Gather required content and approvals as dictated by the guideline.
- Maintain the company's tone, templates, and formatting for consistency.
- Verify facts and dates; seek clarification if the request is unclear.
Example Use Cases
- A weekly 3P update to the product team outlining Progress, Plans, and Problems.
- A leadership update summarizing quarterly progress for executives.
- A company-wide newsletter announcing new hires and milestones.
- An FAQ response clarifying a common policy question for employees.
- An incident report detailing outage cause, impact, and remediation steps.
