Generate Internal Communications

Internal Comms Community is a compatibility alias of the internal-comms skill. Its own instructions say to use the internal-comms ID for new references when no existing contract requires this one, and to preserve this callable ID whenever an existing manifest or client configuration already uses it. The full instructions and support files remain local so existing installations continue to work offline, and the skill describes itself as one shared procedure rather than an additional capability.

The procedure has three steps: identify the communication type from the request, load the matching guideline file from the examples directory, and follow that file's instructions for formatting, tone and content gathering. The supported types are 3P updates (Progress, Plans, Problems), company newsletters, FAQ responses, status reports, leadership updates, project updates and incident reports.

The four bundled guideline files split the work like this:

• The 3P guideline produces a short team update built from three sections. Progress covers what was accomplished over the past reporting period, Plans covers top-of-mind priorities for the next period, and Problems covers anything slowing the team down, such as too few people, blockers, or a deal that fell through. It counts as a success when it can be read in 30-60 seconds.
• The newsletter guideline summarizes a week or month of company activity in roughly 20-25 bullet points for delivery over Slack and email. It favors many links, one or two sentence bullets and the "we" voice, and it prioritizes company-wide impact, leadership announcements, major milestones and external recognition. It says to leave granular team details for 3Ps and to skip information relevant only to small groups or already communicated.
• The FAQ guideline surfaces questions that confuse many employees and answers each in a sentence or two, based on official company communications where possible, with uncertainty stated clearly and a flag when a question needs executive input.
• The general guideline covers anything else. It asks about the audience, the purpose, the tone and any formatting requirements before drafting, and it recommends clear, concise, active-voice writing that puts the most important information first.

More detail from the guidelines: a 3P update gathers its material from available tools, such as Slack posts in large channels with many reactions, Google Drive documents from key team members, emails with many responses, and important non-recurring calendar meetings like product reviews. Progress covers anything from a week ago to today, Plans covers today through the next week, and Problems covers the past week. The larger the team, the less granular the items should be: a mobile team might report shipped features and fixed bugs, while a whole company reports things like new hires or closed deals. The default 3P format opens with an emoji chosen to fit the team's vibe. The newsletter guideline suggests an example layout with Company Announcements, Progress on Priorities (areas with sub-areas), Leadership Updates and Social Updates, and it draws on company-wide announcements from executives, large-attendee meetings such as all-hands, new documents that got attention, and external press. The FAQ guideline names areas employees often ask about, such as fundraising, new executives, upcoming launches, hiring progress and changes to vision or focus, and asks for links to authoritative sources such as docs, announcements and emails.

Use it when an existing installation or configuration still calls this ID for internal communications. Otherwise, prefer the internal-comms ID. Typical requests are a weekly update, a company newsletter, an FAQ roundup, a status report, a leadership update, a project update or an incident report.

Keep drafting separate from sending. The skill states that drafting does not authorize sending, scheduling or publishing, and that the expected handoff is a draft for the intended audience, not a claim that a message was sent. Use only the audience, date range and approved sources supplied. Reactions, executive seniority and document views are not proof of accuracy, and a private source does not automatically belong in a company-wide update. Do not treat the output as a substitute for environment-specific validation, testing or expert review. If required inputs, permissions, safety boundaries or success criteria are missing, stop and ask.

Inputs are the request, the intended audience and purpose, the date range, and the approved sources. For a 3P update, the team name and the time period are also needed. If the team name is not given, the skill says to ask for it. The skill's example turns two confirmed shipped items, one next-week task and one open dependency into Progress, Plans and Problems, preserving dates and uncertainty and leaving unknown metrics out. The output is a draft in the requested format.

Where they are available, the guidelines point to Slack (posts and questions in large channels with many reactions), Google Drive documents, email, and calendar events such as product reviews and all-hands meetings. Without access, the skill asks the user what to cover and then mostly formats the material.

Teams that already reference this alias in a manifest or client configuration, and anyone who needs a repeatable structure for internal updates, newsletters, FAQ roundups or incident reports.