internal-comms

Write structured internal communications with verified facts and explicit actions.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill internal-comms-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internal-comms
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/internal-comms
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill internal-comms-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn complex, urgent, or context-heavy information into concise internal communications that readers can quickly understand and act on.

Core Features & Use Cases

  • Incident Reports and Post-Mortems: Document impact, timelines, root causes, response actions, and prevention items in a factual, blameless format.
  • Status and Leadership Updates: Create structured Progress/Plans/Problems updates, executive briefings, risk summaries, and decision requests.
  • Announcements, FAQs, and Meeting Summaries: Communicate launches, all-hands outcomes, recurring questions, and next steps with audience-appropriate tone.
  • Use Case: Turn a production outage into a clear incident update that states the impact, current status, timeline, action items, and owner responsibilities without speculation or blame.

Quick Start

Use the internal-comms skill to draft a concise leadership update about the project status, key risks, and decision needed from executives.

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 blameless incident report for a production outage?

A blameless incident report documents impact, timelines, root causes, response actions, and prevention items factually. It requires verified facts and explicit owner responsibilities without speculation or blame to ensure clear post-mortem communication.

What is the best way to structure leadership updates and executive briefings?

The best way to structure leadership updates is using a Progress, Plans, and Problems format. This structured approach provides executives with concise status information, key risks, and explicit decision requests without unnecessary context.

How do I draft launch announcements and FAQs for engineering teams?

Draft launch announcements and FAQs by organizing essential information with audience-appropriate tone. Use concise formatting to communicate next steps, recurring questions, and launch outcomes that engineering teams can quickly understand and act on.

Can I use this for all-hands summaries and team status updates?

Yes, you can generate all-hands summaries and team status updates. The skill produces concise, actionable communications tailored for company-wide audiences, ensuring essential meeting outcomes and project statuses are clearly documented.

What should a post-mortem include to ensure it is actionable?

An actionable post-mortem must include verified facts, a detailed timeline, root causes, response actions, and explicit prevention items. Handling incidents blamelessly ensures the document remains objective and focused on future prevention.