
Team Communications
FreeStreamline your internal company communications effortlessly.
Free · Opens the source repo
What Team Communications does
The Team Communications skill is designed to assist users in drafting and formatting various types of internal communications within a company. It supports the creation of 3P updates (Progress, Plans, Problems), company newsletters, FAQ roundups, incident reports, leadership updates, status reports, and general internal communications. By leveraging this skill, users can ensure that their messages are not only polished but also adhere to the specific formats required by their organization.
This skill operates by first identifying the type of communication based on the user's request. It utilizes predefined reference files that contain the necessary formatting and content guidelines for each communication type. For instance, if a user requests a weekly update, the skill will refer to the references/3p-updates.md file to ensure that the output matches the company’s established format. This structured approach helps maintain consistency and professionalism in internal messaging.
Users can interact with the skill by using specific trigger phrases such as "3P", "newsletter", or "FAQ". Once a request is made, the skill gathers relevant inputs, either from connected tools like Slack or Gmail, or by prompting the user for context if those tools are unavailable. It then drafts the communication, ensuring it is concise and informative, and presents the draft for user review before finalizing.
This skill is ideal for team leaders, project managers, and anyone responsible for internal communications who seeks to save time and improve the quality of their updates. By automating the drafting process and ensuring adherence to company standards, it allows users to focus on content rather than formatting.
When to use it
Use this skill when you need to create any form of internal communication, such as updates, reports, or newsletters, and want to ensure they follow the correct format.
When not to use it
This skill may not be suitable for external communications or creative writing tasks, as it is specifically tailored for internal company messaging.
What you can build with it
Weekly Team Update
Use the skill to draft a concise weekly update for your team, ensuring it follows the company's 3P format.
Company Newsletter
Create a polished company newsletter by triggering the skill with relevant phrases, allowing for a professional presentation of updates.
FAQ Roundup
Compile a list of frequently asked questions and their answers into a clear and structured format for internal distribution.
How to install Team Communications
View source1. Install with the skills CLI
npx skills add alirezarezvani/claude-skills/team-communications --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by alirezarezvaniInternal Comms
Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.
Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.
Routing
Identify the communication type from the user's request, then read the matching reference file before writing anything:
| Type | Trigger phrases | Reference file |
|---|---|---|
| 3P Update | "3P", "progress plans problems", "weekly team update", "what did we ship" | references/3p-updates.md |
| Newsletter | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | references/company-newsletter.md |
| FAQ | "FAQ", "common questions", "what people are asking", "confusion around" | references/faq-answers.md |
| General | anything internal that doesn't match above | references/general-comms.md |
If the type is ambiguous, ask one clarifying question — don't guess.
Workflow
- Read the reference file for the matched type. Follow its formatting exactly.
- Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
- Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
- Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
- Present the draft and ask if anything needs to be added, removed, or reworded.
Tone & Style (applies to all types)
- Use "we" — you are part of the company.
- Active voice, present tense for progress, future tense for plans.
- Concise. Every sentence should carry information. Cut filler.
- Include metrics and links wherever possible.
- Professional but approachable — not corporate-speak.
- Put the most important information first.
When tools are unavailable
If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.
Anti-Patterns
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |
| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |
| Using passive voice for accomplishments | "The feature was shipped" hides who did the work | "Team X shipped the feature" — active voice credits the team |
| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |
| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |
Related Skills
| Skill | Relationship |
|---|---|
project-management/senior-pm | Broader PM scope — status reports feed into PM reporting |
project-management/meeting-analyzer | Meeting insights can feed into 3P updates and status reports |
project-management/confluence-expert | Publish comms as Confluence pages for permanent record |
marketing-skill/content-production | External comms — use for public-facing content, not internal |
Frequently asked questions about Team Communications
Similar skills
Invoice Chase
Automate overdue invoice reminders with personalized tones.
Roundup Setup
Personalize your status updates with ease.
Ticket Deflector
Streamline customer support responses with ease.
Orbit Gmail Briefing
Streamline your Gmail inbox with automated daily digests.
Email Sequence
Design and draft complete email sequences effortlessly.
Inbox Triage
Automate your email management with intelligent triage.
