team-communications
by alirezarezvaniteam-communications helps AI assistants draft internal Workplace Communication, including 3P updates, newsletters, FAQ roundups, leadership updates, status reports, incident reports, and general team messages using reference templates and routing rules.
This skill scores 78/100, making it a solid listing candidate for directory users who want agents to draft or structure internal company communications. It has clear triggers and useful reference-backed workflows for common comms formats, though adoption is somewhat limited by missing install guidance and uneven depth across all formats named in the description.
- Strong triggerability: the frontmatter lists clear internal-comms keywords such as 3P, weekly update, newsletter, FAQ, status report, company update, and casual requests like “write my update.”
- Operational routing is explicit: SKILL.md maps communication types to reference files before drafting, reducing agent guesswork.
- Reference files provide practical content guidance for 3P updates, newsletters, FAQs, and general internal communications, including audience, length, tone, source-gathering expectations, and clarification questions.
- The repository has no install command or README at this skill path, so users must infer installation from the broader repo or platform conventions.
- Some formats advertised in the description, such as incident reports, leadership updates, and status reports, appear to fall back to the general comms guidance rather than having dedicated templates.
Overview of team-communications skill
What the team-communications skill does
The team-communications skill helps an AI assistant draft, edit, and format internal company communications: 3P updates, company newsletters, FAQ roundups, leadership updates, status reports, project updates, incident reports, and general team messages. It is built for Workplace Communication scenarios where the output must be concise, audience-aware, and ready to post in Slack, email, docs, or an internal update channel.
Best fit and real job-to-be-done
Use this skill when you have scattered work context and need a polished internal message rather than a generic summary. It is especially useful for managers, project leads, founders, chiefs of staff, engineering leads, and operators who regularly translate team activity into updates for executives, peers, or the whole company. The main job is not just “write nicely”; it is to choose the right communication format, ask for missing context, and turn raw notes into a clear update people can act on.
What makes it different from a normal prompt
The skill includes routing guidance and reference formats for common internal comms types. Instead of treating every request as a blank writing task, it maps prompts like “write my weekly update,” “summarize what shipped,” “make a FAQ,” or “draft a company newsletter” to the appropriate reference file. This reduces guesswork around structure, expected length, audience, and tone.
Important constraints before installing
The team-communications skill is most valuable when the assistant has enough source material: notes, Slack summaries, project status, docs, links, decisions, blockers, or leadership context. It does not magically verify company facts. For sensitive updates, incidents, layoffs, policy changes, or executive communications, expect a human review step before publishing.
How to Use team-communications skill
team-communications install and repository path
Install the skill from the GitHub repository with:
npx skills add alirezarezvani/claude-skills --skill team-communications
The upstream path is project-management/skills/team-communications in alirezarezvani/claude-skills. After installation, read SKILL.md first, then open the reference files that define the formats:
references/3p-updates.mdreferences/company-newsletter.mdreferences/faq-answers.mdreferences/general-comms.md
There is no separate script or automation folder for this skill; the value is in the routing rules and writing templates.
Inputs that produce better team-communications usage
Give the assistant the audience, time period, source facts, desired format, and publication channel. Weak input is: “write a team update.” Strong input is:
“Use the team-communications skill to write a 3P update for the Data Platform team for this week. Audience: VP Eng and adjacent team leads. Progress: migrated three pipelines, reduced failed jobs by 18%, completed dashboard review. Plans: finish backfill, document ownership, prepare QBR metrics. Problems: one vendor API limit and two open hiring gaps. Tone: concise, factual, no hype.”
This gives the skill enough information to choose the 3P structure and avoid inventing details.
Suggested workflow for first use
Start by naming the communication type if you know it: 3P, newsletter, FAQ, incident report, status report, or general internal comms. If you do not know the type, describe the audience and goal, then let the assistant route it. Ask for a first draft, then a second pass for tone, brevity, and missing context. For newsletters and FAQ roundups, provide links or summaries from Slack, email, calendar events, and docs; the repository guidance expects these sources when available.
Practical prompt patterns
For a newsletter, ask for 20–25 short bullets, links where available, and a “we” voice if that matches your company style. For FAQ roundups, ask the assistant to group repeated employee questions, answer only from provided facts, and flag unknowns. For general communications, include target audience, purpose, tone, and formatting requirements. These details matter more than clever phrasing because internal readers mainly need clarity, relevance, and trust.
team-communications skill FAQ
Is team-communications for Workplace Communication only?
Yes, it is designed for internal Workplace Communication. It can help with leadership updates, team updates, newsletters, FAQs, and operational announcements. It is not the best fit for marketing copy, external PR, customer support macros, legal notices, or sales emails unless you heavily adapt the prompt and review the output.
Can beginners use the team-communications skill?
Yes. The skill is beginner-friendly because it provides recognizable formats and asks for missing context when needed. A new manager can use it to create a weekly update without knowing the exact structure of a 3P. However, beginners should still provide source facts and review the final message for accuracy, politics, and tone.
How is it better than asking for an internal update directly?
A direct prompt may produce a readable message, but it often misses the expected company format or over-explains. The team-communications skill gives the assistant routing behavior: 3P updates should be short and structured around Progress, Plans, and Problems; newsletters should be scannable and link-rich; FAQs should focus on questions causing broad confusion.
When should I not use this skill?
Do not rely on it as the sole author for highly sensitive communications where wording has legal, HR, security, financial, or reputational risk. It is also a poor fit when you have no facts to provide and no tool access. In those cases, use it to create a question list or outline, then gather verified information before drafting.
How to Improve team-communications skill
Improve team-communications outputs with better context
The most common failure mode is a polished but vague update. Prevent this by supplying dates, team names, audience seniority, key decisions, metrics, blockers, owners, and links. For example, “shipped onboarding” is weaker than “shipped self-serve onboarding to 40% of new workspaces; activation improved from 31% to 37% in the first cohort.”
Tighten tone, length, and audience fit
Internal comms should usually be shorter than the writer expects. Ask for a version optimized for the reader: executives need decisions, risks, and measurable outcomes; teammates need next steps and owners; company-wide readers need context without jargon. If the first draft feels generic, request “cut 30%, keep metrics, remove cheerleading, and put the blocker in the first half.”
Iterate from draft to publishable message
A strong workflow is: rough draft, accuracy pass, audience pass, then formatting pass. After the first output, ask the assistant to list assumptions and missing facts. Then provide corrections and request a final version for the intended channel, such as Slack, email, or a doc. This turns the skill from a one-shot writer into an internal communications review loop.
Customize the skill for your company norms
To improve the installed team-communications skill, add examples of your company’s best updates, preferred headings, banned phrases, escalation language, and tone rules. If your organization has recurring rituals such as all-hands notes, launch updates, incident reviews, or monthly business reviews, create additional reference files following the same pattern as the existing references/ documents.