internal-comms

Write internal communications like 3P updates, newsletters, and FAQs using company formats.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill internal-comms-mccleod1290
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: internal-comms
Source: https://github.com/mccleod1290/bb-agentic-setupv2/tree/main/documenting-skills/internal-comms
Command: npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill internal-comms-mccleod1290

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent internal communications in company-preferred formats is time-consuming and inconsistent across authors. This Skill provides ready-made guidelines and strict formatting rules for common internal communication types so every update follows the same structure and tone. ## Core Features & Use Cases - 3P Updates: Produce concise Progress/Plans/Problems updates readable in 30-60 seconds, with strict formatting and data-driven content. - Company Newsletters: Compile 20-25 bullet company-wide newsletters organized into sections with links to relevant docs, Slack posts, and announcements. - FAQ Answers: Identify frequently asked employee questions and draft clear, sourced answers to reduce confusion. - General Communications: Handle any other internal comms by clarifying audience, purpose, and tone first. - Use Case: Ask for a weekly 3P update for the mobile team, and the Skill gathers context from Slack, Drive, email, and calendar (or user input) and outputs the strict emoji-headed Progress/Plans/Problems format. ## Quick Start Write a 3P update for the platform team covering last week's progress, next week's plans, and current blockers.

Frequently Asked Questions about internal-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a 3P update for my team?▼

A 3P update covers Progress, Plans, and Problems for a team over one week. Confirm the team name and time period, gather context from Slack, docs, or the user, then output the strict format: an emoji, team name, dates, and 1-3 sentences per section.

What format should a company-wide newsletter follow?▼

A company newsletter should be roughly 20-25 short bullet points grouped into sections like announcements, priorities, leadership updates, and social updates. Use the "we" voice, include links to relevant docs and Slack posts, and focus on company-wide impact.

Can this skill gather information from Slack and Google Drive?▼

Yes, the guidelines recommend pulling context from Slack posts with high engagement, Google Drive documents, emails, and calendar events when those tools are accessible. Without access, the user can supply the content directly and the skill formats it.

What if my communication type doesn't match any template?▼

Use the general-comms guideline for anything that is not a 3P update, newsletter, or FAQ. It instructs clarifying the target audience, purpose, tone, and formatting requirements before drafting the communication.

How long should a 3P update be?▼

A 3P update should be readable in 30-60 seconds, with each of the Progress, Plans, and Problems sections limited to 1-3 sentences. Content should be data-driven, matter-of-fact, and include metrics where possible.