Team Communications
Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms. Use when the calendar is full, updates go unread, or blockers surface late.
Install
/plugin marketplace add borghei/Claude-SkillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borghei/Claude-Skills --skill team-communicationsgit clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skills/project-management/team-communications ~/.claude/skills/team-communicationsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Team Communications The operating system a delivery team runs its information on: which channel a given message belongs in, how much the recurring calendar actually costs, how a status update survives a 20-second executive skim, and what happens when someone is blocked. Most teams never design this — it accretes, one well-intentioned meeting at a time, until 30% of the week is gone and blockers still surface three days late. ## When to use this skill - **The calendar is full and nobody can say why** — you need the meeting load measured in person-hours and dollars before you can argue about it - **Status updates go unread** — stakeholders keep asking questions the update already answered, which means it is not skimmable - **Blockers surface late** — a problem that existed Monday first appears in Thursday's status, because there is no escalation path with an SLA - **A team goes distributed or adds a third timezone** — the sync-heavy rhythm that worked co-located silently taxes one region - **Recurring "should this be a meeting?" arguments** — you need a routing rule the team agreed to in advance, not a per-case negotiation - **New team formation** — write the charter on day one, before the calendar fills with rituals nobody will later feel able to cancel ## Inputs the skill expects - A calendar export of recurring meetings: title, duration, cadence, attendees, day and start time (UTC)
Details
- Skill name
team-communications- Repository
- borghei/Claude-Skills
- Path
project-management/team-communications/SKILL.md- Repo updated
- 8 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Team Communications skill do?
Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms. Use when the calendar is full, updates go unread, or blockers surface late.
How do I install the Team Communications skill?
Claude Code plugin: /plugin marketplace add borghei/Claude-Skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Team Communications popular?
It lives in borghei/Claude-Skills, which has 1,157 GitHub stars and 217 forks, and is included in 1 curated skill list.
Related skills
Cto Advisor
1.2kborghei/Claude-Skills
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.
Customer Success Manager
1.2kborghei/Claude-Skills
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
Financial Analyst
1.2kborghei/Claude-Skills
Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making
Vpe Advisor
1.2kborghei/Claude-Skills
VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Use when scoring engineering org health, designing the eng org, planning capacity, or building the productivity dashboard.
Summarize Meeting
1.2kborghei/Claude-Skills
Turns meeting notes or transcripts into a summary of decisions, owned and dated action items, and open questions. Use when writing up a meeting, a recap email or a decision log; for patterns across a series use meeting-analyzer.
Weekly Review
1.2kborghei/Claude-Skills
Turn a week's wins, learnings, blockers and OKR progress, gathered by hand from your calendar, tasks and journal, into a structured review with next-week priorities. Use for a Friday/Sunday weekly review, GTD review, or OKR check-in.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.